Use shared Renovate preset and update pnpm to v10#602
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.
Migrate the repository from pnpm v9 to v10 and adopt the shared Renovate preset from
api3dao/renovate-config. This improves supply chain security viaminimumReleaseAgeenforcement and standardizes Renovate configuration across projects.As a part of https://github.com/api3dao/tasks/issues/1855
Changes beyond the task description
dotenv,immer,rimraf,@types/node,hardhat): Latest versions were publishedwithin the 14-day
minimumReleaseAgewindow. Lowered each semver lower bound by one patch so pnpm can resolve amature version within the range. Caret ranges still allow future updates once they age past 14 days.
npm install -g pnpm@9→pnpm@10to match the newpackageManagerfield.Test plan