Commit fb9e6f5
Automate tag, stable branch, and GitHub release after changeset publish
Adds five steps to the changeset-release job in release.yml that run
after `pnpm release latest` succeeds:
1. Get version — reads packages/cli/package.json
2. Create tag — bare X.Y.Z, idempotent
3. Create stable branch — only on main with a minor/major bump, idempotent
4. Build release notes — from the .changeset/*.md files consumed by the
Version Packages merge, with PR + author resolved by walking main's
first-parent history and reading the merge subject
5. Create GitHub release — reads notes from the file written in step 4,
--latest=legacy lets GitHub assign the badge by semver
Release notes are scoped to changesets only — anything without a
changeset is excluded by construction. Each step is independently
idempotent, so re-running the workflow recovers from partial failures.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 362ccfa commit fb9e6f5
1 file changed
Lines changed: 54 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
116 | 116 | | |
117 | 117 | | |
118 | 118 | | |
| 119 | + | |
| 120 | + | |
| 121 | + | |
| 122 | + | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
| 147 | + | |
| 148 | + | |
| 149 | + | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
119 | 173 | | |
120 | 174 | | |
121 | 175 | | |
| |||
0 commit comments