You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update release.sh to use branch + PR instead of pushing to main
Branch protection on the public repo requires PR approval for all
changes to main. The script now creates a release/vX.Y.Z branch,
commits, pushes, and opens a PR. After merge, the maintainer creates
a GitHub release which tags the merge commit on main.
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -324,7 +324,11 @@ Releasing these skills is easy! Just run the following command:
324
324
./release.sh
325
325
```
326
326
327
-
This walks you through a semantic version bump (major/minor/patch), updates the version in `plugin.json`, `marketplace.json`, README badge, all `SKILL.md` files, and the CHANGELOG date, then commits, tags, and pushes. After it finishes, create a GitHub release for the tag at the URL it prints.
327
+
This walks you through a semantic version bump (major/minor/patch), updates the version in `plugin.json`, `marketplace.json`, README badge, all `SKILL.md` files, and the CHANGELOG date, then creates a release branch and PR. After the PR is approved and merged, create a GitHub release to tag main:
328
+
329
+
```bash
330
+
gh release create v<version> --target main --title "v<version>" --generate-notes
0 commit comments