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 #1128

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate-bot
Copy link

@renovate-bot renovate-bot commented May 1, 2024

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

  • cloudbuild.yaml (cloudbuild)
  • ci/Dockerfile.cicd (dockerfile)
  • samples/cloud_run/Dockerfile (dockerfile)
  • samples/cloud_run_jobs/Dockerfile (dockerfile)
  • samples/docker/Dockerfile (dockerfile)
  • samples/cloud_functions/requirements.txt (pip_requirements)
  • setup.py (pip_setup)
  • terraform/main.tf (terraform)

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 26 Pull Requests:

chore(deps): update dependency grpcio [security]
  • Branch name: renovate/pypi-grpcio-vulnerability
  • Merge into: develop
  • Upgrade grpcio to ==1.64.0
  • Upgrade grpcio to ==1.53.2
chore(deps): update dependency ibis-framework [security]
  • Branch name: renovate/pypi-ibis-framework-vulnerability
  • Merge into: develop
  • Upgrade ibis-framework to ==9.0.0
  • Upgrade ibis-framework to ==7.1.0
chore(deps): update dependency flask to v2.3.3
  • Schedule: ["at any time"]
  • Branch name: renovate/flask-2.x
  • Merge into: develop
  • Upgrade Flask to ==2.3.3
chore(deps): update dependency jellyfish to v1.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/jellyfish-1.x
  • Merge into: develop
  • Upgrade jellyfish to ==1.0.3
chore(deps): update dependency psycopg2-binary to v2.9.9
  • Schedule: ["at any time"]
  • Branch name: renovate/psycopg2-binary-2.x
  • Merge into: develop
  • Upgrade psycopg2-binary to ==2.9.9
chore(deps): update dependency pyarrow to v14.0.2
  • Schedule: ["at any time"]
  • Branch name: renovate/pyarrow-14.x
  • Merge into: develop
  • Upgrade pyarrow to ==14.0.2
chore(deps): update dependency pydata-google-auth to v1.8.2
  • Schedule: ["at any time"]
  • Branch name: renovate/pydata-google-auth-1.x
  • Merge into: develop
  • Upgrade pydata-google-auth to ==1.8.2
chore(deps): update dependency pymysql to v1.1.1
  • Schedule: ["at any time"]
  • Branch name: renovate/pymysql-1.x
  • Merge into: develop
  • Upgrade PyMySQL to ==1.1.1
chore(deps): update dependency pyyaml to v6.0.1
  • Schedule: ["at any time"]
  • Branch name: renovate/pyyaml-6.x
  • Merge into: develop
  • Upgrade PyYAML to ==6.0.1
chore(deps): update dependency sqlalchemy to v1.4.52
  • Schedule: ["at any time"]
  • Branch name: renovate/sqlalchemy-1.x
  • Merge into: develop
  • Upgrade SQLAlchemy to ==1.4.52
chore(deps): update dependency attrs to v23.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/attrs-23.x
  • Merge into: develop
  • Upgrade attrs to ==23.2.0
chore(deps): update dependency google-api-python-client to v2.129.0
  • Schedule: ["at any time"]
  • Branch name: renovate/google-api-python-client-2.x
  • Merge into: develop
  • Upgrade google-api-python-client to ==2.129.0
chore(deps): update dependency google-cloud-bigquery to v3.23.1
  • Schedule: ["at any time"]
  • Branch name: renovate/google-cloud-bigquery-3.x
  • Merge into: develop
  • Upgrade google-cloud-bigquery to ==3.23.1
chore(deps): update dependency google-cloud-bigquery-storage to v2.25.0
  • Schedule: ["at any time"]
  • Branch name: renovate/google-cloud-bigquery-storage-2.x
  • Merge into: develop
  • Upgrade google-cloud-bigquery-storage to ==2.25.0
chore(deps): update dependency google-cloud-secret-manager to <=2.20.0
  • Schedule: ["at any time"]
  • Branch name: renovate/google-cloud-secret-manager-2.x
  • Merge into: develop
  • Upgrade google-cloud-secret-manager to <=2.20.0
chore(deps): update dependency google-cloud-spanner to v3.46.0
  • Schedule: ["at any time"]
  • Branch name: renovate/google-cloud-spanner-3.x
  • Merge into: develop
  • Upgrade google-cloud-spanner to ==3.46.0
chore(deps): update dependency google-cloud-storage to v2.16.0
  • Schedule: ["at any time"]
  • Branch name: renovate/google-cloud-storage-2.x
  • Merge into: develop
  • Upgrade google-cloud-storage to ==2.16.0
chore(deps): update dependency impyla to v0.19.0
  • Schedule: ["at any time"]
  • Branch name: renovate/impyla-0.x
  • Merge into: develop
  • Upgrade impyla to ==0.19.0
chore(deps): update dependency lazy-object-proxy to v1.10.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lazy-object-proxy-1.x
  • Merge into: develop
  • Upgrade lazy-object-proxy to ==1.10.0
chore(deps): update dependency marshmallow to v3.21.2
  • Schedule: ["at any time"]
  • Branch name: renovate/marshmallow-3.x
  • Merge into: develop
  • Upgrade marshmallow to ==3.21.2
chore(deps): update dependency proto-plus to v1.23.0
  • Schedule: ["at any time"]
  • Branch name: renovate/proto-plus-1.x
  • Merge into: develop
  • Upgrade proto-plus to ==1.23.0
chore(deps): update python docker tag
  • Schedule: ["at any time"]
  • Branch name: renovate/python-3.x
  • Merge into: develop
  • Upgrade python to 3.12.3-slim
  • Upgrade python to 3.12-slim
chore(deps): update dependency flask to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/flask-3.x
  • Merge into: develop
  • Upgrade Flask to ==3.0.3
chore(deps): update dependency pandas to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/pandas-2.x
  • Merge into: develop
  • Upgrade pandas to ==2.2.2
chore(deps): update dependency pyarrow to v16
  • Schedule: ["at any time"]
  • Branch name: renovate/pyarrow-16.x
  • Merge into: develop
  • Upgrade pyarrow to ==16.1.0
chore(deps): update dependency sqlalchemy to v2.0.30
  • Schedule: ["at any time"]
  • Branch name: renovate/sqlalchemy-2.x
  • Merge into: develop
  • Upgrade SQLAlchemy to ==2.0.30

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

Copy link

conventional-commit-lint-gcf bot commented May 1, 2024

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant