Repository navigation
Remove published-url input from call-release-pr workflow - #142
Merged
Merged
Conversation
Generate the release PR body from `package.json` files changed since the base commit. List each package in a table with its compare and published URLs. This covers not only npm packages, but also VS Code extensions (indeed, `vscode-stylelint`). This change also helps standardize release PR workflows across the organization. Ref: https://github.com/stylelint/vscode-stylelint/blob/5265ccc77a6ce1f4b9729e1d1434a9c590155040/.github/workflows/release-pr.yml
jeddy3
approved these changes
Oct 26, 2026
jeddy3
left a comment
jeddy3
left a comment
Member
There was a problem hiding this comment.
Nice standardisation.
LGTM, thank you.
Include private packages in the release PR body with an `N/A` published URL instead of skipping them. Use a scoped tag only when it exists, so a scoped root package still uses the version tag.
Member
Author
|
Much appreciated the quick review! Testing was successful; see PR #143. |
Member
Author
|
Also tested this in the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
None.
Generate the release PR body from
package.jsonfiles changed since the base commit.List each package in a table with its compare and published URLs.
This covers not only npm packages, but also VS Code extensions (indeed,
vscode-stylelint).This change also helps standardize release PR workflows across the organization.
Ref: https://github.com/stylelint/vscode-stylelint/blob/5265ccc77a6ce1f4b9729e1d1434a9c590155040/.github/workflows/release-pr.yml