chore: prepare v3.12.0 release - #282
Merged
Merged
Conversation
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.
Summary
Why
This release groups the consolidation and maintenance improvements merged since v3.11.0. Matching the Python, plugin, npm, lockfile, and VS Code metadata prevents the release workflows from publishing mismatched versions. Keeping the checkpoint compatibility epoch separate from the package version avoids invalidating safe v3.11 checkpoints solely because the release number changed.
Changes
Type of Change
Test plan
Testing
The local suite ran with external database credentials unset; live database tests were skipped locally. GitHub CI on the final head passed the isolated SurrealDB integration, including the v3.11 checkpoint-resume regression coverage.
Checklist
Verified by
@acidkill
Related Issues
None