Skip to content

chore: Configure Renovate#9

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

chore: Configure Renovate#9
fzymgc-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@fzymgc-renovate

@fzymgc-renovate fzymgc-renovate Bot commented Jun 15, 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.yaml (github-actions)
  • .github/workflows/release-please.yaml (github-actions)
  • .github/workflows/release.yaml (github-actions)
  • .github/workflows/vhs.yaml (github-actions)
  • go.mod (gomod)

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
  • 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
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic prefixes for commit messages and PR titles.
  • Automerge digest upgrades if they pass tests.
  • Automerge patch upgrades if they pass tests.
  • Automerge patch and minor upgrades if they pass tests.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced workarounds for known problems with packages.
  • 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

What to Expect

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

chore(deps): update module golang.org/x/sys to v0.44.0 [security]
  • Schedule: ["at any time"]
  • Branch name: renovate/go-golang.org-x-sys-vulnerability
  • Merge into: main
  • Upgrade golang.org/x/sys to v0.44.0
fix(deps): update github.com/emersion/go-vcard digest to d854b7e
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-emersion-go-vcard-digest
  • Merge into: main
  • Upgrade github.com/emersion/go-vcard to d854b7e0e2d3
fix(deps): update module github.com/zalando/go-keyring to v0.2.8
fix(deps): update all non-major dependencies (minor)
chore(deps): update actions/checkout action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-7.x
  • Merge into: main
  • Upgrade actions/checkout to v7
chore(deps): update actions/setup-go action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-go-6.x
  • Merge into: main
  • Upgrade actions/setup-go to v6
chore(deps): update actions/upload-artifact action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: main
  • Upgrade actions/upload-artifact to v7
chore(deps): update arduino/setup-task action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/arduino-setup-task-3.x
  • Merge into: main
  • Upgrade arduino/setup-task to v3.0.0
chore(deps): update golangci/golangci-lint-action action to v9
chore(deps): update googleapis/release-please-action action to v5
chore(deps): update goreleaser/goreleaser-action action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/goreleaser-goreleaser-action-7.x
  • Merge into: main
  • Upgrade goreleaser/goreleaser-action to v7
fix(deps): update module github.com/cucumber/messages/go/v21 to v33

🚸 PR creation will be limited to maximum 4 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 has been generated by Mend Renovate.

@fzymgc-renovate fzymgc-renovate Bot added dependencies Pull requests that update a dependency file renovate labels Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file renovate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants