Add dependabot.yml to reduce manual work #7100
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
birkskyum
force-pushed
the
Add-dependabot
branch
from
ce8fb57
to
0489b99
Compare
gvwilson
added
community
gvwilson
added
P1
birkskyum
force-pushed
the
Add-dependabot
branch
from
0489b99
to
92730be
Compare
|
Thanks very much @birkskyum for this PR. |
|
that makes sense - looking forward to the esbuild setup, it feels quite productive. |
|
And just to clarify, it'll not make any conflicts unless the PRs are manually merged, and it's set to open max 2. |
|
Thanks very much for the PR. |
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.
I noticed these recent commits:
This PR adds a dependabot that'll automate the bumping of minor/patch versions to keep them up to date, with release notes etc. (example here), so that the only work left for maintainers is to merge.
It'll not bump major versions of deps, which could lead to breaking changes.
There will be at most 1 open pr. per lockfile (so two, root+stackgl) with current settings.
It'll not auto merge unless this github workflow is also added. We actually do auto merge in maplibre, because the CI is the bar it has to meet anyway, and it's honestly quite a relief to be able to focus on the areas that needs attention.