Skip to content

chore: Configure Renovate#1

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure
Open

chore: Configure Renovate#1
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link

@renovate renovate bot commented Jan 15, 2026

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/jekyll-gh-pages.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.
  • 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 GitHub.com 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

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

chore(deps): replace dependency eslint-plugin-vitest with @​vitest/eslint-plugin ^1.0.1
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-vitest-replacement
  • Merge into: main
  • Upgrade eslint-plugin-vitest to ^1.0.1
chore(deps): update dependency @​biomejs/biome to v2.3.11
  • Schedule: ["at any time"]
  • Branch name: renovate/biomejs-biome-2.x-lockfile
  • Merge into: main
  • Upgrade @biomejs/biome to 2.3.11
chore(deps): update dependency @​types/node to v24.10.8
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 24.10.8
chore(deps): update dependency @​vitejs/plugin-react to v5.1.2
  • Schedule: ["at any time"]
  • Branch name: renovate/vitejs-plugin-react-5.x-lockfile
  • Merge into: main
  • Upgrade @vitejs/plugin-react to 5.1.2
chore(deps): update dependency effect to v3.19.14
  • Schedule: ["at any time"]
  • Branch name: renovate/effect-3.x-lockfile
  • Merge into: main
  • Upgrade effect to 3.19.14
chore(deps): update dependency eslint-plugin-react-refresh to v0.4.26
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-react-refresh-0.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-react-refresh to 0.4.26
chore(deps): update dependency lovable-tagger to v1.1.13
  • Schedule: ["at any time"]
  • Branch name: renovate/lovable-tagger-1.x-lockfile
  • Merge into: main
  • Upgrade lovable-tagger to 1.1.13
chore(deps): update dependency vitest to v4.0.17
  • Schedule: ["at any time"]
  • Branch name: renovate/vitest-monorepo
  • Merge into: main
  • Upgrade vitest to 4.0.17
chore(deps): update eslint monorepo to v9.39.2
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to 9.39.2
  • Upgrade eslint to 9.39.2
chore(deps): update react monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/react-monorepo
  • Merge into: main
  • Upgrade @types/react to 19.2.8
  • Upgrade react to 19.2.3
  • Upgrade react-dom to 19.2.3
chore(deps): update dependency @eslint-community/eslint-plugin-eslint-comments to v4.6.0
chore(deps): update dependency typescript-eslint to v8.53.0
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-eslint-monorepo
  • Merge into: main
  • Upgrade typescript-eslint to 8.53.0
chore(deps): update dependency vite to v7.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/vite-7.x-lockfile
  • Merge into: main
  • Upgrade vite to 7.3.1
chore(deps): update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
chore(deps): update actions/setup-node action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
chore(deps): update actions/upload-pages-artifact action to v4
chore(deps): update dependency globals to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/globals-17.x
  • Merge into: main
  • Upgrade globals to ^17.0.0
chore(deps): update dependency node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24
chore(deps): update dependency vite-tsconfig-paths to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/vite-tsconfig-paths-6.x
  • Merge into: main
  • Upgrade vite-tsconfig-paths to ^6.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.

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