Skip to content

chore: Configure Renovate - #53

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

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

Conversation

@renovate

@renovate renovate Bot commented May 9, 2026

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

  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/deploy.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 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
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs

What to Expect

With your current configuration, Renovate will create 10 Pull Requests, up to a maximum of 44 over time (see docs for prConcurrentLimit), plus 7 security update Pull Requests which are not subject to this limit:

chore(deps): update dependency better-auth to v1.6.22 [security]
  • Branch name: renovate/npm-better-auth-vulnerability
  • Merge into: main
  • Upgrade better-auth to 1.6.22
chore(deps): update dependency nanoid to v5.1.16 [security]
  • Branch name: renovate/npm-nanoid-vulnerability
  • Merge into: main
  • Upgrade nanoid to 5.1.16
chore(deps): update dependency svelte to v5.55.7 [security]
  • Branch name: renovate/npm-svelte-vulnerability
  • Merge into: main
  • Upgrade svelte to 5.55.7
chore(deps): update dependency @​sveltejs/kit to v2.70.2 [security]
  • Branch name: renovate/npm-sveltejs-kit-vulnerability
  • Merge into: main
  • Upgrade @sveltejs/kit to 2.70.2
fix(deps): update dependency drizzle-orm to ^0.45.0 [security]
  • Branch name: renovate/npm-drizzle-orm-vulnerability
  • Merge into: main
  • Upgrade drizzle-orm to ^0.45.0
chore(deps): update dependency vite to v6 [security]
  • Branch name: renovate/npm-vite-vulnerability
  • Merge into: main
  • Upgrade vite to ~6.4.0
chore(deps): update dependency vitest to v3 [security]
  • Branch name: renovate/npm-vitest-vulnerability
  • Merge into: main
  • Upgrade vitest to ^3.0.0
chore(deps): update dependency @​tailwindcss/typography to v0.5.20
  • Schedule: ["at any time"]
  • Branch name: renovate/tailwindcss-typography-0.x-lockfile
  • Merge into: main
  • Upgrade @tailwindcss/typography to 0.5.20
chore(deps): update dependency autoprefixer to v10.5.4
  • Schedule: ["at any time"]
  • Branch name: renovate/autoprefixer-10.x-lockfile
  • Merge into: main
  • Upgrade autoprefixer to 10.5.4
chore(deps): update dependency better-sqlite3 to v13.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/better-sqlite3-13.x-lockfile
  • Merge into: main
  • Upgrade better-sqlite3 to 13.0.3
chore(deps): update dependency prettier-plugin-svelte to v3.5.2
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-plugin-svelte-3.x-lockfile
  • Merge into: main
  • Upgrade prettier-plugin-svelte to 3.5.2
chore(deps): update dependency @​cloudflare/workers-types to v4.20260702.1
  • Schedule: ["at any time"]
  • Branch name: renovate/cloudflare-workers-types-4.x-lockfile
  • Merge into: main
  • Upgrade @cloudflare/workers-types to 4.20260702.1
chore(deps): update dependency @​eslint/compat to v2.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-compat-2.x-lockfile
  • Merge into: main
  • Upgrade @eslint/compat to 2.1.0
chore(deps): update dependency @​inlang/paraglide-js to v2.25.0
  • Schedule: ["at any time"]
  • Branch name: renovate/inlang-paraglide-js-2.x-lockfile
  • Merge into: main
  • Upgrade @inlang/paraglide-js to 2.25.0
chore(deps): update dependency @​types/node to v26.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/node-26.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 26.4.0
chore(deps): update dependency drizzle-kit to ^0.31.0
  • Schedule: ["at any time"]
  • Branch name: renovate/drizzle-kit-0.x
  • Merge into: main
  • Upgrade drizzle-kit to ^0.31.0
chore(deps): update dependency eslint to v10.9.1
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade eslint to 10.9.1
chore(deps): update dependency eslint-plugin-svelte to v3.23.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-svelte-3.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-svelte to 3.23.0
chore(deps): update dependency prettier to v3.9.6
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: main
  • Upgrade prettier to 3.9.6
chore(deps): update dependency svelte-check to v4.7.6
  • Schedule: ["at any time"]
  • Branch name: renovate/svelte-check-4.x-lockfile
  • Merge into: main
  • Upgrade svelte-check to 4.7.6
