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.

📚 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 17 Pull Requests:

chore(deps): update dependency @​types/node to v25.6.2

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

chore(deps): update dependency @​types/qs to v6.15.1

• Schedule: ["at any time"]
• Branch name: renovate/qs-6.x
• Merge into: main
• Upgrade @types/qs to 6.15.1

chore(deps): update dependency vite to v8.0.11

• Schedule: ["at any time"]
• Branch name: renovate/vite-8.x
• Merge into: main
• Upgrade vite to 8.0.11

chore(deps): update pnpm to v11.0.9

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-11.x
• Merge into: main
• Upgrade pnpm to 11.0.9

chore(deps): update react monorepo to v19.2.6

• Schedule: ["at any time"]
• Branch name: renovate/react-monorepo
• Merge into: main
• Upgrade react to 19.2.6
• Upgrade react-dom to 19.2.6

fix(deps): update dependency @better-auth/passkey to v1.6.10

• Schedule: ["at any time"]
• Branch name: renovate/better-auth-passkey-1.x
• Merge into: main
• Upgrade @better-auth/passkey to 1.6.10

fix(deps): update dependency @​codemirror/view to v6.42.1

• Schedule: ["at any time"]
• Branch name: renovate/codemirror
• Merge into: main
• Upgrade @​codemirror/view to 6.42.1

fix(deps): update dependency @​haklex/rich-agent-chat to v0.4.1

• Schedule: ["at any time"]
• Branch name: renovate/haklex-rich-agent-chat-0.x
• Merge into: main
• Upgrade @haklex/rich-agent-chat to 0.4.1

fix(deps): update dependency @​haklex/rich-agent-core to v0.4.1

• Schedule: ["at any time"]
• Branch name: renovate/haklex-rich-agent-core-0.x
• Merge into: main
• Upgrade @haklex/rich-agent-core to 0.4.1

fix(deps): update dependency @​haklex/rich-diff to v0.4.1

• Schedule: ["at any time"]
• Branch name: renovate/haklex-rich-diff-0.x
• Merge into: main
• Upgrade @haklex/rich-diff to 0.4.1

fix(deps): update dependency @​haklex/rich-editor to v0.4.1

• Schedule: ["at any time"]
• Branch name: renovate/haklex-rich-editor-0.x
• Merge into: main
• Upgrade @haklex/rich-editor to 0.4.1

fix(deps): update dependency @​haklex/rich-ext-ai-agent to v0.4.1

• Schedule: ["at any time"]
• Branch name: renovate/haklex-rich-ext-ai-agent-0.x
• Merge into: main
• Upgrade @haklex/rich-ext-ai-agent to 0.4.1

fix(deps): update dependency @​haklex/rich-ext-nested-doc to v0.4.1

• Schedule: ["at any time"]
• Branch name: renovate/haklex-rich-ext-nested-doc-0.x
• Merge into: main
• Upgrade @haklex/rich-ext-nested-doc to 0.4.1

fix(deps): update dependency @​haklex/rich-style-token to v0.4.1

• Schedule: ["at any time"]
• Branch name: renovate/haklex-rich-style-token-0.x
• Merge into: main
• Upgrade @haklex/rich-style-token to 0.4.1

fix(deps): update dependency @​pierre/diffs to v1.1.21

• Schedule: ["at any time"]
• Branch name: renovate/pierre-diffs-1.x
• Merge into: main
• Upgrade @​pierre/diffs to 1.1.21

fix(deps): update dependency better-auth to v1.6.10

• Schedule: ["at any time"]
• Branch name: renovate/better-auth-1.x
• Merge into: main
• Upgrade better-auth to 1.6.10

fix(deps): update dependency @mx-space/api-client to v4

• Schedule: ["at any time"]
• Branch name: renovate/mx-space-api-client-4.x
• Merge into: main
• Upgrade @mx-space/api-client to 4.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.

[safedep]

SafeDep Report Summary

No dependency changes detected. Nothing to scan.

View complete scan results →

_{This report is generated by SafeDep Github App}