Skip to content

fix: semver.diff prerelease to release recognition - #334

Closed
deefactorial wants to merge 2 commits into
npm:mainfrom
deefactorial:master
Closed

fix: semver.diff prerelease to release recognition#334
deefactorial wants to merge 2 commits into
npm:mainfrom
deefactorial:master

Conversation

@deefactorial

Copy link
Copy Markdown

What / Why

This Bug Fix fixes issues #333 and #288
This bug is when semver.diff incorrectly identifies releases from a prerelease to patch, minor, or major

  • tests included

References

#333#288

@deefactorialdeefactorial changed the title fix: semver.diff prerelease to release recognition fixes #333 #288fix: semver.diff prerelease to release recognitionJul 14, 2020
@deefactorial

Copy link
Copy Markdown
Author

@isaacs could you please review?

@lukekarrys
lukekarrys requested a review from a team as a code ownerApril 11, 2022 17:51
@farahmandakbarfarahmandakbar linked an issue May 12, 2022 that may be closed by this pull request
@wraithgar

Copy link
Copy Markdown
Contributor

#334

@wraithgarwraithgar reopened this Apr 5, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

https://semver.org/.v2.0.0

4 participants

@deefactorial@wraithgar@dominique-blockchain@lukekarrys