2.0.1: General bug fixes, some quality-of-life (both bot & release process)

[daniwasonline]

Howdy, everybody! This release includes a few bug fixes and improvements with the actual bot, as well as a few (pleasant) utils being added to the toolchain for ease-of-development/maintenance:

• Generated memory logs are now uploaded onto a Wastebin instance, with the instance being configurable in env (see .env.example for more information). Currently, memory logs are completely discarded if SpongeChat isn't pointed to a valid Wastebin instance, although there are plans to fix this in a future update.

Note

Currently, this behaviour only takes place when wiping memories through /forget. We'll move the upload process to the generation step in a future update to address this issue. Long passive responses will also receive Wastebin support in the future.

• We quickly patched up a few bugs with passive activation responses. Notably, long passive activations (i.e. responses over 2,000 characters) that call modules (i.e. Imagine) should now automatically include and remove the event/module banners in the response file itself. We may change this behaviour in the future to have the banners in the message content rather than in the file.

• On the development side, we're adding an automated release tool, release-it. We've also built a special plugin for it that automatically generates an AI summary using LLaMA based on provided commit names and versioning information. (We actually pushed this release with the new tooling, scroll down for what it generated!)

If you have your local env set up for Workers AI, you're already set for pushing releases! The plugin itself uses the same Workers AI SDK that we built for 2.0, including the same env keys. If you don't have this, then don't worry: the plugin will fail out, but the rest of the release step should go on as normal.

AI Summary

✨ Note: This release note was written by LLaMA and is not necessarily accurate. Please refer to the Commits section for more concise information on what's changed.

We're excited to release version 2.0.1 of our plugin, packed with some great updates!

First, we've improved the clarity of the GITHUB_TOKEN effect to make it easier to understand how it works. We've also enhanced the error handling when fetching data, so you'll get more helpful messages if anything goes wrong.

Additionally, our environmental configuration files have been tweaked to make them more user-friendly. We've also made some updates to our waste management system, ensuring it's working smoothly.

To improve the overall user experience, we've replaced plaintext links with buttons, and made sure they actually work as intended. We've also done some initial setup for our snapshotting system, laying the groundwork for future enhancements.

Finally, we've fixed a few bugs, including one that could cause issues with long responses and another that forgot to trim some data. With these updates, you should be able to enjoy a more stable and effective plugin experience. Happy using!

Commits

• be more clear on what GITHUB_TOKEN effects dde6e5e
• handle fetch errors better d0866bc
• improved env.example 4162b2d
• memories d6eadb4
• revert version back to .0, plugin should now abort on no api 19d61da
• I think this is good! 04eb9e1
• use buttons instead of plaintext link ccf893c
• make it actually work df601e9
• initial wastebin configuration a020cf0
• initial testing the plugin ca865d1
• cleanup remnants 58d27cd
• dragonfly snapshotting 385a4f9
• forgot to call trim() 51ecbe4
• long responses using the imagine module should return an updated image 1359b0b

---

This discussion was created from the release 2.0.1: General bug fixes, some quality-of-life (both bot & release process).