chore(deps): update dependency tsx to v4.23.12
  • Schedule: ["at any time"]
  • Branch name: renovate/tsx-4.x-lockfile
  • Merge into: main
  • Upgrade tsx to 4.23.12
chore(deps): update dependency typescript-eslint to v8.68.0
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-eslint-monorepo
  • Merge into: main
  • Upgrade typescript-eslint to 8.68.0
chore(deps): update tailwindcss monorepo to v4.3.3
  • Schedule: ["at any time"]
  • Branch name: renovate/tailwindcss-monorepo
  • Merge into: main
  • Upgrade @tailwindcss/vite to 4.3.3
  • Upgrade tailwindcss to 4.3.3
fix(deps): update dependency lucide-svelte to ^0.577.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lucide-monorepo
  • Merge into: main
  • Upgrade lucide-svelte to ^0.577.0
chore(deps): update actions/checkout action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-7.x
  • Merge into: main
  • Upgrade actions/checkout to v7
chore(deps): update actions/setup-node action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-7.x
  • Merge into: main
  • Upgrade actions/setup-node to v7
chore(deps): update cloudflare/wrangler-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/cloudflare-wrangler-action-4.x
  • Merge into: main
  • Upgrade cloudflare/wrangler-action to v4
chore(deps): update dependency @​cloudflare/workers-types to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/cloudflare-workers-types-5.x
  • Merge into: main
  • Upgrade @cloudflare/workers-types to ^5.0.0
chore(deps): update dependency @​sveltejs/adapter-auto to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/sveltejs-adapter-auto-7.x
  • Merge into: main
  • Upgrade @sveltejs/adapter-auto to ^7.0.0
chore(deps): update dependency @​types/better-sqlite3 to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/better-sqlite3-9.x
  • Merge into: main
  • Upgrade @types/better-sqlite3 to ^9.0.0
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 pnpm to v11
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-11.x
  • Merge into: main
  • Upgrade pnpm to 11
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 v7
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-7.x
  • Merge into: main
  • Upgrade typescript to ^7.0.0
chore(deps): update dependency wrangler to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/wrangler-4.x
  • Merge into: main
  • Upgrade wrangler to ^4.0.0
chore(deps): update pnpm/action-setup action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-action-setup-6.x
  • Merge into: main
  • Upgrade pnpm/action-setup to v6
fix(deps): update dependency @​sveltejs/adapter-cloudflare to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/sveltejs-adapter-cloudflare-7.x
  • Merge into: main
  • Upgrade @sveltejs/adapter-cloudflare to ^7.0.0
fix(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
fix(deps): update dependency bits-ui to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/bits-ui-2.x
  • Merge into: main
  • Upgrade bits-ui to ^2.0.0
fix(deps): update dependency lucide-svelte to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/major-lucide-monorepo
  • Merge into: main
  • Upgrade lucide-svelte to ^1.0.0
fix(deps): update dependency marked to v18
  • Schedule: ["at any time"]
  • Branch name: renovate/marked-18.x
  • Merge into: main
  • Upgrade marked to ^18.0.0
fix(deps): update dependency tailwind-merge to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/tailwind-merge-3.x
  • Merge into: main
  • Upgrade tailwind-merge to ^3.0.0
fix(deps): update dependency tailwind-variants to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/tailwind-variants-3.x
  • Merge into: main
  • Upgrade tailwind-variants to ^3.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. Security update Pull Requests are not subject to this limit and will be created straight away.


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

@thunpisit

Copy link
Copy Markdown
Contributor

Triage as part of Phase 5D (#104).

Mergeable, but the failing check is from a run three months old — it predates the config fixes that have since landed:

So that red X is almost certainly stale rather than a real signal. Rebasing this branch on current main should turn it green; I have not pushed to it since it is a bot branch.

On merging it: whether to adopt Renovate is your call, not mine — it changes ongoing maintenance load, and this repo pins Vite at ~5.4.21 deliberately (Vite 6 trips vite-plugin-sveltekit-guard during production builds). If you do adopt it, that pin needs an explicit ignore rule or Renovate will keep proposing the upgrade that breaks the build.

Leaving open for your decision.

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.

1 participant