Skip to content

chore: Configure Renovate#9

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

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

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Apr 16, 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.

📚 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)
  • pnpm-workspace.yaml (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 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
  • Ensure that every dependency pinned by digest and sourced from GitLab.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

What to Expect

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

chore(deps): update dependency svelte to v5.55.10
  • Schedule: ["at any time"]
  • Branch name: renovate/svelte-5.x-lockfile
  • Merge into: main
  • Upgrade svelte to 5.55.10
fix(deps): update dependency workflow to v4.2.5
  • Schedule: ["at any time"]
  • Branch name: renovate/workflow-4.x
  • Merge into: main
  • Upgrade workflow to 4.2.5
chore(deps): update dependency @​sentry/sveltekit to v10.55.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sentry-javascript-monorepo
  • Merge into: main
  • Upgrade @sentry/sveltekit to 10.55.0
chore(deps): update dependency better-auth to ~1.6.0
  • Schedule: ["at any time"]
  • Branch name: renovate/better-auth-monorepo
  • Merge into: main
  • Upgrade better-auth to ~1.6.0
chore(deps): update pnpm to v11.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-11.x
  • Merge into: main
  • Upgrade pnpm to 11.4.0
chore(deps): update dependency @​sveltejs/vite-plugin-svelte to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/sveltejs-vite-plugin-svelte-7.x
  • Merge into: main
  • Upgrade @sveltejs/vite-plugin-svelte to ^7.0.0
chore(deps): update dependency prettier-plugin-svelte to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-plugin-svelte-4.x
  • Merge into: main
  • Upgrade prettier-plugin-svelte to ^4.0.0
chore(deps): update dependency typescript to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-6.x
  • Merge into: main
  • Upgrade typescript to ^6.0.0
chore(deps): update dependency vite to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/vite-8.x
  • Merge into: main
  • Upgrade vite to ^8.0.0
chore(deps): update eslint monorepo to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to ^10.0.0
  • Upgrade eslint to ^10.0.0
fix(deps): update dependency @​vercel/sandbox to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/vercel-sandbox-2.x
  • Merge into: main
  • Upgrade @vercel/sandbox to ^2.0.0
fix(deps): update dependency dockerode to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/dockerode-5.x
  • Merge into: main
  • Upgrade dockerode to ^5.0.0

🚸 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 was generated by Mend Renovate. View the repository job log.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 16, 2026

PR author is in the excluded authors list.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 16, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dayrelay Ready Ready Preview, Comment Apr 16, 2026 1:23am

Request Review

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