Configure Renovate

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

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

• .github/workflows/build_wheels.yml (github-actions)
• .github/workflows/release.yaml (github-actions)
• .github/workflows/run_tests.yml (github-actions)
• .github/workflows/style.yaml (github-actions)
• pyproject.toml (pep621)
• docs/requirements.in (pip-compile)
• .github/workflows/requirements-test.in (pip-compile)
• 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
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• 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.
• Disable semantic prefixes for commit messages and PR titles.
• Apply label dependencies to PRs.

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

Pin actions/checkout action to 692973e

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Upgrade actions/checkout to 692973e3d937129bcbf40652eb9f2f61becf3332

Update actions/checkout action to v4.3.0

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: main
• Upgrade actions/checkout to 08eba0b27e820071cde6df949e0beb9ba4906955

Update actions/checkout action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-5.x
• Merge into: main
• Upgrade actions/checkout to 08c6903cd8c0fde910a37f88322edcfb5dd907a8

Lock file maintenance

• Schedule: ["before 4am on monday"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

Refresh pip-compile outputs

• Schedule: ["before 4am on monday"]
• Branch name: renovate/pip-compile-refresh
• Merge into: main
• Regenerate lock files to use latest dependency versions

🚸 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 was generated by Mend Renovate. View the repository job log.

[DomFijan]

@joaander I managed to get Windows testing to pass. I also fixed the automatic changelog notes extraction. Could you take one last look at all the CI changes to see if I missed something?

[joaander]

This will get refreshed to the latest unless you add a pin in requirements.in.

If you add a pin in requirements.in, then you'll get a specific pull request to update this package to the latest.

[DomFijan]

I think I changed this back to the latest version in most recent commits. I was testing if the Windows issue was related to the version of pytest-rerunfailures, but that was not the case. I think the latest CI run with newest version successfully, so I don't think I need a pin here.

[joaander]

OK. That commit was the one GitHub showed me in the notification - not your message.