Configure Renovate

[renovate]

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.yml (github-actions)
• .github/workflows/crowdin_download.yml (github-actions)
• .github/workflows/crowdin_upload.yml (github-actions)
• .github/workflows/lint.yml (github-actions)
• .github/workflows/test.yml (github-actions)
• pyproject.toml (pep621)
• requirements.txt (pip_requirements)
• setup.py (pip_setup)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• 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 directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Automerge patch upgrades if they pass tests.
• Automerge digest upgrades if they pass tests.
• If automerging, push the new commit directly to the base branch (no PR).
• Run lock file maintenance (updates) early Monday mornings.
• Update _VERSION variables in Dockerfiles.
• Japan7 default configuration for Renovate

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

Update dependency sphinx to v4.5.0

• Schedule: ["at any time"]
• Branch name: renovate/sphinx-4.x
• Merge into: master
• Upgrade sphinx to ==4.5.0

Update actions/checkout action to v4

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

Update actions/github-script action to v7

• Schedule: ["at any time"]
• Branch name: renovate/actions-github-script-7.x
• Merge into: master
• Upgrade actions/github-script to v7

Update actions/setup-node action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-4.x
• Merge into: master
• Upgrade actions/setup-node to v4

Update actions/setup-python action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-python-5.x
• Merge into: master
• Upgrade actions/setup-python to v5

Update dependency sphinx to v7

• Schedule: ["at any time"]
• Branch name: renovate/sphinx-7.x
• Merge into: master
• Upgrade sphinx to ==7.2.6

Update jakebailey/pyright-action action to v2

• Schedule: ["at any time"]
• Branch name: renovate/jakebailey-pyright-action-2.x
• Merge into: master
• Upgrade jakebailey/pyright-action to v2

Update peter-evans/create-pull-request action to v6

• Schedule: ["at any time"]
• Branch name: renovate/peter-evans-create-pull-request-6.x
• Merge into: master
• Upgrade peter-evans/create-pull-request to v6

Lock file maintenance

• Schedule: ["before 4am on Monday"]
• Branch name: renovate/lock-file-maintenance
• Merge into: master
• 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.