Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dependabot: disable version bump checks/only keep security updates #406

Merged
merged 1 commit into from
Jun 21, 2023

Conversation

laurazard
Copy link
Member

Go uses a minimal version selection algorithm to select the version of modules used in a build (see https://github.com/golang/go/wiki/Modules#version-selection).

From the go wiki:

[...] if your module depends on module A which has a require D v1.0.0, and your module
also depends on module B which has a require D v1.1.1, then minimal version selection
would choose v1.1.1 of D to include in the build (given it is the highest listed require version).

Since compose-go is a library and meant to be used by downstream implementations, in order to maximize compatibility with other imports we should try to use the lowest version of any dependencies we need, as opposed to using whatever latest version is available.

This commit changes the dependabot config to disable version bumps, keeping security updates enabled.
(see: https://docs.github.com/en/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)

Go uses a minimal version selection algorithm to select the version of modules
used in a build (see https://github.com/golang/go/wiki/Modules#version-selection).

From the go wiki:

```
[...] if your module depends on module A which has a require D v1.0.0, and your module
also depends on module B which has a require D v1.1.1, then minimal version selection
would choose v1.1.1 of D to include in the build (given it is the highest listed require version).
```

Since `compose-go` is a library and meant to be used by downstream implementations, in order
to maximize compatibility with other imports we should try to use the lowest version of any
dependencies we need, as opposed to using whatever latest version is available.

This commit changes the dependabot config to disable version bumps, but does keep security
updates enabled.
(see: https://docs.github.com/en/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)

Signed-off-by: Laura Brehm <[email protected]>
@laurazard laurazard added the dependencies Pull requests that update a dependency file label May 18, 2023
@laurazard laurazard requested review from ndeloof, glours and milas May 18, 2023 11:50
Copy link
Member

@milas milas left a comment

Choose a reason for hiding this comment

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

I agree with limiting dependabot to security updates here to keep churn/noise low.

In general though, I'd still advocate for bumping to latest dependency versions regularly. I realize there's no "winning" answer here, but IMO depending on old versions (and thus testing against them) is likely to result in more downstream issues than the other way around.

@glours glours merged commit 532cd92 into compose-spec:master Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants