Set dependabot gomod versioning strategy to increase-if-necessary#235
Closed
anisaoshafi wants to merge 1 commit into
Closed
Set dependabot gomod versioning strategy to increase-if-necessary#235anisaoshafi wants to merge 1 commit into
anisaoshafi wants to merge 1 commit into
Conversation
Collaborator
@anisaoshafi I am not convinced about and I'm afraid this PR does not change the behavior but the issue lies somewhere else. We could try migrating to |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Dependabot's default behavior for Go modules skips major version bumps, so security fixes that land in a new major release (e.g. a CVE fixed in v29.x when we're on v28.x) never generate a PR.
Added
versioning-strategy: increase-if-necessaryto thegomodecosystem in.github/dependabot.ymlℹ️ Alternatively we can use
semver-majorCloses DRG-826