Skip to content

Configure Renovate#19

Open
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/configure
Open

Configure Renovate#19
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented May 18, 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

  • composer.json (composer)
  • .github/workflows/dependabot-auto-merge.yml (github-actions)
  • .github/workflows/fix-php-code-style-issues.yml (github-actions)
  • .github/workflows/run-tests.yml (github-actions)
  • .github/workflows/syntax.yml (github-actions)
  • .github/workflows/update-changelog.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.
  • Show all Merge Confidence badges for pull requests.
  • Use semantic prefixes for commit messages and PR titles.

What to Expect

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

chore(deps): pin dependencies
chore(deps): update dependabot/fetch-metadata action to v2.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/dependabot-fetch-metadata-2.x
  • Merge into: main
  • Upgrade dependabot/fetch-metadata to 21025c705c08248db411dc16f3619e6b5f9ea21a
chore(deps): update dependabot/fetch-metadata action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/dependabot-fetch-metadata-3.x
  • Merge into: main
  • Upgrade dependabot/fetch-metadata to 25dd0e34f4fe68f24cc83900b1fe3fe149efef98
chore(deps): update ramsey/composer-install action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/ramsey-composer-install-4.x
  • Merge into: main
  • Upgrade ramsey/composer-install to 65e4f84970763564f46a70b8a54b90d033b3bdda
chore(deps): lock file maintenance
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • 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.

@renovate renovate Bot force-pushed the renovate/configure branch from d5bc921 to 9e804f6 Compare May 21, 2026 20:14
Onboarding PR predated InterWorks/renovate-config; switch from the generic
config:recommended default to local>InterWorks/renovate-config so this repo
inherits minimumReleaseAge (7 days) and the org best-practices config.
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