thomas/svelte-examples
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Configure Renovate #2

Closed
renovate wants to merge 1 commit from renovate/configure into main
pull from: renovate/configure
merge into: thomas:main
Conversation 1 Commits 1 Files changed 1 +26
renovate commented 2026-10-02 14:25:43 +01:00
Collaborator
Copy link

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

  • .forgejo/workflows/deploy.yml (github-actions)
  • package.json (npm)
  • pnpm-workspace.yaml (npm)
  • .nvmrc (nvm)

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
  • 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 3 Pull Requests, up to a maximum of 11 over time (see docs for prConcurrentLimit), plus 4 security update Pull Requests which are not subject to this limit:

ℹ️ If you want to rate limit security update Pull Requests too, set vulnerabilityAlerts.prConcurrentLimit.

Update dependency svelte to v5.55.7 [SECURITY]
  • Branch name: renovate/npm-svelte-vulnerability
  • Merge into: main
  • Upgrade svelte to 5.55.7
Update dependency vite to v8.0.16 [SECURITY]
  • Branch name: renovate/npm-vite-vulnerability
  • Merge into: main
  • Upgrade vite to 8.0.16
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
Update dependency valibot to v1.4.2 [SECURITY]
  • Branch name: renovate/npm-valibot-vulnerability
  • Merge into: main
  • Upgrade valibot to 1.4.2
Update dependency @​sveltejs/adapter-node to v5.5.7
  • Schedule: ["at any time"]
  • Branch name: renovate/sveltejs-adapter-node-5.x-lockfile
  • Merge into: main
  • Upgrade @sveltejs/adapter-node to 5.5.7
Update dependency @​sveltejs/vite-plugin-svelte to v7.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/sveltejs-vite-plugin-svelte-7.x-lockfile
  • Merge into: main
  • Upgrade @sveltejs/vite-plugin-svelte to 7.3.1
Update dependency @​types/node to v25.9.9
  • Schedule: ["at any time"]
  • Branch name: renovate/node-25.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 25.9.9
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
Update dependency @​sveltejs/adapter-node to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/sveltejs-adapter-node-6.x
  • Merge into: main
  • Upgrade @sveltejs/adapter-node to sha512-s7muM4JmJ75OZ8o0G4VRhrEKdi8twuEm3t2o/qQsdlm12hKaX7S/CuUBuw3n983wB/IFBSpzG2ugX0xdGzbKwg==
Update dependency typescript to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-7.x
  • Merge into: main
  • Upgrade typescript to sha512-8FYau96o3NKOhbjKi/qNvG/W5jhzxkbdm5sj9AbZ/5T5sWqn3hJgLfGx27sRKZWTvyzCP8dLRBTf5tBTSRVUNA==
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

🚸 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 has been generated by Mend Renovate CLI.

Welcome to [Renovate](https://github.com/renovatebot/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](https://docs.renovatebot.com/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 * `.forgejo/workflows/deploy.yml` (github-actions) * `package.json` (npm) * `pnpm-workspace.yaml` (npm) * `.nvmrc` (nvm) ### 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 - 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 3 Pull Requests, up to a maximum of 11 over time (see [docs for `prConcurrentLimit`](https://docs.renovatebot.com/configuration-options/#prconcurrentlimit)), plus 4 security update Pull Requests which are not subject to this limit: ℹ️ If you want to rate limit security update Pull Requests too, set [`vulnerabilityAlerts.prConcurrentLimit`](https://docs.renovatebot.com/configuration-options/#vulnerabilityalerts). <details> <summary>Update dependency svelte to v5.55.7 [SECURITY]</summary> - Branch name: `renovate/npm-svelte-vulnerability` - Merge into: `main` - Upgrade [svelte](https://github.com/sveltejs/svelte) to `5.55.7` </details> <details> <summary>Update dependency vite to v8.0.16 [SECURITY]</summary> - Branch name: `renovate/npm-vite-vulnerability` - Merge into: `main` - Upgrade [vite](https://github.com/vitejs/vite) to `8.0.16` </details> <details> <summary>Update dependency @&#8203;sveltejs/kit to v2.70.2 [SECURITY]</summary> - Branch name: `renovate/npm-sveltejs-kit-vulnerability` - Merge into: `main` - Upgrade [@sveltejs/kit](https://github.com/sveltejs/kit) to `2.70.2` </details> <details> <summary>Update dependency valibot to v1.4.2 [SECURITY]</summary> - Branch name: `renovate/npm-valibot-vulnerability` - Merge into: `main` - Upgrade [valibot](https://github.com/open-circle/valibot) to `1.4.2` </details> <details> <summary>Update dependency @&#8203;sveltejs/adapter-node to v5.5.7</summary> - Schedule: ["at any time"] - Branch name: `renovate/sveltejs-adapter-node-5.x-lockfile` - Merge into: `main` - Upgrade [@sveltejs/adapter-node](https://github.com/sveltejs/kit) to `5.5.7` </details> <details> <summary>Update dependency @&#8203;sveltejs/vite-plugin-svelte to v7.3.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/sveltejs-vite-plugin-svelte-7.x-lockfile` - Merge into: `main` - Upgrade [@sveltejs/vite-plugin-svelte](https://github.com/sveltejs/vite-plugin-svelte) to `7.3.1` </details> <details> <summary>Update dependency @&#8203;types/node to v25.9.9</summary> - Schedule: ["at any time"] - Branch name: `renovate/node-25.x-lockfile` - Merge into: `main` - Upgrade [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) to `25.9.9` </details> <details> <summary>Update dependency svelte-check to v4.7.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/svelte-check-4.x-lockfile` - Merge into: `main` - Upgrade [svelte-check](https://github.com/sveltejs/language-tools) to `4.7.6` </details> <details> <summary>Update dependency @&#8203;sveltejs/adapter-node to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/sveltejs-adapter-node-6.x` - Merge into: `main` - Upgrade [@sveltejs/adapter-node](https://github.com/sveltejs/kit) to `sha512-s7muM4JmJ75OZ8o0G4VRhrEKdi8twuEm3t2o/qQsdlm12hKaX7S/CuUBuw3n983wB/IFBSpzG2ugX0xdGzbKwg==` </details> <details> <summary>Update dependency typescript to v7</summary> - Schedule: ["at any time"] - Branch name: `renovate/typescript-7.x` - Merge into: `main` - Upgrade [typescript](https://github.com/microsoft/TypeScript) to `sha512-8FYau96o3NKOhbjKi/qNvG/W5jhzxkbdm5sj9AbZ/5T5sWqn3hJgLfGx27sRKZWTvyzCP8dLRBTf5tBTSRVUNA==` </details> <details> <summary>Lock file maintenance</summary> - Schedule: ["before 4am on monday"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `main` - Regenerate lock files to use latest dependency versions </details> 🚸 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`](https://docs.renovatebot.com/configuration-options/#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](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-config-hash:b3b8bf5b5e5efdf9c310b4cfb1cc98f649de9ea6c3d4ba610254809cb8ddef4b-->
renovate closed this pull request 2026-10-02 14:39:10 +01:00
renovate commented 2026-10-03 04:05:34 +01:00
Author
Collaborator
Copy link

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

### Renovate is disabled Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thomas/svelte-examples!2
No description provided.