chore: Configure Renovate #2

Open
renovate wants to merge 1 commit from renovate/configure into main
Member

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • package.json (npm)
  • .woodpecker.yml (woodpecker)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

With your current configuration, Renovate will create 15 Pull Requests:

chore(deps): update dependency @​nomiclabs/hardhat-etherscan to v2.1.8
  • Schedule: ["at any time"]
  • Branch name: renovate/nomiclabs-hardhat-etherscan-2.x-lockfile
  • Merge into: main
  • Upgrade @nomiclabs/hardhat-etherscan to 2.1.8
chore(deps): update dependency @​nomiclabs/hardhat-waffle to v2.0.6
  • Schedule: ["at any time"]
  • Branch name: renovate/nomiclabs-hardhat-waffle-2.x-lockfile
  • Merge into: main
  • Upgrade @nomiclabs/hardhat-waffle to 2.0.6
chore(deps): update dependency ethereum-waffle to v3.4.4
  • Schedule: ["at any time"]
  • Branch name: renovate/ethereum-waffle-3.x-lockfile
  • Merge into: main
  • Upgrade ethereum-waffle to 3.4.4
chore(deps): update dependency @​nomiclabs/hardhat-ethers to v2.2.3
  • Schedule: ["at any time"]
  • Branch name: renovate/nomiclabs-hardhat-ethers-2.x-lockfile
  • Merge into: main
  • Upgrade @nomiclabs/hardhat-ethers to 2.2.3
chore(deps): update dependency @​openzeppelin/contracts to v4.9.6
  • Schedule: ["at any time"]
  • Branch name: renovate/openzeppelin-contracts-4.x-lockfile
  • Merge into: main
  • Upgrade @openzeppelin/contracts to 4.9.6
chore(deps): update dependency chai to v4.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/chai-4.x-lockfile
  • Merge into: main
  • Upgrade chai to 4.5.0
chore(deps): update dependency ethers to v5.8.0
  • Schedule: ["at any time"]
  • Branch name: renovate/ethers-5.x-lockfile
  • Merge into: main
  • Upgrade ethers to 5.8.0
chore(deps): update dependency hardhat to v2.29.1
  • Schedule: ["at any time"]
  • Branch name: renovate/hardhat-2.x-lockfile
  • Merge into: main
  • Upgrade hardhat to 2.29.1
chore(deps): update dependency @​nomiclabs/hardhat-etherscan to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/nomiclabs-hardhat-etherscan-3.x
  • Merge into: main
  • Upgrade @nomiclabs/hardhat-etherscan to ^3.0.0
chore(deps): update dependency chai to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/chai-6.x
  • Merge into: main
  • Upgrade chai to ^6.0.0
chore(deps): update dependency ethereum-waffle to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/ethereum-waffle-4.x
  • Merge into: main
  • Upgrade ethereum-waffle to ^4.0.0
chore(deps): update dependency ethers to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/ethers-6.x
  • Merge into: main
  • Upgrade ethers to ^6.0.0
chore(deps): update dependency hardhat to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/hardhat-3.x
  • Merge into: main
  • Upgrade hardhat to ^3.0.0
