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

Configure Renovate #5

Closed
wants to merge 1 commit into from
Closed

Conversation

elastic-renovate-prod[bot]
Copy link

@elastic-renovate-prod elastic-renovate-prod bot commented Aug 8, 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

  • docker-compose.yml (docker-compose)
  • Dockerfile (dockerfile)
  • .github/workflows/publish.yml (github-actions)
  • pyproject.toml (pep621)
  • pyproject.toml (poetry)
  • Dockerfile (regex)
  • Dockerfile (regex)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Chainguard Renovate configuration (https://ela.st/wolfi)
  • Chainguard Renovate configuration (https://ela.st/wolfi)
  • 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.
  • Pin Docker digests.
  • Pin github-action digests.
  • Pin dependency versions for devDependencies.
  • Preset with best practices from the Renovate maintainers. Recommended for advanced users, who want to follow our best practices.
  • Shared Renovate configuration for an out-of-the-box set of defaults for Renovate at Elastic

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

Pin dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/pin-dependencies
  • Merge into: main
  • Upgrade actions/checkout to ee0669bd1cc54295c223e0bb666b733df41de1c5
  • Upgrade docker/build-push-action to ac9327eae2b366085ac7f6a2d02df8aa8ead720a
  • Upgrade docker/login-action to dd4fa0671be5250ee6f50aedf4cb05514abda2c7
  • Upgrade python to sha256:49f94609e5a997dc16086a66ac9664591854031d48e375945a9dbf4d1d53abbc
Update dependency ruamel.yaml to ^0.18.0
  • Schedule: ["at any time"]
  • Branch name: renovate/ruamel.yaml-0.x
  • Merge into: main
  • Upgrade ruamel.yaml to ^0.18.0
Update dependency vt-py to ^0.18.0
  • Schedule: ["at any time"]
  • Branch name: renovate/vt-py-0.x
  • Merge into: main
  • Upgrade vt-py to ^0.18.0
Update python Docker tag to v3.13
  • Schedule: ["at any time"]
  • Branch name: renovate/python-3.x
  • Merge into: main
  • Upgrade python to sha256:2ec5a4a5c3e919570f57675471f081d6299668d909feabd8d4803c6c61af666c
Update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to eef61447b9ff4aafe5dcd4e0bbf5d482be7e7871
Update dependency ecs-logging to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/ecs-logging-2.x
  • Merge into: main
  • Upgrade ecs-logging to ^2.0.0
Update dependency flake8 to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/flake8-7.x
  • Merge into: main
  • Upgrade flake8 to <8
Update dependency mypy to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/mypy-1.x
  • Merge into: main
  • Upgrade mypy to ^1.0.0
Update dependency pycti to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/pycti-6.x
  • Merge into: main
  • Upgrade pycti to ^6.0.0
Update dependency pyproject-flake8 to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/pyproject-flake8-7.x
  • Merge into: main
  • Upgrade pyproject-flake8 to ^7.0.0
Update dependency pytest to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-8.x
  • Merge into: main
  • Upgrade pytest to ^8.0.0
Update dependency pytest-isort to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/pytest-isort-4.x
  • Merge into: main
  • Upgrade pytest-isort to ^4.0.0
Update docker/build-push-action action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-6.x
  • Merge into: main
  • Upgrade docker/build-push-action to 4f58ea79222b3b9dc2c8bbdd6debcef730109a75
Update docker/login-action action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-3.x
  • Merge into: main
  • Upgrade docker/login-action to 9780b0c442fbb1117ed29e0efdff1e18412f7567

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

@nuugen nuugen closed this Oct 16, 2024
@nuugen
Copy link
Member

nuugen commented Oct 16, 2024

Closing stale Renovate Onboarding PR (unmerged since creation >30 days ago).

@elastic-renovate-prod
Copy link
Author

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.

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