Repository navigation
Release 2.1.0 - #65
Merged
Merged
Conversation
2 of 3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this change?
Bumps the version to 2.1.0 in
package.jsonandpackage-lock.json, and moves the unreleased changelog entries under## 2.1.0 (2026-10-05). It also adds the missing date to the 2.0.0 heading.2.1.0 rather than 2.0.1 because it adds features: the Discord bot (#63), BetaCraft and extra server lists (#63), and remembered minigame arenas (#64). It also carries the fixes from #63 and #64.
Once this is merged, tagging
v2.1.0runs the release workflow.How did you test it?
npm run lintpasses. Only the version and the changelog changed; CI runs the tests.node scripts/release-notes.js 2.1.0prints the 2.1.0 section, which the release workflow uses as the notes.Generated by Claude Code