chore(deps): update node.js to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24-bookworm
fix(deps): update dependency @​openzeppelin/contracts to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/openzeppelin-contracts-5.x
  • Merge into: main
  • Upgrade @openzeppelin/contracts to ^5.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR has been generated by Renovate Bot.

Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. --- ### Detected Package Files * `package.json` (npm) * `.woodpecker.yml` (woodpecker) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - Enable Renovate Dependency Dashboard creation. - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use. - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests (except for nuget) directories. - Group known monorepo packages together. - Use curated list of recommended non-monorepo package groupings. - Show only the Age and Confidence Merge Confidence badges for pull requests. - Apply crowd-sourced package replacement rules. - Apply crowd-sourced workarounds for known problems with packages. 🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs. --- ### What to Expect With your current configuration, Renovate will create 15 Pull Requests: <details> <summary>chore(deps): update dependency @&#8203;nomiclabs/hardhat-etherscan to v2.1.8</summary> - Schedule: ["at any time"] - Branch name: `renovate/nomiclabs-hardhat-etherscan-2.x-lockfile` - Merge into: `main` - Upgrade [@nomiclabs/hardhat-etherscan](https://github.com/nomiclabs/hardhat) to `2.1.8` </details> <details> <summary>chore(deps): update dependency @&#8203;nomiclabs/hardhat-waffle to v2.0.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/nomiclabs-hardhat-waffle-2.x-lockfile` - Merge into: `main` - Upgrade [@nomiclabs/hardhat-waffle](https://github.com/NomicFoundation/hardhat-waffle) to `2.0.6` </details> <details> <summary>chore(deps): update dependency ethereum-waffle to v3.4.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/ethereum-waffle-3.x-lockfile` - Merge into: `main` - Upgrade [ethereum-waffle](https://github.com/EthWorks/Waffle) to `3.4.4` </details> <details> <summary>chore(deps): update dependency @&#8203;nomiclabs/hardhat-ethers to v2.2.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/nomiclabs-hardhat-ethers-2.x-lockfile` - Merge into: `main` - Upgrade [@nomiclabs/hardhat-ethers](https://github.com/nomiclabs/hardhat) to `2.2.3` </details> <details> <summary>chore(deps): update dependency @&#8203;openzeppelin/contracts to v4.9.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/openzeppelin-contracts-4.x-lockfile` - Merge into: `main` - Upgrade [@openzeppelin/contracts](https://github.com/OpenZeppelin/openzeppelin-contracts) to `4.9.6` </details> <details> <summary>chore(deps): update dependency chai to v4.5.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/chai-4.x-lockfile` - Merge into: `main` - Upgrade [chai](https://github.com/chaijs/chai) to `4.5.0` </details> <details> <summary>chore(deps): update dependency ethers to v5.8.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/ethers-5.x-lockfile` - Merge into: `main` - Upgrade [ethers](https://github.com/ethers-io/ethers.js) to `5.8.0` </details> <details> <summary>chore(deps): update dependency hardhat to v2.29.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/hardhat-2.x-lockfile` - Merge into: `main` - Upgrade [hardhat](https://github.com/NomicFoundation/hardhat) to `2.29.1` </details> <details> <summary>chore(deps): update dependency @&#8203;nomiclabs/hardhat-etherscan to v3</summary> - Schedule: ["at any time"] - Branch name: `renovate/nomiclabs-hardhat-etherscan-3.x` - Merge into: `main` - Upgrade [@nomiclabs/hardhat-etherscan](https://github.com/nomiclabs/hardhat) to `^3.0.0` </details> <details> <summary>chore(deps): update dependency chai to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/chai-6.x` - Merge into: `main` - Upgrade [chai](https://github.com/chaijs/chai) to `^6.0.0` </details> <details> <summary>chore(deps): update dependency ethereum-waffle to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/ethereum-waffle-4.x` - Merge into: `main` - Upgrade [ethereum-waffle](https://github.com/EthWorks/Waffle) to `^4.0.0` </details> <details> <summary>chore(deps): update dependency ethers to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/ethers-6.x` - Merge into: `main` - Upgrade [ethers](https://github.com/ethers-io/ethers.js) to `^6.0.0` </details> <details> <summary>chore(deps): update dependency hardhat to v3</summary> - Schedule: ["at any time"] - Branch name: `renovate/hardhat-3.x` - Merge into: `main` - Upgrade [hardhat](https://github.com/NomicFoundation/hardhat) to `^3.0.0` </details> <details> <summary>chore(deps): update node.js to v24</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-24.x` - Merge into: `main` - Upgrade [node](https://github.com/nodejs/node) to `24-bookworm` </details> <details> <summary>fix(deps): update dependency @&#8203;openzeppelin/contracts to v5</summary> - Schedule: ["at any time"] - Branch name: `renovate/openzeppelin-contracts-5.x` - Merge into: `main` - Upgrade [@openzeppelin/contracts](https://github.com/OpenZeppelin/openzeppelin-contracts) to `^5.0.0` </details> 🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for `prhourlylimit` for details. --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
Add renovate.json
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
ci/woodpecker/pr/woodpecker Pipeline failed
f001a51d97
Owner

drain skip: no occupying job for rebase/fix-pr/CI-wait; remaining continue

drain skip: no occupying job for rebase/fix-pr/CI-wait; remaining continue
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
ci/woodpecker/pr/woodpecker Pipeline failed
Required
Details
Some required checks were not successful.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin "renovate/configure:renovate/configure"
git switch "renovate/configure"
Sign in to join this conversation.
No reviewers
code/maintainers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
code/czf-belt-vault!2
No description provided.