chore: Configure Renovate #1

Open
renovate-bot wants to merge 22 commits from renovate/configure into main
First-time contributor

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

  • .forgejo/workflows/mock-ci.yml (github-actions)
  • ci-metrics/action.yml (github-actions)
  • .python-version (pyenv)
  • 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
  • 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
  • Update _VERSION variables in Dockerfiles.
  • Remove limit for open PRs at any time.
  • Rate limit PR creation to a maximum of four per hour.
  • Use semantic prefixes for commit messages and PR titles.

What to Expect

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

chore(deps): update python docker tag to v3.14.6
  • Schedule: ["at any time"]
  • Branch name: renovate/python-3.x
  • Merge into: main
  • Upgrade python to 3.14.6
chore(deps): update actions/checkout action to v7

❓ 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. 🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. πŸ“š 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/mock-ci.yml` (github-actions) * `ci-metrics/action.yml` (github-actions) * `.python-version` (pyenv) * `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 - 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 - Update `_VERSION` variables in Dockerfiles. - Remove limit for open PRs at any time. - Rate limit PR creation to a maximum of four per hour. - Use semantic prefixes for commit messages and PR titles. --- ### What to Expect With your current configuration, Renovate will create 2 Pull Requests: <details> <summary>chore(deps): update python docker tag to v3.14.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/python-3.x` - Merge into: `main` - Upgrade python to `3.14.6` </details> <details> <summary>chore(deps): update actions/checkout action to v7</summary> - Schedule: ["at any time"] - Branch name: `renovate/https-stackit-iaas.git.onstackit.cloud-actions-checkout-7.x` - Merge into: `main` - Upgrade [https://stackit-iaas.git.onstackit.cloud/actions/checkout](https://stackit-iaas.git.onstackit.cloud/actions/checkout) to `v7` </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:5651a3c3417c12a47ecfeb61b25a1b7c720ab76d7f5e6ac4ff60a05530dd7a57-->
chore(deps): add renovate.json
Some checks failed
Multi-Job Random Tester / job-alpha (push) Successful in 1s
Multi-Job Random Tester / metrics-summary (push) Failing after 2s
42cd135b13
pr-auto-approve left a comment

Autoapprove by approve-bot

Autoapprove by approve-bot
Author
First-time contributor

Branch Conflicted

⚠️ This PR has a merge conflict which Renovate is unable to automatically resolve, so updates to this PR description are now paused. Please resolve the merge conflict manually.

### Branch Conflicted ⚠️ This PR has a merge conflict which Renovate is unable to automatically resolve, so updates to this PR description are now paused. Please resolve the merge conflict manually.
Some checks failed
Multi-Job Random Tester / job-alpha (push) Successful in 1s
Multi-Job Random Tester / metrics-summary (push) Failing after 2s
This pull request has changes conflicting with the target branch.
  • .forgejo/workflows/mock-ci.yml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

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 STACKIT Git.

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
actions/ci-metrics-action!1
No description provided.