Configure Renovate #1

Open
renovate[bot] wants to merge 1 commit from renovate/configure into master
renovate[bot] commented 2024-07-06 00:59:13 +01:00 (Migrated from github.com)

Mend 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/publish.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 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 5 Pull Requests:

Update dependency jinja2 to v3.1.4
  • Schedule: ["at any time"]
  • Branch name: renovate/jinja2-3.x-lockfile
  • Merge into: master
  • Upgrade jinja2 to 3.1.4
Update dependency fastapi to ^0.111.0
  • Schedule: ["at any time"]
  • Branch name: renovate/fastapi-0.x
  • Merge into: master
  • Upgrade fastapi to ^0.111.0
Update dependency pydantic-settings to v2.3.4
  • Schedule: ["at any time"]
  • Branch name: renovate/pydantic-settings-2.x-lockfile
  • Merge into: master
  • Upgrade pydantic-settings to 2.3.4
Update dependency ruff to ^0.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/ruff-0.x
  • Merge into: master
  • Upgrade ruff to ^0.5.0
Update dependency uvicorn to ^0.30.0
  • Schedule: ["at any time"]
  • Branch name: renovate/uvicorn-0.x
  • Merge into: master
  • Upgrade uvicorn to ^0.30.0

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

[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) Welcome to [Renovate](https://togithub.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 * `.github/workflows/publish.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 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 5 Pull Requests: <details> <summary>Update dependency jinja2 to v3.1.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/jinja2-3.x-lockfile` - Merge into: `master` - Upgrade [jinja2](https://togithub.com/pallets/jinja) to `3.1.4` </details> <details> <summary>Update dependency fastapi to ^0.111.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/fastapi-0.x` - Merge into: `master` - Upgrade [fastapi](https://togithub.com/tiangolo/fastapi) to `^0.111.0` </details> <details> <summary>Update dependency pydantic-settings to v2.3.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/pydantic-settings-2.x-lockfile` - Merge into: `master` - Upgrade [pydantic-settings](https://togithub.com/pydantic/pydantic-settings) to `2.3.4` </details> <details> <summary>Update dependency ruff to ^0.5.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/ruff-0.x` - Merge into: `master` - Upgrade [ruff](https://togithub.com/astral-sh/ruff) to `^0.5.0` </details> <details> <summary>Update dependency uvicorn to ^0.30.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/uvicorn-0.x` - Merge into: `master` - Upgrade [uvicorn](https://togithub.com/encode/uvicorn) to `^0.30.0` </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://togithub.com/renovatebot/renovate/discussions). --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/cpressland/carousel). <!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
Commenting is not possible because the repository is archived.
No description provided.