Skip to content

ticket-230: integration owns release metadata - #276

Closed
tom-sapletta-com wants to merge 1 commit into
mainfrom
ticket/230-release-ownership
Closed

tom-sapletta-com wants to merge 1 commit into
mainfrom
ticket/230-release-ownership

Conversation

@tom-sapletta-com

Copy link
Copy Markdown
Contributor

Release metadata (planfile/release-metadata.json) and its test were owned by application, the version it must follow by integration, so no single release ticket could keep main green (ticket-220 left test_release_availability red). Lists the two paths in the integration ownedPaths. Verified in an isolated clone with this manifest as base: one integration ticket changing uv.lock + both paths passes governance (GOV-PASS). See project/ticket-230/README.md.

@tom-sapletta-com

Copy link
Copy Markdown
Contributor Author

Closing this stale PR as superseded. Its implementation is already present on current main (7c593332be1a1b26fce9a0ea6ecbba8bf8d75cbe), introduced by c8bee8c8ed6b868cf2479debcb3d5a094d81e45f. All non-tracking files in this PR are byte-identical to main. Focused current-main verification: 49 tests passed across release availability, CI readiness, foundation helpers and SQLite/retry performance; governance reported PASS. This closure does not assert that this PR passed independent protected review or was merged. Existing OneDev runs fail PLANFILE_DEPENDENCY_PIN_MISMATCH and remain historical failures. Branches and the external ticket-231 dirty worktree are preserved.

@tom-sapletta-com
tom-sapletta-com deleted the ticket/230-release-ownership branch October 23, 2026 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant