Skip to content

Configure Renovate - #1

Open
figure-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure
Open

Configure Renovate#1
figure-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@figure-renovate

@figure-renovate figure-renovate Bot commented Nov 15, 2024

Copy link
Copy Markdown

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.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 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.


Detected Package Files

  • package.json (npm)
  • renovate.json (renovate-config-presets)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • 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.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Enable Renovate configuration migration PRs when needed.
  • Show all Merge Confidence badges for pull requests.
  • Run Renovate on following schedule: on Monday

What to Expect

With your current configuration, Renovate will create 20 Pull Requests:

Update dependency vite from `^5.4.11` to `v6` [SECURITY]
  • Branch name: renovate/npm-vite-vulnerability
  • Merge into: main
  • Upgrade vite to ^6.0.0
Pin dependencies
Pin dependencies
Update dependency @​vitejs/plugin-react-swc from `^3.5.0` to `^3.11.0`
  • Schedule: ["on Monday"]
  • Branch name: renovate/vitejs-plugin-react-swc-3.x
  • Merge into: main
  • Upgrade @vitejs/plugin-react-swc to ^3.11.0
Update dependency autoprefixer from `^10.4.20` to `^10.5.4`
  • Schedule: ["on Monday"]
  • Branch name: renovate/autoprefixer-10.x
  • Merge into: main
  • Upgrade autoprefixer to ^10.5.4
Update dependency eslint-plugin-react-refresh from `^0.4.14` to `^0.5.0`
  • Schedule: ["on Monday"]
  • Branch name: renovate/eslint-plugin-react-refresh-0.x
  • Merge into: main
  • Upgrade eslint-plugin-react-refresh to ^0.5.0
Update dependency globals from `^15.11.0` to `^15.12.0`
  • Schedule: ["on Monday"]
  • Branch name: renovate/globals-15.x
  • Merge into: main
  • Upgrade globals to ^15.12.0
Update dependency postcss from `^8.4.49` to `^8.5.23`
  • Schedule: ["on Monday"]
  • Branch name: renovate/postcss-8.x
  • Merge into: main
  • Upgrade postcss to ^8.5.23
Update dependency tsx from `^4.19.2` to `^4.23.1`
  • Schedule: ["on Monday"]
  • Branch name: renovate/tsx-4.x
  • Merge into: main
  • Upgrade tsx to ^4.23.1
Update dependency typescript from `~5.6.2` to `~5.9.0`
  • Schedule: ["on Monday"]
  • Branch name: renovate/typescript-5.x
  • Merge into: main
  • Upgrade typescript to ~5.9.0
Update eslint monorepo from `^9.13.0` to `^9.14.0`
  • Schedule: ["on Monday"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to ^9.14.0
  • Upgrade eslint to ^9.14.0
Update dependency @​vitejs/plugin-react-swc from `^3.5.0` to `v4`
  • Schedule: ["on Monday"]
  • Branch name: renovate/vitejs-plugin-react-swc-4.x
  • Merge into: main
  • Upgrade @vitejs/plugin-react-swc to ^4.0.0
Update dependency express from `4.21.1` to `v5`
  • Schedule: ["on Monday"]
  • Branch name: renovate/express-5.x
  • Merge into: main
  • Upgrade express to ^5.0.0
Update dependency globals from `^15.11.0` to `v17`
  • Schedule: ["on Monday"]
  • Branch name: renovate/globals-17.x
  • Merge into: main
  • Upgrade globals to ^17.0.0
Update dependency react from `^18.3.1` to `v19`
  • Schedule: ["on Monday"]
  • Branch name: renovate/react-19.x
  • Merge into: main
  • Upgrade react to ^19.0.0
Update dependency react-dom from `^18.3.1` to `v19`
  • Schedule: ["on Monday"]
  • Branch name: renovate/react-dom-19.x
  • Merge into: main
  • Upgrade react-dom to ^19.0.0
Update dependency tailwindcss from `3.4.14` to `v4`
  • Schedule: ["on Monday"]
  • Branch name: renovate/major-tailwindcss-monorepo
  • Merge into: main
  • Upgrade tailwindcss to ^4.0.0
Update dependency typescript from `~5.6.2` to `v7`
  • Schedule: ["on Monday"]
  • Branch name: renovate/typescript-7.x
  • Merge into: main
  • Upgrade typescript to ~7.0.0
Update eslint monorepo from `^9.13.0` to `v10` (major)
  • Schedule: ["on Monday"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to ^10.0.0
  • Upgrade eslint to ^10.0.0
Update react monorepo (major)

🚸 PR 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.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants