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

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

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 23, 2023

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/release.yml (github-actions)
  • package.json (npm)
  • packages/core/package.json (npm)
  • playground/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.
  • Use curated list of recommended non-monorepo package groupings.
  • Group all minor and patch updates together.
  • Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.
  • Schedule automerge monthly.
  • Schedule monthly.
  • Automerge non-major upgrades for semver stable packages if they pass tests.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Run Renovate on following schedule: before 4am on the first day of the month

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

fix(deps): update @dcloudio to v3.0.0-alpha-4030320241109002
chore(deps): update all non-major dependencies
chore(deps): update actions/checkout action to v4
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
chore(deps): update actions/setup-node action to v4
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: main
  • Upgrade actions/setup-node to v4
chore(deps): update dependency @​antfu/eslint-config to v3
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/antfu-eslint-config-3.x
  • Merge into: main
  • Upgrade @antfu/eslint-config to ^3.0.0
chore(deps): update dependency @​types/node to v22
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/node-22.x
  • Merge into: main
  • Upgrade @types/node to ^22.0.0
chore(deps): update dependency eslint to v9
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade eslint to ^9.0.0
chore(deps): update dependency esno to v4
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/esno-4.x
  • Merge into: main
  • Upgrade esno to ^4.0.0
chore(deps): update dependency rollup to v4
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/rollup-4.x
  • Merge into: main
  • Upgrade rollup to ^4.0.0
chore(deps): update dependency unbuild to v2
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/unbuild-2.x
  • Merge into: main
  • Upgrade unbuild to ^2.0.0
chore(deps): update dependency vite to v5
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/vite-5.x
  • Merge into: main
  • Upgrade vite to 5.4.11
  • Upgrade vite to ^5.0.0
chore(deps): update dependency vitest to v2
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/major-vitest-monorepo
  • Merge into: main
  • Upgrade vitest to ^2.0.0
chore(deps): update dependency vue-tsc to v2
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/vue-tsc-2.x
  • Merge into: main
  • Upgrade vue-tsc to ^2.0.0
chore(deps): update pnpm to v9
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/pnpm-9.x
  • Merge into: main
  • Upgrade pnpm to 9.13.2
fix(deps): update dependency chokidar to v4
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/chokidar-4.x
  • Merge into: main
  • Upgrade chokidar to ^4.0.0
fix(deps): update dependency minimatch to v10
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/minimatch-10.x
  • Merge into: main
  • Upgrade minimatch to ^10.0.0
fix(deps): update dependency vue-i18n to v10
  • Schedule: ["before 4am on the first day of the month"]
  • Branch name: renovate/vue-i18n-10.x
  • Merge into: main
  • Upgrade vue-i18n to ^10.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

coderabbitai bot commented Aug 17, 2024

Walkthrough

The introduction of renovate.json enhances the project's dependency management by implementing a schema configuration for the Renovate bot. This enables automated updates of dependencies, drawing from a predefined configuration while allowing for custom settings. The adjustment aims to streamline the maintenance process, ensuring the project stays current with minimal manual effort.

Changes

Files Change Summary
renovate.json New file created for Renovate bot configuration, specifying schema validation and extending settings from uni-helper/renovate-config.

Poem

🐇 In the meadow where updates play,
A new config hops in, brightening the day.
With Renovate's help, our project can dance,
Dependencies updated, giving growth a chance!
So let’s cheer for the changes, both big and small,
For a smoother path awaits us, standing tall! 🌼


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2c062f1 and f5c27cd.

Files selected for processing (1)
  • renovate.json (1 hunks)
Files skipped from review due to trivial changes (1)
  • renovate.json

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.

0 participants