Configure Renovate

[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

• .github/workflows/ci.yml (github-actions)
• package.json (npm)
• .nvmrc (nvm)

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
• Pin all dependency versions except peerDependencies.
• Convert pinned GitHub Action digests to SemVer.
• Update lint packages automatically if tests pass.
• Update testing packages automatically if tests pass.
• Update @types/* packages automatically if tests pass.
• Require all status checks to pass before any automerging.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
• Enable Renovate configuration migration PRs when needed.

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

Pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Pin @eslint-react/eslint-plugin to 2.4.0
• Pin @eslint/js to 9.39.2
• Pin @fontsource-variable/karla to 5.2.8
• Pin @fontsource-variable/rubik to 5.2.8
• Pin @netlify/vite-plugin-tanstack-start to 1.2.6
• Pin @pandacss/dev to 1.7.1
• Pin @stylistic/eslint-plugin to 5.6.1
• Pin @tanstack/react-router to 1.143.4
• Pin @tanstack/react-start to 1.143.4
• Pin @types/node to 22.19.3
• Pin @unpic/react to 1.0.2
• Pin @vitejs/plugin-react to 5.1.2
• Upgrade actions/checkout to 34e114876b0b11c390a56381ad16ebd13914f8d5
• Upgrade actions/setup-node to 49933ea5288caeca8642d1e84afbd3f7d6820020
• Pin eslint to 9.39.2
• Pin eslint-config-prettier to 10.1.8
• Pin eslint-import-resolver-typescript to 4.4.4
• Pin eslint-plugin-import-x to 4.16.1
• Pin eslint-plugin-jsx-a11y to 6.10.2
• Pin eslint-plugin-react-hooks to 7.0.1
• Pin globals to 16.5.0
• Pin husky to 9.1.7
• Pin lint-staged to 16.2.7
• Pin node to v22.21.1
• Upgrade pnpm/action-setup to 41ff72655975bd51cab0327fa583b6e92b6d3061
• Pin react-icons to 5.5.0
• Pin typescript to 5.9.3
• Pin typescript-eslint to 8.50.0
• Pin usehooks-ts to 3.1.1
• Pin vite to 7.3.0
• Pin vite-tsconfig-paths to 6.0.3

Pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/react-monorepo
• Merge into: main
• Pin @types/react to 19.2.7
• Pin @types/react-dom to 19.2.3

Update pnpm to v10.26.2

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/pnpm-10.x
• Merge into: main
• Upgrade pnpm to 10.26.2

Update actions/checkout action to v4.3.1

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: main
• Upgrade actions/checkout to 34e114876b0b11c390a56381ad16ebd13914f8d5

Update actions/setup-node action to v4.4.0

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-4.x
• Merge into: main
• Upgrade actions/setup-node to 49933ea5288caeca8642d1e84afbd3f7d6820020

Update pnpm/action-setup action to v4.2.0

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-action-setup-4.x
• Merge into: main
• Upgrade pnpm/action-setup to 41ff72655975bd51cab0327fa583b6e92b6d3061

Update actions/checkout action to v6

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-6.x
• Merge into: main
• Upgrade actions/checkout to 8e8c483db84b4bee98b60c0593521ed34d9990e8

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 395ad3262231945c25e8478fd5baf05154b1d79f

Update Node.js to v24

• Schedule: ["at any time"]
• Branch name: renovate/node-24.x
• Merge into: main
• Upgrade node to 24
• Upgrade @types/node to ^24.0.0

Lock file maintenance

• Schedule: ["before 4am on monday"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

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

[netlify]

✅ Deploy Preview for mario-beltran ready!

Name	Link
🔨 Latest commit	66f429d
🔍 Latest deploy log	https://app.netlify.com/projects/mario-beltran/deploys/694c1a1fe299ab000839ef39
😎 Deploy Preview	https://deploy-preview-83.mario.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.