chore: Configure Renovate #43

Merged

renovate[bot] merged 2 commits from renovate/configure into main

2023-11-27 02:50:29 +00:00

renovate[bot] commented

2023-11-27 02:44:04 +00:00

(Migrated from github.com)

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

backend/Dockerfile (dockerfile)
.github/workflows/backend-pipeline.yml (github-actions)
.github/workflows/ci.yml (github-actions)
.github/workflows/frontend-pipeline.yml (github-actions)
backend/pyproject.toml (pep621)
backend/requirements.txt (pip_requirements)
backend/.python-version (pyenv)

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.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 5 Pull Requests:

chore(deps): update python docker tag

Schedule: ["at any time"]
Branch name: renovate/python-3.x
Merge into: main
Upgrade python to 3.12.0
Upgrade python to 3.12-slim

chore(deps): update actions/checkout action to v4

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

chore(deps): update actions/github-script action to v7

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

chore(deps): update actions/setup-node action to v4

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

chore(deps): update actions/setup-python action to v4

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

🚸 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 logo banner](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 * `backend/Dockerfile` (dockerfile) * `.github/workflows/backend-pipeline.yml` (github-actions) * `.github/workflows/ci.yml` (github-actions) * `.github/workflows/frontend-pipeline.yml` (github-actions) * `backend/pyproject.toml` (pep621) * `backend/requirements.txt` (pip_requirements) * `backend/.python-version` (pyenv) ### 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. 🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the `renovate.json` in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs. --- ### What to Expect With your current configuration, Renovate will create 5 Pull Requests: <details> <summary>chore(deps): update python docker tag</summary> - Schedule: ["at any time"] - Branch name: `renovate/python-3.x` - Merge into: `main` - Upgrade python to `3.12.0` - Upgrade python to `3.12-slim` </details> <details> <summary>chore(deps): update actions/checkout action to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-checkout-4.x` - Merge into: `main` - Upgrade [actions/checkout](https://togithub.com/actions/checkout) to `v4` </details> <details> <summary>chore(deps): update actions/github-script action to v7</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-github-script-7.x` - Merge into: `main` - Upgrade [actions/github-script](https://togithub.com/actions/github-script) to `v7` </details> <details> <summary>chore(deps): update actions/setup-node action to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-setup-node-4.x` - Merge into: `main` - Upgrade [actions/setup-node](https://togithub.com/actions/setup-node) to `v4` </details> <details> <summary>chore(deps): update actions/setup-python action to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/actions-setup-python-4.x` - Merge into: `main` - Upgrade [actions/setup-python](https://togithub.com/actions/setup-python) to `v4` </details> <br /> 🚸 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/mcataford/rotini).

This repo is archived. You cannot comment on pull requests.

No reviewers