Skip to content

chore: Configure Renovate#6

Closed
abkrim wants to merge 1 commit into
mainfrom
renovate/configure
Closed

chore: Configure Renovate#6
abkrim wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@abkrim
Copy link
Copy Markdown
Contributor

@abkrim abkrim commented May 4, 2026

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/phpstan.yml (github-actions)
  • .github/workflows/run-tests.yml (github-actions)
  • .github/workflows/update-changelog.yml (github-actions)

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.
  • 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
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic prefixes for commit messages and PR titles.
  • Separate major versions of dependencies into individual branches/PRs.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Run Renovate on following schedule: before 10am on monday

What to Expect

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

chore(deps): pin dependencies
chore(deps): lock file maintenance
  • Schedule: ["before 10am on monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

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

@abkrim
Copy link
Copy Markdown
Contributor Author

abkrim commented May 11, 2026

Superseded by #7 (canonical STD-002 config, merged 2026-05-11). Repo already has renovate.json on main — onboarding no longer needed.

@abkrim abkrim closed this May 11, 2026
@abkrim abkrim deleted the renovate/configure branch May 11, 2026 10:37
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.

2 participants