Add Version command not respecting semver
Open
need/triage
- Dominant language
- Less
- Stars
- 50
- Forks
- 30
- Avg merge
- 50m
- Merged PRs (30d)
- 1
Description
When doing `./add-version ` for a patch release of the repo that is semver-wise later than the new version the `current` file points to the patch release rather than staying with the latest version.
Additionally, although less problematically, when the patch release is added to the `versions` file it is added at the end of the file rather than being added at the semver-wise correct spot.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.