chore: Configure Renovate (#6)

Welcome to [Renovate](https://redirect.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

 * `.github/workflows/ci.yml` (github-actions)
 * `.github/workflows/deploy.yml` (github-actions)
 * `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
  - 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 2 Pull Requests:

<details>
<summary>chore(deps): update dependency @&#8203;types/node to
v25.6.0</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/node-25.x-lockfile`
  - Merge into: `main`
- Upgrade
[@types/node](https://redirect.github.com/DefinitelyTyped/DefinitelyTyped)
to `25.6.0`


</details>

<details>
<summary>chore(deps): update actions/github-script action to
v9</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-github-script-9.x`
  - Merge into: `main`
- Upgrade
[actions/github-script](https://redirect.github.com/actions/github-script)
to `v9`


</details>


---
> 
> [!WARNING]
> Please correct - or verify that you can safely ignore - these
dependency lookup failures before you merge this PR.
> 
> -   `Failed to look up npm package @void-sdk/void: no-result`
> 
> Files affected: `pnpm-workspace.yaml`


---

❓ 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://redirect.github.com/renovatebot/renovate/discussions).


---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/voidzero-dev/setup.viteplus.dev).


<!--renovate-config-hash:7748ea026d07812cba2cb72643e0f135ccbe933bb95169741a551e58b5dfc5cb-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: MK <fengmk2@gmail.com>

Author: renovate[bot]

renovate.json

@@ -0,0 +1,4 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": ["config:recommended"]
+}