Skip to content

Release v2.4.6 - #233

Merged
Kkkermit merged 13 commits into
mainfrom
develop
Nov 19, 2026
Merged

Kkkermit merged 13 commits into
mainfrom
develop

Conversation

@Kkkermit

Copy link
Copy Markdown
Owner

Testify v2.4.6

Important

Merge #232 (the version bump) into develop first. Until it merges, this pull request still reads 2.4.5, and merging it would release nothing.

What this changes

Ships #228 to #232 as version 2.4.6:

Release notes

Testify v2.4.6

Make your copy your own with one file. Hosts can now set their own links, who runs the copy and the default prefix in testify.config.json. Whoever adds the bot to a server is sent a getting-started message. This release also fixes misleading start-up logs, a development crash after switching branches, and a banner that dropped punctuation from the bot's name. npm ci now installs without warnings.

⚠️ Before you upgrade

  • The getting-started message is on by default. Once you upgrade, whoever adds the bot to a server gets one direct message. To turn it off, add { "greetInviter": false } to testify.config.json.
  • Nothing else needs setting up. testify.config.json is optional, and a copy without it keeps the original's links and the t? prefix. There are no new commands, intents or collections, and no database migration.
  • New optional variable: TESTIFY_CONFIG. It is only needed when the file is not beside .env, such as on a Railway volume. docker-compose.yml sets it itself.
  • Docker Compose users: take the new docker-compose.yml. It mounts the folder it runs from, read-only, at /app/instance, so the bot reads testify.config.json from beside .env.
  • Run npm ci and npm run build, rebuild the Docker image, or pull ghcr.io/kkkermit/testify:2.4.6. The lockfile changed. The new versions are all development tools apart from the reshaped undici override, and that override still installs undici 6.

✨ New

  • testify.config.json. It sits beside .env and holds nothing secret. Its keys:
    • repository: the website's source browser and every Source code button.
    • supportServer: every Support button. null hides them.
    • developer: who /bot info names.
    • operator: who runs the copy and how to reach them, shown on the privacy notice and the terms.
    • defaultPrefix: the prefix a server starts with.
    • greetInviter: whether the getting-started message is sent.
  • How the file behaves:
    • Every key is optional.
    • A mistake or an unknown key stops start-up with a list of every problem.
    • Editors check the file as you type through testify.config.schema.json.
    • npm run setup offers to write it at the end.
  • A getting-started message for whoever adds the bot. It says how to see what the bot can do, where to set it up, and how to change the prefix.
    • The adder is found from the server's audit log, then from the bot's own integration, and the server's owner gets it when neither says.
    • Closed direct messages are left alone, and bots and blacklisted accounts get nothing.
    • Nothing about it is stored, and the privacy notice now says so.
  • The operator is named. With operator set, the privacy notice and the terms open with a card naming whoever runs the copy and linking their contact.
  • Railway. A testify.config.json committed to a fork is copied into the image when the Dockerfile is built. A volume with TESTIFY_CONFIG works too. docs/hosting.md has both ways, and docs/customising.md is the new guide to the file.

🐛 Fixes

  • The banner draws the bot's whole name. Punctuation and accented letters were dropped, so a bot called Fixxer2.0 was shown as FIXXER20.
    • . , ! ? : ; _ / ( ) [ ] < > # $ % & * @ ^ now come from the banner's own font.
    • ' " + = \ | are drawn to match it.
    • An accented letter is drawn as the plain letter.
  • A reload during start-up no longer contradicts itself. Saving a file while the bot was starting printed "Connected to MongoDB", then a lost connection and failing log writes. Shutting down had closed the database under it. Start-up now stops quietly, and a disconnect the bot asked for is never reported as a lost connection.
  • A changed default prefix reaches every server that never chose one. A server's prefix is stored only when it differs from the default.
    • A server that saved one before this release keeps it until someone presses the prefix panel's Reset.

🛠️ For developers

  • The dev bot runs @testify/shared from its source. npm run dev and npm run dev:all pass --conditions=development, so:
    • A branch switched under a running dev:all can no longer crash it with Cannot read properties of undefined.
    • Starting no longer restarts the bot a second in on macOS.
  • A synced project folder is named. When iCloud Drive, Dropbox or Google Drive is syncing the folder, macOS cancels file reads with ECANCELED. dev:all now says so once, and how to fix it, and the README's troubleshooting table does too.
  • npm ci prints no warnings. The undici override is now a top-level undici@^5 entry, which npm 11.6 no longer warns about. jsdom is held at 29.1.1 for the tests and better-npm-audit is at 4.2.1, which removes the deprecated whatwg-encoding and lodash.get.

🔒 Security

  • The picomatch suppression is gone. GitHub withdrew advisory GHSA-fc5q-39xc-vjpf, so .nsprc no longer needs the entry 2.4.5 added, and npm run audit passes without it.

🧪 Tests

Full changelog: release/v2.4.5...release/v2.4.6

Why

How to verify

Before merging:

  • chore: Bumped the version to 2.4.6 and brought main into develop #232 is merged, and develop reads 2.4.6 in all three package manifests.
  • CI and the Docker image check on this pull request finish green.
  • Test the getting-started message live. Add the bot to a test server and check that the direct message arrives. It could not be tested against Discord before now.

After merging:

  • Actions → Release is green, and Releases shows v2.4.6 Testify with the notes above.
  • ghcr.io/kkkermit/testify has 2.4.6 and latest.

Checklist

  • This is the release pull request from develop into main.
  • Version updated to 2.4.6 in all three package manifests, the lockfile and the bug report template (chore: Bumped the version to 2.4.6 and brought main into develop #232, which merges into develop first).
  • npm ci --dry-run accepts the bumped lockfile.
  • npm run check passes locally. The database suites ran on CI, where they passed on feat: Let hosts make the bot their own with testify.config.json, and greet whoever adds it #228 to fix: Draw punctuation and accented letters in the start-up banner's name #231.
  • No read-modify-save operations on numeric fields.
  • Embeds come from the embed() factory.
  • No raw console.* calls.
  • Every promise is awaited or otherwise handled.
  • No new timers registered with the bot.
  • One new environment variable, TESTIFY_CONFIG, is in src/config/env.ts, both .env*.example files and docker-compose.yml. It is optional and the setup wizard does not ask for it.
  • No command's options or names changed, so docs/commands.md is unchanged.
  • Documentation updated: docs/customising.md (new), docs/hosting.md, the README, AGENTS.md and the privacy notice.
  • No database migration is needed.
  • Verified against live Discord from the real host: the getting-started message still needs a live check.
  • Release notes reflect the final merged changes.

Generated by Claude Code

@Kkkermit
Kkkermit merged commit 83646d7 into main Nov 19, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant