Skip to content

⭐️⭐️⭐️ Open-source, self-hosted alternative to Linear and Plane. Project management and issue tracking where teams and AI agents work side by side to plan and ship products.

ci: fix release-please releases and mirror them into a release branch (#33)

Croffe38f319a770a
diff --git a/.github/workflows/release-branch.yml b/.github/workflows/release-branch.yml
new file mode 100644
index 00000000..7a82e5e8
--- /dev/null
+++ b/.github/workflows/release-branch.yml
@@ -0,0 +1,29 @@
+name: Release branch
+
+# Moves the `release` branch to the commit of every published GitHub Release, so
+# a deploy target that follows a branch (Coolify) runs released versions only.
+# The branch is a mirror: this workflow is the only writer, which keeps the push
+# a fast-forward. It is created on the first published release.
+on:
+ release:
+ types: [published]
+
+# Needed to push the branch with GITHUB_TOKEN. Do not protect `release` with a
+# rule that requires a pull request: GITHUB_TOKEN cannot push through it.
+permissions:
+ contents: write
+
+concurrency:
+ group: release-branch
+ cancel-in-progress: false
+
+jobs:
+ sync:
+ name: Move the release branch
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v4
+ with:
+ ref: ${{ github.event.release.tag_name }}
+
+ - run: git push origin HEAD:release
diff --git a/AGENTS.md b/AGENTS.md
index da904683..b490f99c 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -172,6 +172,21 @@ be a valid Conventional Commit (enforced by `pr-title.yml`).
The scope is the name of one app or package (`api`, `web`, `worker`, `bot`, `db`,
`auth`, …). A change spanning several of them carries no scope.
+`"package-name": ""` in `release-please-config.json` is what lets the release be
+created at all. With `separate-pull-requests: false` release-please names the
+release PR branch `release-please--branches--main`, without a component, while the
+`node` release type otherwise derives the component from the `name` in the root
+`package.json`. The two disagree, release-please skips the release, the merged PR
+keeps its `autorelease: pending` label, and every later run stops at
+`There are untagged, merged release PRs outstanding - aborting`. An empty package
+name makes both sides resolve to no component. Tags stay `vX.Y.Z` — that is
+`include-component-in-tag: false`, a separate setting.
+
+Publishing a release moves the `release` branch to the released commit
+(`release-branch.yml`), which is what the deploy target follows. `main` stays the
+only branch anyone works in; `release` is a mirror with a single writer, so it
+never needs a merge back. It appears with the first published release.
+
**Agents do not commit.** Do the work, then write the proposed commit message in
chat as a Conventional Commit (`type(scope): summary`) for the user to run. Do
not call `git commit` or `git push` unless the user explicitly asks.
diff --git a/release-please-config.json b/release-please-config.json
index 5783f2ac..52620bf0 100644
--- a/release-please-config.json
+++ b/release-please-config.json
@@ -6,6 +6,7 @@
"packages": {
".": {
"release-type": "node",
+ "package-name": "",
"changelog-path": "CHANGELOG.md",
"changelog-sections": [
{ "type": "feat", "section": "Features" },