Configure Renovate #2

Merged

mg merged 1 commit from renovate/configure into master

2025-11-12 20:28:37 +01:00

renovate commented

2025-11-12 20:09:29 +01:00

Collaborator

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

requirements.yaml (ansible-galaxy)
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.
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.

🔡 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 5 Pull Requests:

Update dependency community.crypto to v3.0.5

Schedule: ["at any time"]
Branch name: renovate/community.crypto-3.x
Merge into: master
Upgrade community.crypto to 803635125670f17b0b09a154bfbc472f97d50c4e350861347e156ba87707cb36

Update dependency community.docker to v5.0.1

Schedule: ["at any time"]
Branch name: renovate/community.docker-5.x
Merge into: master
Upgrade community.docker to 2bea2752ff66b929d78e2e2e7b4a30e640bd5d89b6390e9b579210ae2a43d9e7

Update dependency viczem.keepass to v0.7.5

Schedule: ["at any time"]
Branch name: renovate/viczem.keepass-0.x
Merge into: master
Upgrade viczem.keepass to 8ca6158ce6e11e40bfb737e2863f12481be38a183f464f787b5a0e61f666af52

Update dependency community.general to v11.4.1

Schedule: ["at any time"]
Branch name: renovate/community.general-11.x
Merge into: master
Upgrade community.general to 618b2cad75706f2939a5607271bfdcf4a10d3b6f3fe792e1569910c270485399

Update dependency community.general to v12

Schedule: ["at any time"]
Branch name: renovate/community.general-12.x
Merge into: master
Upgrade community.general to b396c86c3dd95281d8481401009dd1cbdbc4e71e2dcf8218819ae388ab6656d9

🚸 Branch 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 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 * `requirements.yaml` (ansible-galaxy) * `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. - 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. 🔡 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 5 Pull Requests: <details> <summary>Update dependency community.crypto to v3.0.5</summary> - Schedule: ["at any time"] - Branch name: `renovate/community.crypto-3.x` - Merge into: `master` - Upgrade [community.crypto](https://github.com/ansible-collections/community.crypto) to `803635125670f17b0b09a154bfbc472f97d50c4e350861347e156ba87707cb36` </details> <details> <summary>Update dependency community.docker to v5.0.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/community.docker-5.x` - Merge into: `master` - Upgrade [community.docker](https://github.com/ansible-collections/community.docker) to `2bea2752ff66b929d78e2e2e7b4a30e640bd5d89b6390e9b579210ae2a43d9e7` </details> <details> <summary>Update dependency viczem.keepass to v0.7.5</summary> - Schedule: ["at any time"] - Branch name: `renovate/viczem.keepass-0.x` - Merge into: `master` - Upgrade [viczem.keepass](https://github.com/viczem/ansible-keepass) to `8ca6158ce6e11e40bfb737e2863f12481be38a183f464f787b5a0e61f666af52` </details> <details> <summary>Update dependency community.general to v11.4.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/community.general-11.x` - Merge into: `master` - Upgrade [community.general](https://github.com/ansible-collections/community.general) to `618b2cad75706f2939a5607271bfdcf4a10d3b6f3fe792e1569910c270485399` </details> <details> <summary>Update dependency community.general to v12</summary> - Schedule: ["at any time"] - Branch name: `renovate/community.general-12.x` - Merge into: `master` - Upgrade [community.general](https://github.com/ansible-collections/community.general) to `b396c86c3dd95281d8481401009dd1cbdbc4e71e2dcf8218819ae388ab6656d9` </details> 🚸 Branch 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](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 added 1 commit

2025-11-12 20:09:29 +01:00