Dependency Dashboard

[renovate]

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Config Migration Needed

• Select this checkbox to let Renovate create an automated Config Migration PR.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update all non-major dependencies (@vue/compat, @vue/compiler-dom, @vue/compiler-sfc, @vue/server-renderer, eslint, pnpm, rollup, vue)

Detected dependencies

github-actions

.github/workflows/ci.yml

• actions/checkout v4
• pnpm/action-setup v4.0.0
• actions/setup-node v4

npm

package.json

• js-beautify ^1.14.9
• vue-component-type-helpers ^2.0.0
• @rollup/plugin-commonjs 28.0.1
• @rollup/plugin-json 6.1.0
• @rollup/plugin-node-resolve 15.3.0
• @rollup/plugin-replace 6.0.1
• @rollup/plugin-typescript 12.1.1
• @types/js-beautify 1.14.3
• @types/node 22.9.0
• @vitejs/plugin-vue 5.2.0
• @vitejs/plugin-vue-jsx 4.1.0
• @vitest/coverage-v8 2.1.5
• @vue/compat 3.5.12
• @vue/compiler-dom 3.5.12
• @vue/compiler-sfc 3.5.12
• @vue/server-renderer 3.5.12
• eslint 9.14.0
• eslint-config-prettier 9.1.0
• eslint-plugin-prettier 5.2.1
• husky 9.1.6
• jsdom 25.0.1
• jsdom-global 3.0.2
• lint-staged 15.2.10
• prettier 3.3.3
• reflect-metadata 0.2.2
• rollup 4.26.0
• tslib 2.8.1
• typescript 5.6.3
• typescript-eslint 8.14.0
• unplugin-vue-components 0.27.4
• vite 5.4.11
• vitepress 1.5.0
• vitepress-translation-helper 0.2.1
• vitest 2.1.5
• vue 3.5.12
• vue-class-component 8.0.0-rc.1
• vue-router 4.4.5
• vue-tsc 2.1.10
• vuex 4.1.0
• @vue/server-renderer 3.x
• vue 3.x
• pnpm 9.13.0

---

• Check this box to trigger a request for Renovate to run again on this repository

[lmiller1990]

What is the point of this issue? I guess I need to investigate what renovate does more closely.

[cexbrayat]

This is a dashboard that Renovate keeps up to date automatically (by editing the issue description). It shows the next PR, the one currently opened, and the one we closed without merging. It allows to retry them and trigger a run manually.
It's quite useful and does not generate noise, so I think we should keep it (but it can be configured to go away if needed).

[lmiller1990]

Right, I see. That's neat, let's keep it around! I hadn't seen this before, so I was a little confused. I did not realize you could trigger things from an issue via a checkbox! Very cool.