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

Closed
wants to merge 1 commit into from

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

  • .github/workflows/labeler.yml (github-actions)
  • .github/workflows/test.yml (github-actions)
  • package.json (npm)

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

chore(deps): pin dependencies
chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • Upgrade actions/checkout to eef61447b9ff4aafe5dcd4e0bbf5d482be7e7871
chore(deps): update actions/setup-node action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: master
  • Upgrade actions/setup-node to 0a44ba7841725637a19e28fa30b79a866c81b0a6
chore(deps): update dependency tape to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/tape-5.x
  • Merge into: master
  • Upgrade tape to ^5.0.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 Renovate Bot.

@github-actions github-actions bot added the agent-nodejs Make available for APM Agents project planning. label Aug 8, 2024
@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
agent-nodejs Make available for APM Agents project planning.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant