Skip to content

chore: Configure Renovate - #7

Merged
setchy merged 1 commit into
mainfrom
renovate/configure
Oct 8, 2026
Merged

setchy merged 1 commit into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Oct 8, 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/renovate-config-validator.yml (github-actions)
  • renovate.json (renovate-config)

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.
  • Raise PR when vulnerability alerts are detected.
  • If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
  • Use semantic commit scope deps for all commits and PR titles.
  • Separate each major version of dependencies into individual branches/PRs.
  • Rebase existing PRs any time the base branch has been updated.
  • Weekly schedule on early Monday mornings (before 4 AM).
  • Group all Vite+ related packages together.
  • Group download-artifact and upload-artifact major updates together.
  • Update $schema version in biome.json configuration files.
  • Pin github-action digests.
  • Convert pinned GitHub Action digests to SemVer.
  • Default preset for use with gitify's repos
  • Onboarding entry point for gitify organization repositories
  • Run Renovate on following schedule: * 0-3 * * 1

What to Expect

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

chore(deps): update actions/setup-node action to v4.4.0
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: main
  • Upgrade actions/setup-node to 49933ea5288caeca8642d1e84afbd3f7d6820020
chore(deps): update actions/setup-node action to v5
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-setup-node-5.x
  • Merge into: main
  • Upgrade actions/setup-node to a0853c24544627f65ddf259abe73b1d18a591444
chore(deps): update actions/setup-node action to v6
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to 249970729cb0ef3589644e2896645e5dc5ba9c38
chore(deps): update actions/setup-node action to v7
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-setup-node-7.x
  • Merge into: main
  • Upgrade actions/setup-node to 949feb2413d6458794dcd2491c4babbbce0c15c1

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

@renovate renovate Bot added the dependency label Oct 8, 2026
@setchy
setchy merged commit a2ad085 into main Oct 8, 2026
1 check passed
@setchy
setchy deleted the renovate/configure branch October 8, 2026 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant