Prepare v2.0.0 release - #13
Merged
Merged
Conversation
- Add version field to package.json - Add CHANGELOG.md documenting the v1.0.0 -> v2.0.0 changes - Add a Releasing section to CONTRIBUTING.md for future releases - Add a release badge to README.md Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
Prepares the v2.0.0 release: adds a
versionfield, aCHANGELOG.md, and a documented release process so the next release is repeatable."version": "2.0.0"topackage.jsonCHANGELOG.md(Keep a Changelog format) covering the v1.0.0 -> v2.0.0 changes: repo restructure (breaking), growth to 52 architectures / 1297+ questions, the[Scenario]tag, the quiz site, the build/validation toolchain, and CI fixes## Releasingsection toCONTRIBUTING.mddocumenting the tag/release steps for future maintainersREADME.mdValidation
npm run ci(test, check, readme:check, build) passes locallyNext steps (after merge)
Tag the merge commit
v2.0.0and create the GitHub Release per the newCONTRIBUTING.mdsteps.🤖 Generated with Claude Code