Skip to content

Releases: Luzifer/twitch-bot

v3.35.1

12 Dec 10:26
v3.35.1
99eecd1
Compare
Choose a tag to compare
  • Bugfixes
    • [core] Fix: Reduce token requirements for category search
    • Update node dependencies
    • Update Go dependencies

v3.35.0

02 Dec 12:31
v3.35.0
f26ce9b
Compare
Choose a tag to compare
  • New Features

    • [template] Add functions parseDuration, parseDurationToSeconds
  • Bugfixes

    • [raffle] Fix: Raffle channel did not allow underscore in channel name

v3.34.0

16 Sep 09:17
v3.34.0
ff475f2
Compare
Choose a tag to compare
  • New Features

    • [marker] Implement actor to create stream markers
    • [templating] Add currentVOD function
  • Bugfixes

    • [linkcheck] Fix: Replace static (deprecated) user-agent list

v3.33.2

27 Aug 15:27
v3.33.2
8819b40
Compare
Choose a tag to compare
  • Bugfixes
    • [overlays] Fix KoFi donation currency in eventfeed
    • [raffle] Lint: Ignore linter false-positive
    • [CI] Lint: Replace deprecated linter

v3.33.1

14 Aug 14:31
v3.33.1
b1ceb29
Compare
Choose a tag to compare
  • Bugfixes
    • [core] Fix: Do not execute action after permission check
    • [editor] Update dependencies
    • [raffle] Fix: Send ID as string

Important

Make sure to update to this release ASAP as it contains a security-fix for the editor-APIs which previously did insufficient authorization checking.

v3.33.0

27 Jul 21:46
v3.33.0
4964ed2
Compare
Choose a tag to compare
  • New Features

    • [overlays] Add eventfeed as default-overlay
  • Improvements

    • [linkcheck] Add support for meta-redirects
  • Bugfixes

    • [kofi] Fix: Use message as string
    • [overlays] Fix: Transmit event-id as string

v3.32.0

09 Jun 11:59
v3.32.0
f1d4c1a
Compare
Choose a tag to compare
  • New Features

    • [templating] Add streamIsLive function
  • Bugfixes

    • [core] Fix: Accept proper token declaration in Authorization header
    • [core] Fix: Include username and channel in ban errors

v3.31.0

13 May 16:40
v3.31.0
19a30d3
Compare
Choose a tag to compare
  • Improvements

    • [core] Add locking to prevent concurrent rule executions
  • Bugfixes

    • [spotify] Fix: Refresh-Token gets revoked when using two functions

v3.30.0

26 Apr 17:56
v3.30.0
a01ce9a
Compare
Choose a tag to compare
  • New Features

    • [templating] Add userExists function
  • Improvements

    • [eventsub] Suspicious user topics were moved from beta to v1
  • Bugfixes

    • Update dependencies

v3.29.2

13 Apr 12:26
v3.29.2
932879c
Compare
Choose a tag to compare

Important

This release introduces a new configuration validation which might lead to your bot not starting as of stronger type checking of actor settings. To validate the config is fine run a validation against the config once before replacing the bot binary / Docker image:

./twitch-bot --storage-conn-string "file::memory:?cache=shared" -c path/to/config.yaml validate-config

Using the connection string shown above will use a non-persistent database and can be used while the existing bot is running.

  • New Features

    • [eventsub] Add support for suspicious user events
  • Improvements

    • [core] Enforce attribute type schema validation on config
    • [core] Remove deprecated fallback token / token migration
    • [counter] Allow counterTopList to specify how to sort
    • [counter] Record first seen and last updated on counters
    • [counter] Revise template parsing logic
    • [docs] Add field-type annotations to events
    • [spotify] Improve error handling / documentation
    • [spotify] Switch to PKCE flow, remove need for clientSecret
  • Bugfixes

    • [core] Fix: Do not retry core-kv query when it's not set
    • [core] Fix: Don't initialize twitch client before start checks
    • [eventsub] Fix: Fetching existing subscriptions broken

Note

In case you're using the DockerHub Docker images and rely on the presence of the stable tag please switch to the Github Registry and use the latest tag. Development releases are published as develop. The stable tag will not be updated beyond v3.28.1, DockerHub images are currently still supported but will be faded out.

Note

Re-release of v3.29.0 as of broken CI-pipeline in that release, no functional changes.