Skip to content

Configure Renovate#20

Open
cesmarvin wants to merge 1 commit into
developfrom
renovate/configure
Open

Configure Renovate#20
cesmarvin wants to merge 1 commit into
developfrom
renovate/configure

Conversation

@cesmarvin

@cesmarvin cesmarvin commented Jul 6, 2026

Copy link
Copy Markdown
Member

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

  • 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
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs

You have configured Renovate to use branch /^(develop|main|master)$/ as base branch.

What to Expect

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

Update module github.com/cloudogu/go-cas to v2.4.0 (develop)
  • Schedule: ["at any time"]
  • Branch name: renovate/develop-github.com-cloudogu-go-cas-2.x
  • Merge into: develop
  • Upgrade github.com/cloudogu/go-cas to v2.4.0
Update module github.com/vulcand/oxy to v1.4.2 (develop)
  • Schedule: ["at any time"]
  • Branch name: renovate/develop-github.com-vulcand-oxy-1.x
  • Merge into: develop
  • Upgrade github.com/vulcand/oxy to 9260f86ffc5f9fe79432596f3aa9a55e7c5f2b2b
Update module golang.org/x/time to v0.15.0 (develop)
  • Schedule: ["at any time"]
  • Branch name: renovate/develop-golang.org-x-time-0.x
  • Merge into: develop
  • Upgrade golang.org/x/time to v0.15.0
Update module github.com/vulcand/oxy to v2 (develop)
  • Schedule: ["at any time"]
  • Branch name: renovate/develop-github.com-vulcand-oxy-2.x
  • Merge into: develop
  • Upgrade github.com/vulcand/oxy to db4bdb49d5f387df1731b60d6833e0ea605c6c90
Update module gopkg.in/yaml.v2 to v3 (develop)
  • Schedule: ["at any time"]
  • Branch name: renovate/develop-gopkg.in-yaml.v2-3.x
  • Merge into: develop
  • Upgrade gopkg.in/yaml.v2 to v3.0.1
Update github.com/op/go-logging digest to 970db52 (master)
  • Schedule: ["at any time"]
  • Branch name: renovate/master-github.com-op-go-logging-digest
  • Merge into: master
  • Upgrade github.com/op/go-logging to 970db520ece7
Update module github.com/cloudogu/go-cas to v2.4.0 (master)
  • Schedule: ["at any time"]
  • Branch name: renovate/master-github.com-cloudogu-go-cas-2.x
  • Merge into: master
  • Upgrade github.com/cloudogu/go-cas to v2.4.0
Update module github.com/pkg/errors to v0.9.1 (master)
  • Schedule: ["at any time"]
  • Branch name: renovate/master-github.com-pkg-errors-0.x
  • Merge into: master
  • Upgrade github.com/pkg/errors to v0.9.1
Update module github.com/stretchr/testify to v1.11.1 (master)
  • Schedule: ["at any time"]
  • Branch name: renovate/master-github.com-stretchr-testify-1.x
  • Merge into: master
  • Upgrade github.com/stretchr/testify to v1.11.1
Update module github.com/vulcand/oxy to v1.4.2 (master)
  • Schedule: ["at any time"]
  • Branch name: renovate/master-github.com-vulcand-oxy-1.x
  • Merge into: master
  • Upgrade github.com/vulcand/oxy to 9260f86ffc5f9fe79432596f3aa9a55e7c5f2b2b
Update module golang.org/x/time to v0.15.0 (master)
  • Schedule: ["at any time"]
  • Branch name: renovate/master-golang.org-x-time-0.x
  • Merge into: master
  • Upgrade golang.org/x/time to v0.15.0
Update module gopkg.in/yaml.v2 to v2.4.0 (master)
  • Schedule: ["at any time"]
  • Branch name: renovate/master-gopkg.in-yaml.v2-2.x
  • Merge into: master
  • Upgrade gopkg.in/yaml.v2 to v2.4.0
Update module github.com/vulcand/oxy to v2 (master)
  • Schedule: ["at any time"]
  • Branch name: renovate/master-github.com-vulcand-oxy-2.x
  • Merge into: master
  • Upgrade github.com/vulcand/oxy to db4bdb49d5f387df1731b60d6833e0ea605c6c90
Update module gopkg.in/yaml.v2 to v3 (master)
  • Schedule: ["at any time"]
  • Branch name: renovate/master-gopkg.in-yaml.v2-3.x
  • Merge into: master
  • Upgrade gopkg.in/yaml.v2 to v3.0.1

🚸 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 has been generated by Mend Renovate.

@cesmarvin cesmarvin force-pushed the renovate/configure branch from 1ad9164 to b2ee793 Compare July 6, 2026 19:01
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