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

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

Configure Renovate #2

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 5, 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

  • compose.yaml (docker-compose)
  • Dockerfile (dockerfile)
  • .github/workflows/deploy.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
  • 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 (except for nuget) 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 4 Pull Requests:

Update dependency @​hono/node-server to v1.13.7
  • Schedule: ["at any time"]
  • Branch name: renovate/hono-node-server-1.x-lockfile
  • Merge into: main
  • Upgrade @hono/node-server to 1.13.7
Update dependency @​types/node to v20.17.6
  • Schedule: ["at any time"]
  • Branch name: renovate/node-20.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 20.17.6
Update dependency hono to v4.6.10
  • Schedule: ["at any time"]
  • Branch name: renovate/hono-4.x-lockfile
  • Merge into: main
  • Upgrade hono to 4.6.10
Update Node.js to v22
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x
  • Merge into: main
  • Upgrade node to 22-alpine
  • Upgrade @types/node to ^22.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 was generated by Mend Renovate. View the repository job log.

Copy link

sourcery-ai bot commented Nov 5, 2024

Reviewer's Guide by Sourcery

This PR introduces Renovate, an automated dependency update tool, by adding its initial configuration file. The implementation uses the recommended default configuration that extends from Renovate's base configuration preset.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Added initial Renovate configuration
  • Created new configuration file with JSON schema reference
  • Configured to use recommended preset settings
  • Set up for automatic dependency updates across Docker, docker-compose, and npm packages
renovate.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

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.

0 participants