Skip to content

chore: Configure Renovate - #10

Merged
bearpong merged 2 commits into
mainfrom
renovate/configure
Sep 16, 2026
Merged

bearpong merged 2 commits into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Sep 16, 2026 •

Copy link
Copy Markdown
Contributor

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.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 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.


Detected Package Files

  • .github/workflows/pr.yml (github-actions)
  • .github/workflows/publish.yml (github-actions)
  • package.json (npm)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • 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.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs
  • Pin github-action digests.
  • Convert pinned GitHub Action digests to SemVer.
  • Run Renovate on following schedule: * 0-5 * * 1

What to Expect

With your current configuration, Renovate will create 3 Pull Requests, up to a maximum of 6 over time (see docs for prConcurrentLimit), plus 1 security update Pull Request which is not subject to this limit:

chore(deps): Update dependency vitest to v4.1.11 [SECURITY]
  • Branch name: renovate/npm-vitest-vulnerability
  • Merge into: main
  • Upgrade vitest to sha512-fhACrNXUidIbGSBr5FlbuBkO7VWC1ZyLl0DO4CU2DrQoAPxX84Ysxs+HeGQpii5lZWV1Q4gBZTTu49mF+A6Edw==
chore(deps): Update weekly dependency updates
  • Schedule: ["* 0-5 * * 1"]
  • Branch name: renovate/weekly-dependency-updates
  • Merge into: main
  • Upgrade @biomejs/biome to sha512-+SEC/mFk1a+5mvUANZgbZTaiZXs1nj4iMhL/PHiqDT5TPUEPFIlliEtkKKZB4N862yylHC3UI+/Sj2I0HJEqhA==
  • Upgrade @types/node to sha512-YJ7EqCstVTzIr0fMr7qul/977en+pQHrfmuKIo6Zr9i75Be21dr3MovcfvGtyvi2HAUrRerWps5sMO9I7WaxDw==
  • Upgrade @types/semver to 7.8.0
  • Upgrade abitype to 1.3.0
  • Upgrade actions/cache to caa296126883cff596d87d8935842f9db880ef25
  • Upgrade actions/checkout to d23441a48e516b6c34aea4fa41551a30e30af803
  • Upgrade actions/setup-node to 249970729cb0ef3589644e2896645e5dc5ba9c38
  • Upgrade foundry-rs/foundry-toolchain to 908c540300062bd5a7e473851cdb4282204cee09
  • Upgrade pnpm/action-setup to ea17c68df8912ef543352723c149a84f56e3d413
  • Upgrade semver to 7.8.5
  • Upgrade tsx to 4.23.13
chore(deps): Update actions/cache action to v6
  • Schedule: ["* 0-5 * * 1"]
  • Branch name: renovate/actions-cache-6.x
  • Merge into: main
  • Upgrade actions/cache to 55cc8345863c7cc4c66a329aec7e433d2d1c52a9
chore(deps): Update actions/checkout action to v7
  • Schedule: ["* 0-5 * * 1"]
  • Branch name: renovate/actions-checkout-7.x
  • Merge into: main
  • Upgrade actions/checkout to 3d3c42e5aac5ba805825da76410c181273ba90b1
chore(deps): Update actions/setup-node action to v7
  • Schedule: ["* 0-5 * * 1"]
  • Branch name: renovate/actions-setup-node-7.x
  • Merge into: main
  • Upgrade actions/setup-node to 820762786026740c76f36085b0efc47a31fe5020
chore(deps): Update dependency typescript to v7
  • Schedule: ["* 0-5 * * 1"]
  • Branch name: renovate/typescript-7.x
  • Merge into: main
  • Upgrade typescript to sha512-8FYau96o3NKOhbjKi/qNvG/W5jhzxkbdm5sj9AbZ/5T5sWqn3hJgLfGx27sRKZWTvyzCP8dLRBTf5tBTSRVUNA==

🚸 PR 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. Security update Pull Request is not subject to this limit and will be created straight away.


❓ 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 was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from bearpong as a code owner September 16, 2026 13:35
@bearpong
bearpong merged commit 2a3ed29 into main Sep 16, 2026
3 of 4 checks passed
@bearpong
bearpong deleted the renovate/configure branch September 16, 2026 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant