Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Configure Renovate #1

Merged
merged 1 commit into from
Oct 23, 2024
Merged

chore: Configure Renovate #1

merged 1 commit into from
Oct 23, 2024

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 23, 2024

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

  • .devcontainer/Dockerfile (dockerfile)
  • .github/workflows/autocloser.yaml (github-actions)
  • .github/workflows/lintpr.yaml (github-actions)
  • .github/workflows/moderate.yaml (github-actions)
  • .github/workflows/pre-commit.yml (github-actions)
  • .github/workflows/semantic_release.yml (github-actions)
  • .github/workflows/stale.yml (github-actions)
  • .github/workflows/validate.yaml (github-actions)
  • pyproject.toml (pep621)
  • pyproject.toml (poetry)

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 (except for nuget) 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.

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

chore(deps): update dependency pytest-homeassistant-custom-component to v0.13.174
chore(deps): update dependency safety to v3.2.8
  • Schedule: ["at any time"]
  • Branch name: renovate/safety-3.x-lockfile
  • Merge into: dev
  • Upgrade safety to 3.2.8
chore(deps): update dependency black to v24.10.0
  • Schedule: ["at any time"]
  • Branch name: renovate/black-24.x-lockfile
  • Merge into: dev
  • Upgrade black to 24.10.0
chore(deps): update dependency homeassistant to v2023.12.4
  • Schedule: ["at any time"]
  • Branch name: renovate/homeassistant-2023.x-lockfile
  • Merge into: dev
  • Upgrade homeassistant to 2023.12.4
chore(deps): update dependency prospector to v1.12.1
  • Schedule: ["at any time"]
  • Branch name: renovate/prospector-1.x-lockfile
  • Merge into: dev
  • Upgrade prospector to 1.12.1
chore(deps): update dependency pytest to v7.4.4
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-7.x-lockfile
  • Merge into: dev
  • Upgrade pytest to 7.4.4
chore(deps): update dependency pyupgrade to v3.19.0
  • Schedule: ["at any time"]
  • Branch name: renovate/pyupgrade-3.x-lockfile
  • Merge into: dev
  • Upgrade pyupgrade to 3.19.0
chore(deps): update mcr.microsoft.com/devcontainers/python docker tag to v3.12
  • Schedule: ["at any time"]
  • Branch name: renovate/mcr.microsoft.com-devcontainers-python-3.x
  • Merge into: dev
  • Upgrade mcr.microsoft.com/devcontainers/python to 3.12-bullseye
chore(deps): update roots/issue-closer action to v1.2
  • Schedule: ["at any time"]
  • Branch name: renovate/roots-issue-closer-1.x
  • Merge into: dev
  • Upgrade roots/issue-closer to v1.2
fix(deps): update dependency aiohttp to v3.10.10
  • Schedule: ["at any time"]
  • Branch name: renovate/aiohttp-3.x-lockfile
  • Merge into: dev
  • Upgrade aiohttp to 3.10.10
chore(deps): update actions/cache action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-cache-4.x
  • Merge into: dev
  • Upgrade actions/cache to v4
chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: dev
  • Upgrade actions/checkout to v4
chore(deps): update actions/setup-python action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-python-5.x
  • Merge into: dev
  • Upgrade actions/setup-python to v5
chore(deps): update actions/stale action to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-stale-9.x
  • Merge into: dev
  • Upgrade actions/stale to v9
chore(deps): update amannn/action-semantic-pull-request action to v5
chore(deps): update dependency homeassistant to v2024
  • Schedule: ["at any time"]
  • Branch name: renovate/homeassistant-2024.x-lockfile
  • Merge into: dev
  • Upgrade homeassistant to 2024.10.3
chore(deps): update dependency pre-commit to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/pre-commit-4.x-lockfile
  • Merge into: dev
  • Upgrade pre-commit to 4.0.1
chore(deps): update dependency pytest to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-8.x-lockfile
  • Merge into: dev
  • Upgrade pytest to 8.3.3
chore(deps): update dependency pytest-cov to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-cov-5.x-lockfile
  • Merge into: dev
  • Upgrade pytest-cov to 5.0.0
chore(deps): update relekang/python-semantic-release action to v9

🚸 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.

@brianegge brianegge merged commit b9998e4 into dev Oct 23, 2024
@renovate renovate bot deleted the renovate/configure branch October 23, 2024 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant