release: sync main resolution and version gate into dev - #2332
Merged
Conversation
Release 0.8.10: stats, memory, imports, and runtime hardening
Merge release/0.8.11 into main
Release 0.8.12
# Conflicts: # package.json
Release 0.9.0
release: Code UX 0.9.1
Merged
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
Syncs current
mainconflict resolution back intodevbefore the release promotion, bumps the package version to0.9.2, and adds a CI gate that requires futuremainrelease PRs to include a version bump.What Changed
maininto the release promotion branch sodevreceives the E2E and workflow conflict resolutions before the final main PR.devwhile adding the deterministic agent preset fixture helper frommain.main.package.jsonfrom0.9.1to0.9.2.Release Version Bumpto CI for pull requests targetingmain; it comparespackage.jsonbetween the PR head and targetmaincommit and fails unless the version increases.Validation
Risk / Rollback
Low runtime risk: this PR only syncs release branch resolution, package metadata, CI, E2E conflict resolution, and docs. Roll back by reverting this PR before creating the final
mainrelease PR.