Skip to content

Releases: synzen/MonitoRSS

6.13.1

29 Apr 00:54

Choose a tag to compare

Integrate new version discord-rest v0.6.0 into DeliveryPipeline with Redis for distributed rate limit handling

6.12.7

29 Apr 00:53

Choose a tag to compare

Fix refresh rate calculations not working correctly for external pledges being fetched

6.12.6

29 Apr 00:52

Choose a tag to compare

Add support for fetching pledges from external API

6.12.5

10 Apr 02:44

Choose a tag to compare

Fix fallback absolute images not working. If a absolute HTTP url was in the last position for fallback urls, it was ignored if every every other placeholder in front of it was absent and the placeholder would resolve to nothing.

This issue arose when debugging why Discord was saying that the description was required in last 3 embeds of a 4-embed webhook execute payload (a hack for sending 4 embeds within 1 embed). The issue was the last 3 embeds had broken URLs because there were no fallback images.

6.12.4

14 Mar 22:50

Choose a tag to compare

Add statusOverride to Patron model to account for the case when Patreon fails to update a patron's status

6.12.3

13 Mar 04:49

Choose a tag to compare

Add additional check if patron's pledge is >0 since in some cases, Patreon's API keeps a patron who cancelled their pledge as active status, but have a pledge of 0

6.12.2

19 Feb 14:20

Choose a tag to compare

Removed changes that were being used for active development within the npm package (they should not have been uploaded to the npm registry)

6.12.1

19 Feb 01:29

Choose a tag to compare

Fix default prefix not showing for the help text for the prefix command (it was showing the server-defined prefix instead, if it existed)

6.12.0

06 Feb 14:55

Choose a tag to compare

Added support for any properties to be added in n/p comparisons through the compare command (previously only -title was allowed)

6.11.3

02 Feb 03:00

Choose a tag to compare

Add pledgeLifetimeOverride to Patron model as a remedial solution to Patreon possibly reporting incorrect lifetime amounts after start of new billing period