-
Notifications
You must be signed in to change notification settings - Fork 312
Output the next version for components #1184
Copy link
Copy link
Open
Labels
priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Metadata
Metadata
Assignees
Labels
priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Is your feature request related to a problem? Please describe
I'd like to be able to get the next version of a component that release please will create a release for, based on the currently open PR.
For example, when I merge to main and release please opens a PR, I can get the
prsfrom the outputs, but there is no way to get just the next version of a component.Describe the solution you'd like
I'd like a new variable
next_versionto be included in the outputs for root and path components whenrelease_createdfor that component isfalse.Describe alternatives you've considered
The only real alternative is to try and extract the next version from the
prsoutput. However, this is not reliable because if release please doesn't update the PR, the output is omitted.Additional context
There is a scenario where only e.g.
chorecommits have been pushed and release please has not yet created a PR. In that case, I would suggest that the next patch version should be output asnext_versionfor root and path components.