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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chore: Configure Renovate #30

wants to merge 2 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 12, 2025

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/lint.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
  • Hopefully safe environment variables to allow users to configure.
  • 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.
  • Automerge patch upgrades if they pass tests.
  • Automerge patch and minor upgrades if they pass tests.
  • Raise PR when vulnerability alerts are detected.
  • Run Renovate on following schedule: before 3am 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 26 Pull Requests:

chore(deps): pin dependencies
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/type-definitions
  • Merge into: main
  • Pin @types/bcryptjs to 2.4.6
  • Pin @types/node to 22.10.2
fix(deps): pin dependencies
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/auth-packages
  • Merge into: main
  • Pin @auth/core to 0.35.3
  • Pin @auth/prisma-adapter to 2.7.4
fix(deps): pin dependencies
fix(deps): pin dependencies
fix(deps): pin dependency @​prisma/client to 6.1.0
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/prisma-packages
  • Merge into: main
  • Pin @prisma/client to 6.1.0
chore(deps): update dependency eslint-config-next to v15.1.6
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/patch-nextjs-monorepo
  • Merge into: main
  • Upgrade eslint-config-next to 15.1.6
chore(deps): update dependency react-email to v3.0.6
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-3.0.x
  • Merge into: main
  • Upgrade react-email to 3.0.6
chore(deps): update type definitions (patch)
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/patch-type-definitions
  • Merge into: main
  • Upgrade @types/node to ^22.10.2
  • Upgrade @types/react to 19.0.8
  • Upgrade @types/react-dom to 19.0.3
fix(deps): update dependency @react-email/body to ^0.0.11
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-body-0.0.x
  • Merge into: main
  • Upgrade @react-email/body to ^0.0.11
fix(deps): update dependency @react-email/button to ^0.0.19
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-button-0.0.x
  • Merge into: main
  • Upgrade @react-email/button to ^0.0.19
fix(deps): update dependency @react-email/container to ^0.0.15
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-container-0.0.x
  • Merge into: main
  • Upgrade @react-email/container to ^0.0.15
fix(deps): update dependency @react-email/head to ^0.0.12
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-head-0.0.x
  • Merge into: main
  • Upgrade @react-email/head to ^0.0.12
fix(deps): update dependency @react-email/hr to ^0.0.11
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-hr-0.0.x
  • Merge into: main
  • Upgrade @react-email/hr to ^0.0.11
fix(deps): update dependency @react-email/html to ^0.0.11
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-html-0.0.x
  • Merge into: main
  • Upgrade @react-email/html to ^0.0.11
fix(deps): update dependency @react-email/img to ^0.0.11
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-img-0.0.x
  • Merge into: main
  • Upgrade @react-email/img to ^0.0.11
fix(deps): update dependency @react-email/preview to ^0.0.12
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-preview-0.0.x
  • Merge into: main
  • Upgrade @react-email/preview to ^0.0.12
fix(deps): update dependency @react-email/section to ^0.0.16
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-section-0.0.x
  • Merge into: main
  • Upgrade @react-email/section to ^0.0.16
fix(deps): update dependency @react-email/text to ^0.0.11
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/react-email-text-0.0.x
  • Merge into: main
  • Upgrade @react-email/text to ^0.0.11
chore(deps): update dependency postcss to ^8.5.1
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/postcss-8.x
  • Merge into: main
  • Upgrade postcss to ^8.5.1
chore(deps): update dependency prisma to ^6.1.0
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/prisma-monorepo
  • Merge into: main
  • Upgrade prisma to ^6.1.0
fix(deps): update dependency lucide-react to ^0.474.0
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/lucide-monorepo
  • Merge into: main
  • Upgrade lucide-react to ^0.474.0
fix(deps): update dependency next-themes to ^0.4.0
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/next-themes-0.x
  • Merge into: main
  • Upgrade next-themes to ^0.4.0
fix(deps): update dependency tailwind-merge to ^2.6.0
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/tailwind-merge-2.x
  • Merge into: main
  • Upgrade tailwind-merge to ^2.6.0
chore(deps): update actions/checkout action to v4
  • Schedule: ["before 3am 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 3am 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 tailwindcss to v4
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/tailwindcss-4.x
  • Merge into: main
  • Upgrade tailwindcss to ^4.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

vercel bot commented Jan 12, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-auth-example ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 28, 2025 8:21pm

Copy link

coderabbitai bot commented Jan 28, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

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