Skip to content

Handle NPM prerelease caret range expression #120

Merged
keshav-space merged 3 commits into
mainfrom
117-fix-npm-caret-range
Sep 6, 2023
Merged

Handle NPM prerelease caret range expression #120
keshav-space merged 3 commits into
mainfrom
117-fix-npm-caret-range

Conversation

@keshav-space

Copy link
Copy Markdown
Member

@TG1999

TG1999 commented Sep 6, 2023

Copy link
Copy Markdown
Contributor

@keshav-space LGTM! please add some context in commit messages to highlight why we are handling the caret expression in a special manner.

- Don't use `python-semanticversion` for parsing the npm caret range:
    it's returning incorrect vers range for the prerelease caret range expressions.
- Issue #117

Signed-off-by: Keshav Priyadarshi <git@keshav.space>
Signed-off-by: Keshav Priyadarshi <git@keshav.space>
Signed-off-by: Keshav Priyadarshi <git@keshav.space>
@keshav-space keshav-space force-pushed the 117-fix-npm-caret-range branch from 865dc05 to da287b1 Compare September 6, 2023 16:39
@keshav-space

Copy link
Copy Markdown
Member Author

@keshav-space LGTM! please add some context in commit messages to highlight why we are handling the caret expression in a special manner.

Thanks @TG1999, I have added the context along with the link to the original issue in the commit message.

@TG1999 TG1999 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@keshav-space keshav-space merged commit f28c4b0 into main Sep 6, 2023
@keshav-space keshav-space deleted the 117-fix-npm-caret-range branch September 6, 2023 18:47
Sign up for free to 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.

NpmVeresionRange is giving incorrect version range sequence for prerelease caret range

2 participants