Repository navigation
ci: add weekly Dependabot updates for actions and the npm package - #141
Merged
Merged
Conversation
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
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.
Adds
.github/dependabot.ymlwith weekly version updates forgithub-actions(all workflows under.github/workflows/) andnpmincontracts/evm/npm. The workflows pin actions by commit and the package pins its versions exactly, so without this nothing proposes updates.Both entries set a 7-day cooldown (Dependabot's default is 3), so a freshly published version is not proposed until it has been public for a week. Security updates are not subject to the cooldown.
The npm entry ignores
@openzeppelin/*. Those are the package's only dependencies today (peer, pinned to 5.4.0), and the package README states they are pinned to the version the protocol is built with, which is thecontracts/evm/lib/submodules. A Dependabot PR that bumped the peer pin alone would publish a package claiming a version the sources were never built against; an OpenZeppelin upgrade has to move the submodules and the pins together. So the npm entry has nothing to watch until the package gains another dependency.