chore: Configure Renovate #6

Open
renovate wants to merge 3 commits from renovate/configure into main
Member

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

  • .forgejo/workflows/ci.yml (github-actions)
  • .forgejo/workflows/release.yml (github-actions)
  • .mise.toml (mise)
  • package.json (npm)
  • renovate.json (renovate-config)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Forgejo-platform overrides. Two things the platform gets wrong on its own. (1) Forgejo Actions don't populate the commit-status API that Renovate's prCreation:not-pending reads (GET /commits/{sha}/status is empty even on green CI), so not-pending never resolves and PRs hang the full prNotPendingHours. Force immediate PR creation on the Forgejo path. force: because consumers extend :default (not-pending) at the repo level, which only an admin-level force overrides. (2) The github-actions manager assigns datasource github-tags unconditionally, so a uses: pointing at a Forgejo-native repo is resolved against api.github.com. Where a github.com twin exists but carries no tags, that returns an empty list rather than an error — the pin freezes silently. The customManagers below read webgrip/* pins from Forgejo instead, in both shapes consumers write: digest plus version comment, and bare version tag.
  • 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
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic prefixes for commit messages and PR titles.
  • Separate each major version of dependencies into individual branches/PRs.
  • Raise PR when vulnerability alerts are detected.
  • Evaluate schedules according to timezone Europe/Amsterdam.
  • Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  • Show all Merge Confidence badges for pull requests.
  • Webgrip org default Renovate preset — strict, conservative defaults for all repositories. Graduated release soak times, per-type semantic commits and labels, OSV vulnerability alerts, and Merge Confidence badges included. Schedule is 'at any time' since 2026-09-18: with dashboard approval required for every update type, nothing opens unattended anyway, so a window only delayed work a human had already asked for — and Renovate does not persist an approval it cannot act on, so a tick made outside the window could be silently discarded (see rule 12). It also fought the move to hourly runs, which was made to cut exactly this kind of latency. A repo that wants quiet hours can set its own schedule.

What to Expect

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

ci(actions): Pin actions/checkout action to v5.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: main
  • Pin actions/checkout to fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09
ci(actions): Update actions/checkout action ( v5.1.0 ➔ v6.1.0 )
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to d23441a48e516b6c34aea4fa41551a30e30af803
ci(actions): Update actions/checkout action ( v5.1.0 ➔ v7.0.1 )
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-7.x
  • Merge into: main
  • Upgrade actions/checkout to 3d3c42e5aac5ba805825da76410c181273ba90b1
chore(deps): lock file maintenance
  • Schedule: ["* 0-3 1 * *"]
  • 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.

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. 🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request. 📚 See our [Reading List](https://docs.renovatebot.com/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 * `.forgejo/workflows/ci.yml` (github-actions) * `.forgejo/workflows/release.yml` (github-actions) * `.mise.toml` (mise) * `package.json` (npm) * `renovate.json` (renovate-config) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - Forgejo-platform overrides. Two things the platform gets wrong on its own. (1) Forgejo Actions don't populate the commit-status API that Renovate's prCreation:not-pending reads (GET /commits/{sha}/status is empty even on green CI), so not-pending never resolves and PRs hang the full prNotPendingHours. Force immediate PR creation on the Forgejo path. force: because consumers extend :default (not-pending) at the repo level, which only an admin-level force overrides. (2) The github-actions manager assigns datasource github-tags unconditionally, so a `uses:` pointing at a Forgejo-native repo is resolved against api.github.com. Where a github.com twin exists but carries no tags, that returns an empty list rather than an error — the pin freezes silently. The customManagers below read webgrip/* pins from Forgejo instead, in both shapes consumers write: digest plus version comment, and bare version tag. - 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 - Enable Renovate Dependency Dashboard creation. - Use semantic prefixes for commit messages and PR titles. - Separate each `major` version of dependencies into individual branches/PRs. - Raise PR when vulnerability alerts are detected. - Evaluate schedules according to timezone `Europe/Amsterdam`. - Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides. - Show all Merge Confidence badges for pull requests. - Webgrip org default Renovate preset — strict, conservative defaults for all repositories. Graduated release soak times, per-type semantic commits and labels, OSV vulnerability alerts, and Merge Confidence badges included. Schedule is 'at any time' since 2026-09-18: with dashboard approval required for every update type, nothing opens unattended anyway, so a window only delayed work a human had already asked for — and Renovate does not persist an approval it cannot act on, so a tick made outside the window could be silently discarded (see rule 12). It also fought the move to hourly runs, which was made to cut exactly this kind of latency. A repo that wants quiet hours can set its own schedule. --- ### What to Expect With your current configuration, Renovate will create 4 Pull Requests: <details> <summary>ci(actions): Pin actions/checkout action to v5.1.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/pin-dependencies` - Merge into: `main` - Pin [actions/checkout](https://github.com/actions/checkout) to `fbc6f3992d24b796d5a048ff273f7fcc4a7b6c09` </details> <details> <summary>ci(actions): Update actions/checkout action ( v5.1.0 ➔ v6.1.0 )</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-6.x` - Merge into: `main` - Upgrade [actions/checkout](https://github.com/actions/checkout) to `d23441a48e516b6c34aea4fa41551a30e30af803` </details> <details> <summary>ci(actions): Update actions/checkout action ( v5.1.0 ➔ v7.0.1 )</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-7.x` - Merge into: `main` - Upgrade [actions/checkout](https://github.com/actions/checkout) to `3d3c42e5aac5ba805825da76410c181273ba90b1` </details> <details> <summary>chore(deps): lock file maintenance</summary> - Schedule: ["* 0-3 1 * *"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `main` - Regenerate lock files to use latest dependency versions </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 [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-config-hash:1f6fc0bcbdbe918793dadca77a7a56065c83b9731f4206ce6653b11fdd8a0b1b-->
chore(deps): add renovate.json
Some checks failed
CI / Manifests, dist & plugin tests (pull_request) Failing after 9s
06cf91e129
chore(renovate): pin de presetverwijzing
Some checks failed
CI / Manifests, dist & plugin tests (pull_request) Failing after 20s
7dbb355e86
Renovate onboardt met een kale `local>webgrip/renovate-config`, maar default.json
draagt twee regels die alleen tegen een gepinde verwijzing betekenis hebben: een
soak-uitzondering voor preset-updates (bestaat alleen als er een versie te bumpen
valt) en een pinDigests: false waarvan de beschrijving zegt dat de verwijzing 'is
already pinned to a protected semver release tag'.

Ongepind ziet deze repo het preset nooit op zijn dashboard. De onboarding zelf is
rechtgezet in homelab-cluster d9169897.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
merge main: marketplace.json sync
All checks were successful
CI / Manifests, dist & plugin tests (pull_request) Successful in 27s
368f7a4a51
All checks were successful
CI / Manifests, dist & plugin tests (pull_request) Successful in 27s
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/configure:renovate/configure
git switch renovate/configure

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff renovate/configure
git switch renovate/configure
git rebase main
git switch main
git merge --ff-only renovate/configure
git switch renovate/configure
git rebase main
git switch main
git merge --no-ff renovate/configure
git switch main
git merge --squash renovate/configure
git switch main
git merge --ff-only renovate/configure
git switch main
git merge renovate/configure
git push origin main
Sign in to join this conversation.
No reviewers
No labels
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
webgrip/ai-skills!6
No description provided.