nebula-plugins / nebula-plugins/nebula-release-plugin
Since 18.0.4 NearestVersionLocator cannot handle non-semver tags (ie. "latest") correctly any more
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
Hey,
up until v18.0.3 the following scenario was handled correctly:
Given the following tag history of a repository in chronologically descending order:
latest
v2.0.0
v1.3.0
v1.2.4
Nebula release until v18.0.3 correctly detects v2.0.0 as the latest semver tag and infers the correct version calculates the correct next release version and tag.
Nebula release v18.0.4 however does not correctly detects v2.0.0 as the latest semver tag and infers instead version v0.0.1.
If there is a semver compliant tag chronologically newer than the tag "latest" nebula release v18.0.4 works as expected.
It would be great if you could revert the logic back to its prior v18.0.4 state.
Thanks a lot in advance!
Cheers
Oliver
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at NearestVersionLocator and compare its behavior between releases v18.0.3 and v18.0.4. Reproduce the tag history with the non-semver tag "latest" and semver tag v2.0.0, then verify that the latest semver version and next release tag are inferred correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100