Repository navigation
release(security): require both develop #575 and owner-publication #634 gates before 3.1.0 (#575) - #636
Merged
tse-wei-chen merged 7 commits intoNov 13, 2026
Conversation
…ted #575 security gate
…oth security gates
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.
TDD two-stage security/publication gate. Complete #575 on develop without touching main or weakening release controls: 3.1.0 publishing must separately demand owner-approved #634 closed completed with all checklist items checked, AND the existing exact-main SHA 18 Tests + SqlCore baseline gate. New test-first branch HEAD fails until #634 is actually queried, not an optional comment. No main/tag/release. Exact PR head 18/18 + SqlCore baseline and exact merge develop-push candidate required.
Final exact-HEAD evidence
a47198fba4878fe5ebb81026f4151cf83f847d93(base: develop).