chore: establish v2.1 development safety gate - #78
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
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.
Establishes the v2.1.0 integration workflow before Sprint 16B is merged.
The repository policy now defines
mainas production-only andv2.1as the active integration branch. Routine Sprint work uses short-lived branches and pull requests intov2.1; production promotion uses a separately authorizedv2.1→mainrelease pull request. Merge authorization, hotfix handling, release/tag separation, and branch cleanup are documented for agents and maintainers.CI adds a dependency-free branch-policy step:
feat/*,fix/*,test/*, andchore/*may targetv2.1.v2.1release promotion orhotfix/*may targetmain.GitHub branch protections were configured separately on both
mainandv2.1using the existingValidate static toolscheck. Both branches require pull requests, up-to-date CI, and resolved conversations; block force pushes and deletion; keep merge commits available; and require zero approving reviews because the repository currently has one maintainer.Validation:
npm testnpm run buildnode tests/ocr-smoke.test.mjsgit diff --checkThis PR contains no product or OCR implementation changes. It must remain open until explicitly reviewed and authorized for merge.