Skip to content

chore: Configure Renovate - #1

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Oct 17, 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.

🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request.

📚 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

  • .devcontainer/devcontainer.json (devcontainer)
  • images/buildx/Dockerfile (dockerfile)
  • images/go-task/Dockerfile (dockerfile)
  • go.mod (gomod)
  • images/go-task/go.mod (gomod)
  • renovate.json (renovate-config)
  • .woodpecker/image.yaml (woodpecker)
  • .woodpecker/release-pr.yaml (woodpecker)
  • .woodpecker/release.yaml (woodpecker)
  • .woodpecker/validate.yaml (woodpecker)

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.
  • Update vulnerable PHP runtime pins for CVE-2026-109618 and CVE-2026-109619.
  • 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.

What to Expect

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

chore(deps): update ghcr.io/revotale/ci/base docker tag to v0.1.6
  • Schedule: ["at any time"]
  • Branch name: renovate/ghcr.io-revotale-ci-base-0.x
  • Merge into: main
  • Upgrade ghcr.io/revotale/ci/base to sha256:f787bff2bc8551cd6499a93dce9f928a172c74e11b00050ec9828a73959d2514
chore(deps): update woodpeckerci/plugin-ready-release-go docker tag to v4.1.3
  • Schedule: ["at any time"]
  • Branch name: renovate/woodpeckerci-plugin-ready-release-go-4.x
  • Merge into: main
  • Upgrade woodpeckerci/plugin-ready-release-go to sha256:9b74a11d65a8a78c3c2d01f58bfda7ea2816f0ec3ddc43097e087e186749f6e3
chore(deps): update woodpeckerci/woodpecker-cli docker tag to v3.20.1
  • Schedule: ["at any time"]
  • Branch name: renovate/woodpeckerci-woodpecker-cli-3.x
  • Merge into: main
  • Upgrade woodpeckerci/woodpecker-cli to sha256:74c576faf49cce699825d11c7d7bd38ab5f007dd4f57cdbdd55099d2c0f2621a

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

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.

0 participants