chore: Configure Renovate #1

Merged
onlyhavecans merged 1 commit from renovate/configure into main 2026-01-10 15:32:43 -08:00
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.


Detected Package Files

  • .forgejo/workflows/ci.yml (github-actions)
  • go.mod (gomod)
  • renovate.json (renovate-config-presets)

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 GitHub.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
  • 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.
  • Use semantic prefixes for commit messages and PR titles.

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


What to Expect

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

chore(deps): pin dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: main
  • Upgrade actions/checkout to 8e8c483db84b4bee98b60c0593521ed34d9990e8
  • Upgrade actions/golangci-lint to 1e7e51e771db61008b38414a730f564565cf7c20
  • Upgrade actions/setup-go to 4dc6199c7b1a012772edbd06daecab0f50c9053c
fix(deps): update module github.com/spf13/viper to v1.21.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-spf13-viper-1.x
  • Merge into: main
  • Upgrade github.com/spf13/viper to v1.21.0
fix(deps): update module github.com/stretchr/testify to v1.11.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-stretchr-testify-1.x
  • Merge into: main
  • Upgrade github.com/stretchr/testify to v1.11.1

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 Renovate Bot.

Welcome to [Renovate](https://github.com/renovatebot/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. --- ### Detected Package Files * `.forgejo/workflows/ci.yml` (github-actions) * `go.mod` (gomod) * `renovate.json` (renovate-config-presets) ### 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 GitHub.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 - 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. - Use semantic prefixes for commit messages and PR titles. 🔡 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. --- ### What to Expect With your current configuration, Renovate will create 3 Pull Requests: <details> <summary>chore(deps): pin dependencies</summary> - Schedule: ["at any time"] - Branch name: `renovate/pin-dependencies` - Merge into: `main` - Upgrade [actions/checkout](https://onlyhavecans.works/actions/checkout) to `8e8c483db84b4bee98b60c0593521ed34d9990e8` - Upgrade [actions/golangci-lint](https://onlyhavecans.works/actions/golangci-lint) to `1e7e51e771db61008b38414a730f564565cf7c20` - Upgrade [actions/setup-go](https://onlyhavecans.works/actions/setup-go) to `4dc6199c7b1a012772edbd06daecab0f50c9053c` </details> <details> <summary>fix(deps): update module github.com/spf13/viper to v1.21.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-spf13-viper-1.x` - Merge into: `main` - Upgrade [github.com/spf13/viper](https://github.com/spf13/viper) to `v1.21.0` </details> <details> <summary>fix(deps): update module github.com/stretchr/testify to v1.11.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-stretchr-testify-1.x` - Merge into: `main` - Upgrade [github.com/stretchr/testify](https://github.com/stretchr/testify) to `v1.11.1` </details> --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-config-hash:60ae7e708ff8835679ac3a90548977c50f368aa53ce48909a5fe28762009a8de-->
chore(deps): add renovate.json
Some checks failed
CI / lint (pull_request) Failing after 2s
CI / test (pull_request) Failing after 28s
CI / build (pull_request) Has been skipped
3a3f7e2e79
onlyhavecans force-pushed renovate/configure from 3a3f7e2e79
Some checks failed
CI / lint (pull_request) Failing after 2s
CI / test (pull_request) Failing after 28s
CI / build (pull_request) Has been skipped
to dcf0380e22
All checks were successful
CI / lint (pull_request) Successful in 25s
CI / test (pull_request) Successful in 9m56s
CI / build (pull_request) Successful in 23s
2026-01-10 13:44:48 -08:00
Compare
onlyhavecans referenced this pull request from a commit 2026-01-10 15:32:43 -08:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tools/muck!1
No description provided.