v1.2.5

Assurance that source matches against external when checking if payloads are equal (external sometimes doesn't have a certain key, either embeds or components). This may still need additional patches, but it covers what it needs to for now - v2.x should have this corrected when it is planned for transfer to TypeScript.

v1.2.4 - Fix --replace functionality

discord-microhook was updated to v1.0.5 which adds artificial thread support. In doing so, the channel ID for the message is no longer sent to the request (which was causing the error to begin with). Furthermore, the literal of null appearing in the cache has been fixed, and will now either be {webhookID} or {webhookID}-{threadID} to ensure cache accessibility (and backport consistency with prior stable versions).

v1.2.3 was published, but did not fix any problems due to persistent issues with discord-microhook until now. So it will be left unpublished on here.

CRLF line break CI errors are still appearing in the actions log, I'll see if I can disable or correct it for next minor or major release.

v1.2.2

reference will now check for context history, before attempting to use it - it had assumed it already existed, which it doesn't if there's no history to begin with.

Still having problems with caching details... this is what I get for assuming everything works first time.

v1.2.1 - Patch export target

package.json exports were pointed at a TypeScript file... which didn't exist.

Still running into a few problems while I try to setup TinkerStorm's new menu system for custom onboarding.

i.e. meow doesn't exist.

v1.2.0 - Thread support

channel-backup now supports the use of threads in Text and Forum Channels.

Please take the time to ensure that you have your environment configured if you decide to post to a Forum Channel, as it will not know what type of channel is being targeted (regardless if threadID or thread_name is provided, the type of parent channel is not immediately known to the webhook).

---

Join the community server for support, as well as updates on all projects of TinkerStorm.

Forum Use

To create a forum post using a webhook, specify a thread_name in the config you intend to use. Upon a successful run of the program, it will update the configuration to include the newly provided threadID - if using this with a CI runner, commit and push this as you would with the cache reference.

Thread Use

To post to a thread (or existing forum post), specify a threadID in the config you intend to use. Sequence branching is forbidden, the program will do everything it can to avoid this possibility.

v1.1.1 - ENV Support

• Webhook can be placed in the config or environment variables (not having one will cause the command to error at the moment).

  Fail states exist for no webhook or an invalid one, or if a message does not exist when modifying a message.
  A fail state also doesn't cleanup after itself, including if it had deleted messages or posted new ones - the cache would not be updated.

• The core schema no longer requires a webhook in the visible configuration.

Our community configuration has been setup with a matrix run using the template.

If you need any help setting this up, drop by our Discord server.

v1.0.0 - First Release

For users of the script that I 'distributed' before publishing it as a standardized package, I highly recommend you update to this - ensuring that you get updates without having me hand out copies of the code file whenever you request an update... (then again, I think it is just me handling that).

For the repositories created and hosted here that used a previous iteration of this script, they will be updated in due course. If you need any help setting this up for your own community, please drop by the project discord channel. If you want to know what this does... it keeps 'stuff' in a channel consistent, rather than having to ask an individual who authored the message(s) or knows how to control the bot that posted it. 😐

If installed globally, this command can be run in any folder (provided it has the necessary config to run in the first place).