6.13.26

Fix linting issues
Fix permission check bug where it did not make an exception for owners for supporter-blocked bots

6.13.25

Reorder command permission checks to check if bot is supporter-blocked after other permission checks (to allow owner IDs to work as intended)

6.13.24

Fix debug feed ids added from database not fully registering

6.13.23

Fix a case where no feed alerts were sent when a profile exists but no users are set

6.13.22

Fixed config.feeds.articleRateLimit not being respected (it was being multiplied by 5 on self hosts)

6.13.21

Change the minimum config.feeds.max value to be -1 to disable all feeds
Add config._vipRestricted to restrict global access to supporters
Fix webhook command checking the wrong channel for webhook permission and webhooks

6.13.20

Support articleMaxAge for feed-specific staleness determination for date checks

6.13.19

Fixed the occasional RangeError: Maximum call stack size exceeded that happens in logging
Support whitelisted schedules in run schedule script
Optimize sending fail record alerts by re-using the already-queried schedule feeds in schedule runs

6.13.18

Add support for registering debug feed IDs through the database. This decouples the debugging process from bot commands.

6.13.17

Fix custom schedules not being read properly in independent schedule runs