fix: enable --print-last-released*
when in detached head or non-release branch
#926
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.
Purpose
version --print-last-released
outside of release branches #900Rationale
When using PSR to evaluate what the last released tag was, it is irrelevant to impose release branch restrictions on the usage as it doesn't matter what branch you are actually on.
--print
and--print-tag
are not included here as those determine the next version value and those do currently rely upon the release branch configuration.How I tested
Created test cases that evaluate non-release branch environments in regular or strict mode while using
--print-last-released
,--print-last-released-tag
. The tests also evaluated the same command when in a detached head state.