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

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

chore: Configure Renovate #7

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 16, 2024

Mend Renovate

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

  • 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 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 20 Pull Requests:

fix(deps): update dependency next to v13 [security]
  • Branch name: renovate/npm-next-vulnerability
  • Merge into: main
  • Upgrade next to 13.5.0
chore(deps): update dependency husky to v8.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-8.x-lockfile
  • Merge into: main
  • Upgrade husky to 8.0.3
chore(deps): update babel monorepo to v7.24.7
chore(deps): update dependency @​types/node to v18.19.39
  • Schedule: ["at any time"]
  • Branch name: renovate/node-18.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 18.19.39
chore(deps): update dependency eslint to v8.57.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade eslint to 8.57.0
chore(deps): update dependency eslint-config-next to v12.3.4
  • Schedule: ["at any time"]
  • Branch name: renovate/nextjs-monorepo
  • Merge into: main
  • Upgrade eslint-config-next to 12.3.4
chore(deps): update dependency lint-staged to v13.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lint-staged-13.x-lockfile
  • Merge into: main
  • Upgrade lint-staged to 13.3.0
chore(deps): update dependency prettier to v2.8.8
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-2.x-lockfile
  • Merge into: main
  • Upgrade prettier to 2.8.8
chore(deps): update dependency typescript to v4.9.5
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-4.x
  • Merge into: main
  • Upgrade typescript to 4.9.5
chore(deps): update react monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/react-monorepo
  • Merge into: main
  • Upgrade @types/react to 18.3.3
  • Upgrade react to 18.3.1
  • Upgrade react-dom to 18.3.1
fix(deps): update emotion monorepo to v11.11.0
  • Schedule: ["at any time"]
  • Branch name: renovate/emotion-monorepo
  • Merge into: main
  • Upgrade @emotion/cache to 11.11.0
  • Upgrade @emotion/server to 11.11.0
chore(deps): update dependency @​types/node to v20
  • Schedule: ["at any time"]
  • Branch name: renovate/node-20.x
  • Merge into: main
  • Upgrade @types/node to ^20.0.0
chore(deps): update dependency eslint to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade eslint to 9.7.0
chore(deps): update dependency eslint-config-next to v14
  • Schedule: ["at any time"]
  • Branch name: renovate/major-nextjs-monorepo
  • Merge into: main
  • Upgrade eslint-config-next to 14.2.5
chore(deps): update dependency eslint-plugin-simple-import-sort to v12
chore(deps): update dependency eslint-plugin-unused-imports to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-unused-imports-4.x
  • Merge into: main
  • Upgrade eslint-plugin-unused-imports to ^4.0.0
chore(deps): update dependency husky to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-9.x
  • Merge into: main
  • Upgrade husky to ^9.0.0
chore(deps): update dependency lint-staged to v15
  • Schedule: ["at any time"]
  • Branch name: renovate/lint-staged-15.x
  • Merge into: main
  • Upgrade lint-staged to ^15.0.0
chore(deps): update dependency prettier to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x
  • Merge into: main
  • Upgrade prettier to ^3.0.0
chore(deps): update dependency typescript to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x
  • Merge into: main
  • Upgrade typescript to 5.5.3

🚸 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 Mend Renovate. View repository job log here.

Copy link

vercel bot commented Jul 16, 2024

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

Name Status Preview Comments Updated (UTC)
vote ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 16, 2024 7:19am

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant