Skip to content

Configure Renovate - #17

Merged
sgt0 merged 2 commits into
masterfrom
renovate/configure
Jul 13, 2026
Merged

Configure Renovate#17
sgt0 merged 2 commits into
masterfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Apr 13, 2026

Copy link
Copy Markdown

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/ci.yml (github-actions)
  • flake.nix (nix)
  • pyproject.toml (pep621)

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 Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for development dependencies.
  • Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  • Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
  • Run lock file maintenance (updates) early Monday mornings.
  • Disable Renovate Dependency Dashboard creation.

What to Expect

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

Pin dependencies
Update actions/checkout action to v6.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: master
  • Upgrade actions/checkout to df4cb1c069e1874edd31b4311f1884172cec0e10
Update dependency meson to v1.11.2
  • Schedule: ["at any time"]
  • Branch name: renovate/meson-1.x
  • Merge into: master
  • Upgrade meson to ==1.11.2
Update astral-sh/setup-uv action to v8.3.2
  • Schedule: ["at any time"]
  • Branch name: renovate/astral-sh-setup-uv-8.x
  • Merge into: master
  • Upgrade astral-sh/setup-uv to 11f9893b081a58869d3b5fccaea48c9e9e46f990
Update dependency hatchling to >=1.31.0
  • Schedule: ["at any time"]
  • Branch name: renovate/hatchling-1.x
  • Merge into: master
  • Upgrade hatchling to >=1.31.0
Update msys2/setup-msys2 action to v2.32.0
  • Schedule: ["at any time"]
  • Branch name: renovate/msys2-setup-msys2-2.x
  • Merge into: master
  • Upgrade msys2/setup-msys2 to 66cd2cce69caa17b53920067426061ca1de3a884
Update Python to >=3.14.6
  • Schedule: ["at any time"]
  • Branch name: renovate/python-3.x
  • Merge into: master
  • Upgrade python to >=3.14.6
Update actions/checkout action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-7.x
  • Merge into: master
  • Upgrade actions/checkout to 9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0
Update dependency vapoursynth to v77
  • Schedule: ["at any time"]
  • Branch name: renovate/vapoursynth-77.x
  • Merge into: master
  • Upgrade vapoursynth to >=77
Lock file maintenance
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: master
  • Regenerate lock files to use latest dependency versions

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


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

@sgt0
sgt0 force-pushed the renovate/configure branch from 4ef86f6 to 5af4452 Compare July 13, 2026 21:04
@sgt0
sgt0 force-pushed the renovate/configure branch from 5af4452 to 14f5ea8 Compare July 13, 2026 21:52
@sgt0
sgt0 merged commit 705a5c4 into master Jul 13, 2026
12 checks passed
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