bump(debugpy): downgrade to 1.6.7 #2382
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MrGreenTea
changed the title
williamboman
changed the title
williamboman
approved these changes
Aug 8, 2023
There was a problem hiding this comment.
Thanks! They probably just pulled that release from pypi. If Renovate runs before that happens, the CI will pass and the version will be upgraded. There's a setting in Renovate to wait X amount of time before merging version upgrades from package repositories that allow packages to revoke versions, but it's not really been an issue so far.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The debugpy team tested their release pipeline and this new release triggered renovate (see PR #2344) to update
debugpyto v1.6.8 which does not exist onpypi.Closes #2381.
Closes williamboman/mason.nvim#1441.
Note: I would have liked to find a way to prevent renovate from doing this in the future, but didn't fully understand the configuration. To me it looks like you already use the
pypidatasourceTemplate for this and therefore I don't exactly know if this can be prevented onmason-registry's side.