root/goodbuddy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: make release tags optional

Browse Source
This commit is contained in:
lofyer
2026-08-11 00:05:44 +08:00
parent 1f44782b98
commit 80c4ef5ed0
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+7 -5
View File
@@ -103,13 +103,15 @@ Keep Electron security boundaries intact:
CommonJS macOS icon tool. CommonJS macOS icon tool.
- Tag builds must use `v${package.version}`. The workflow also supports manual - Tag builds must use `v${package.version}`. The workflow also supports manual
dispatch and main-branch changes to release tooling. dispatch and main-branch changes to release tooling.
- Every push that updates the `github` remote is a release push. Before pushing, - Before a push that updates the `github` remote, ask whether the user wants a
release tag unless they already specified that choice. A branch-only push
does not require a version bump or tag. When the user requests a release,
verify that `package.json` and `package-lock.json` contain the same release verify that `package.json` and `package-lock.json` contain the same release
version, create `v${package.version}` at the exact commit being pushed, and version, create `v${package.version}` at the exact commit being pushed, and
push that tag so the native package matrix and GitHub Release run. push that tag so the native package matrix and GitHub Release run.
- Never move or reuse an existing release tag. If `v${package.version}` already - Never move or reuse an existing release tag. If `v${package.version}` already
exists locally or on a remote at another commit, increment the package exists locally or on a remote at another commit, increment the package
version and create a new matching tag before pushing. version and create a new matching tag before the release push.
- Verified baseline on 2026-08-04: commit `2f54938`, GitHub Actions run - Verified baseline on 2026-08-04: commit `2f54938`, GitHub Actions run
`30893805567` succeeded for validation and all six package targets, producing `30893805567` succeeded for validation and all six package targets, producing
six release artifacts plus the shared production bundle. six release artifacts plus the shared production bundle.
@@ -134,6 +136,6 @@ credentials, or private user artifacts.
This repository has two synchronized remotes, `origin` and `github`. Unless the This repository has two synchronized remotes, `origin` and `github`. Unless the
user explicitly names a remote, every requested push must update the current user explicitly names a remote, every requested push must update the current
branch on both remotes. Any push that includes `github` must also push the branch on both remotes. When the user requests a release tag, push the new tag
required `v${package.version}` release tag to every remote receiving the branch to every remote receiving the branch update. Verify all updated branch refs and
update. Verify all updated branch and tag refs after pushing. any applicable tag refs after pushing.