feat: add ability to output candidate releases #1041
Conversation
This file contains 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
In order to enable this new feature, I've added a new input called `only` that allows running only the desired functionality (`'create-github-releases' | 'list-candidate-releases' | 'update-pull-requests'`). It is backwards compatible with the `skipGitHubRelease` and `skipGitHubPullRequest` inputs.
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.
For the purposes of releasing, it is useful to just get the information of the packages that are about to be released.
If
only: 'list-candidate-releases'is set, only output information about which packages would be released.It provides
releases_pendingandpaths_to_releaseas the outputs.In order to enable this new feature, I've added a new input called
onlythat allows running only the desired functionality ('create-github-releases' | 'list-candidate-releases' | 'update-pull-requests').It is not a breaking change, and is backwards compatible with the
skipGitHubReleaseandskipGitHubPullRequestinputs.