chore(release): prepare 1.11.0 - #162
Merged
Merged
Conversation
Prepares the v1.11.0 release. Version bookkeeping only - no runtime code changes. - package.json version -> 1.11.0 - both package-lock.json version fields -> 1.11.0 - exact packaging/release/update-compatibility.json entry for 1.11.0 The migration registry is unchanged since v1.9.2 (git diff v1.9.2 main -- server/modules/database is empty). Schema generation stays at 20 and rollback stays exact, carrying forward every version declared by 1.10.0 plus 1.10.0 itself: 1.8.17, 1.8.18, 1.8.19, 1.9.0, 1.9.1, 1.9.2 and 1.10.0. npm run release:check-metadata passes with exactly this declaration. Release contents since v1.10.0: - #158 - feat(codex): answer asynchronous Codex questions from ChatMux - #161 - fix(claude): finish compaction in ready state Minor bump (1.10.0 -> 1.11.0) because #158 lands a user-facing feature, matching the 1.9.2 -> 1.10.0 precedent.
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 v1.11.0 release. Version bookkeeping only - no runtime code changes.
package.jsonversion -> 1.11.0package-lock.jsonversion fields -> 1.11.0packaging/release/update-compatibility.jsonentry for 1.11.0Schema generation and rollback
The migration registry is unchanged since v1.9.2 (
git diff v1.9.2 main -- server/modules/databaseis empty). Schema generation stays at 20 and rollback stays exact, carrying forward every version declared by 1.10.0 plus 1.10.0 itself: 1.8.17, 1.8.18, 1.8.19, 1.9.0, 1.9.1, 1.9.2, 1.10.0.npm run release:check-metadatapasses with exactly this declaration.Release contents since v1.10.0
Minor bump (1.10.0 -> 1.11.0) because #158 lands a user-facing feature, matching the 1.9.2 -> 1.10.0 precedent.
Verification
npm run release:check-metadatapassed locally for 1.11.0 (schema generation 20; 7 rollback-compatible versions)