mirrors/pikasTech-unidesk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify release line service ownership

Browse Source
This commit is contained in:
Codex
2026-05-25 11:52:28 +00:00
parent 4a03052747
commit 1d56c46546
2 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/release-governance.md
+2
View File
@@ -27,6 +27,8 @@ This document records the target policy. It does not by itself create a `release
- security and compatibility fixes;
- narrowly scoped deployment fixes that preserve the existing architecture.
Frontend and CLI ownership are intentionally separate from this stable line. The production frontend service, `scripts/cli.ts`, the `tran` wrapper and distributed SSH passthrough behavior follow `master` unless an explicit release decision says otherwise. `release/v1` is only the stable maintenance target for backend-core / Code Queue runtime fixes; do not backport frontend or CLI/tran changes to `release/v1` merely because they are needed by the current production UI or runner control path.
`release/v1` must not carry new product features, large architecture changes, the default Rust backend-core switch, or speculative Code Agent sandbox behavior. Any exception requires an explicit issue and a deployment rollback plan.
Until the release-line implementation is completed in CLI, CI, CD and documentation, the current repository rule still applies: UniDesk agent changes are developed on `master` and pushed to `origin master`. Creating or updating `release/v1` is an explicit release operation, not a replacement for arbitrary feature or fix branches.