Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: Configure Renovate #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 1 commit into main
base: main
Choose a base branch
Loading
from renovate/configure
Open

chore: Configure Renovate #2

renovate wants to merge 1 commit into main from renovate/configure

Conversation

@renovate
Copy link

@renovate renovate bot commented Sep 10, 2025
edited
Loading

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

  • apps/backend/package.json (npm)
  • apps/frontend/package.json (npm)
  • 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.

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

chore(deps): update dependency @​sveltejs/adapter-node to v5.3.2
  • Schedule: ["at any time"]
  • Branch name: renovate/sveltejs-adapter-node-5.x-lockfile
  • Merge into: main
  • Upgrade @sveltejs/adapter-node to 5.3.2
chore(deps): update dependency svelte to v5.38.10
  • Schedule: ["at any time"]
  • Branch name: renovate/svelte-5.x-lockfile
  • Merge into: main
  • Upgrade svelte to 5.38.10
fix(deps): update dependency zod to v4.1.8
  • Schedule: ["at any time"]
  • Branch name: renovate/zod-4.x-lockfile
  • Merge into: main
  • Upgrade zod to 4.1.8
chore(deps): update dependency @​sveltejs/kit to v2.39.1
  • Schedule: ["at any time"]
  • Branch name: renovate/sveltejs-kit-2.x-lockfile
  • Merge into: main
  • Upgrade @sveltejs/kit to 2.39.1
chore(deps): update dependency @​sveltejs/vite-plugin-svelte to v6.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sveltejs-vite-plugin-svelte-6.x-lockfile
  • Merge into: main
  • Upgrade @sveltejs/vite-plugin-svelte to 6.2.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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants

AltStyle によって変換されたページ (->オリジナル) /