Skip to content

fix: prevent update diagnostics from showing for matching pre-releases#162

Merged
saecki merged 2 commits intosaecki:mainfrom
happenslol:compare-pre-release-strings
May 13, 2025
Merged

fix: prevent update diagnostics from showing for matching pre-releases#162
saecki merged 2 commits intosaecki:mainfrom
happenslol:compare-pre-release-strings

Conversation

@happenslol
Copy link
Copy Markdown
Contributor

When the user requests a pre-release (e.g. crate = "1.0.0-alpha.3"), an update diagnostic was shown to the user even if the requested pre-release was the newest release.

This makes sure that both newest and newest_pre are considered when checking if the newest found version is matched by the user's requirements.

@saecki
Copy link
Copy Markdown
Owner

saecki commented May 13, 2025

Can you give an example of where that would be the case? I'm not quite sure I understand 🤔

Edit: never mind I've figured it out

@saecki
Copy link
Copy Markdown
Owner

saecki commented May 13, 2025

You were complete right, I've just changed things up a bit.

CI is failing because of, uhhhm reasons...

@saecki saecki merged commit 69a9c51 into saecki:main May 13, 2025
1 of 3 checks passed
@happenslol happenslol deleted the compare-pre-release-strings branch May 14, 2025 00:55
@happenslol
Copy link
Copy Markdown
Contributor Author

You were complete right, I've just changed things up a bit.

CI is failing because of, uhhhm reasons...

Cool, thanks for merging! The way you refactored it was the other possibility I considered 😅

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.

2 participants