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
{{ message }}
Repository navigation
Commit cb0c45f
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ The lookup uses `cargo metadata --no-deps`, ignores non-workspace packages, and
18
18
Contains release-plz post-processing commands:
19
19
20
20
-`x52-bump-changelogs` checks out a release-plz pull request, adds the released versions to crate changelogs, updates README version links, and pushes a commit when anything changed.
21
-
-`x52-update-release-notes` copies the matching changelog sections into GitHub releases.
21
+
-`x52-update-release-notes` copies the matching changelog sections into GitHub releases. Use `--then-undraft` to publish each release after its notes update succeeds.
22
22
-`x52-comment-release-pr` adds or updates a draft-release link comment on the merged release pull request.
23
23
-`x52-comment-release-assets-uploaded` adds or updates a comment after the release assets are uploaded.
24
24
-`x52-update-homebrew-tap` updates macOS checksums in `x52dev/homebrew-tap` and opens a formula pull request.
@@ -115,6 +115,17 @@ For GitHub Actions, enter the development shell before invoking the release comm
115
115
116
116
Pass release-plz output through `RELEASE_PLZ_PR_JSON` or `RELEASE_PLZ_RELEASES_JSON`, and provide `GH_TOKEN` for GitHub mutations.
117
117
118
+
`x52-update-release-notes`leaves the release's draft status unchanged by default.
119
+
To publish each release after its changelog notes are set, run:
120
+
121
+
```sh
122
+
x52-update-release-notes --then-undraft
123
+
```
124
+
125
+
The command skips releases whose package has no `CHANGELOG.md`. A failed notes
126
+
update stops the command before it publishes that release. An empty changelog
127
+
section uses the existing fallback note and can still be published.
128
+
118
129
The commands use fixed `x52-` HTML markers. They make retries update the existing comment instead of creating another one:
0 commit comments