rbrooks/Quest-Board
Watch
1
0
Fork
You've already forked Quest-Board
 0
Code Issues 59 Pull requests 7 Projects Releases 76 Packages Wiki Activity Actions 2

chore(deps): update dependency @vitejs/plugin-react to v6.1.1 #316

Closed
renovate-bot wants to merge 1 commit from renovate/vitejs-plugin-react-6.x into main
pull from: renovate/vitejs-plugin-react-6.x
merge into: rbrooks:main
Conversation 3 Commits 1 Files changed 1 +1 -1
renovate-bot commented 2026-08-24 06:28:10 +00:00
Contributor
Copy link

This PR contains the following updates:

Package Change Age Confidence
@vitejs/plugin-react (source) 6.0.5 → 6.1.1 age confidence

Release Notes

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v6.1.1

Compare Source

Add compiler.logDiagnostics option

Recoverable React Compiler diagnostics are no longer logged by default. Set compiler.logDiagnostics to true to log them through Vite. Fatal diagnostics are always logged and fail the transform.

Respect environment sourcemap option for React Compiler transform when builder.sharedPlugins is enabled (#​1439)

The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental builder.sharedPlugins was enabled.

v6.1.0

Compare Source

Add experimental native React Compiler support (#​1419)

Add experimental native React Compiler support.

You can use it by installing oxc-transform-react and enabling it via the compiler option:

npm install -D oxc-transform-react

import { defineConfig } from 'vite'
import react from '@​vitejs/plugin-react'

export default defineConfig({
  plugins: [
     react({ compiler: true })
  ]
})

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 9am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/main/packages/plugin-react#readme) ([source](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react)) | [`6.0.5` → `6.1.1`](https://renovatebot.com/diffs/npm/@vitejs%2fplugin-react/6.0.5/6.1.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@vitejs%2fplugin-react/6.1.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@vitejs%2fplugin-react/6.0.5/6.1.1?slim=true) | --- ### Release Notes <details> <summary>vitejs/vite-plugin-react (@&#8203;vitejs/plugin-react)</summary> ### [`v6.1.1`](https://github.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#611-2026-08-28) [Compare Source](https://github.com/vitejs/vite-plugin-react/compare/39b31735bf79c2dd380eedaba7ed849256f92a29...04cac5020e349f452d76c5a4f6d788ad4b38930a) ##### Add `compiler.logDiagnostics` option Recoverable React Compiler diagnostics are no longer logged by default. Set `compiler.logDiagnostics` to `true` to log them through Vite. Fatal diagnostics are always logged and fail the transform. ##### Respect environment sourcemap option for React Compiler transform when `builder.sharedPlugins` is enabled ([#&#8203;1439](https://github.com/vitejs/vite-plugin-react/pull/1439)) The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental `builder.sharedPlugins` was enabled. ### [`v6.1.0`](https://github.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#610-2026-08-19) [Compare Source](https://github.com/vitejs/vite-plugin-react/compare/68c0cb8796ce18bd049c3d05c5210eaf0617eac0...39b31735bf79c2dd380eedaba7ed849256f92a29) ##### Add experimental native React Compiler support ([#&#8203;1419](https://github.com/vitejs/vite-plugin-react/pull/1419)) Add experimental native React Compiler support. You can use it by installing `oxc-transform-react` and enabling it via the `compiler` option: ```sh npm install -D oxc-transform-react ``` ```js import { defineConfig } from 'vite' import react from '@&#8203;vitejs/plugin-react' export default defineConfig({ plugins: [ react({ compiler: true }) ] }) ``` </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - "before 9am on monday" - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yODAuMyIsInVwZGF0ZWRJblZlciI6IjQzLjI4OC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-08-24 06:28:11 +00:00
renovate-bot commented 2026-08-24 06:28:12 +00:00
Author
Contributor
Copy link

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: webapp/frontend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: quest-board@0.1.0
npm error Found: @babel/core@7.29.7
npm error node_modules/@babel/core
npm error   peer @babel/core@"^7.0.0" from @babel/helper-create-class-features-plugin@7.29.7
npm error   node_modules/@babel/helper-create-class-features-plugin
npm error     @babel/helper-create-class-features-plugin@"^7.29.7" from @babel/plugin-transform-class-properties@7.29.7
npm error     node_modules/@babel/plugin-transform-class-properties
npm error       @babel/plugin-transform-class-properties@"^7.29.7" from @babel/preset-env@7.29.7
npm error       node_modules/@babel/preset-env
npm error         @babel/preset-env@"^7.11.0" from workbox-build@7.4.1
npm error         node_modules/workbox-build
npm error     @babel/helper-create-class-features-plugin@"^7.29.7" from @babel/plugin-transform-class-static-block@7.29.7
npm error     node_modules/@babel/plugin-transform-class-static-block
npm error       @babel/plugin-transform-class-static-block@"^7.29.7" from @babel/preset-env@7.29.7
npm error       node_modules/@babel/preset-env
npm error         @babel/preset-env@"^7.11.0" from workbox-build@7.4.1
npm error         node_modules/workbox-build
npm error     2 more (@babel/plugin-transform-private-methods, @babel/plugin-transform-private-property-in-object)
npm error   peer @babel/core@"^7.0.0" from @babel/helper-create-regexp-features-plugin@7.29.7
npm error   node_modules/@babel/helper-create-regexp-features-plugin
npm error     @babel/helper-create-regexp-features-plugin@"^7.18.6" from @babel/plugin-syntax-unicode-sets-regex@7.18.6
npm error     node_modules/@babel/plugin-syntax-unicode-sets-regex
npm error       @babel/plugin-syntax-unicode-sets-regex@"^7.18.6" from @babel/preset-env@7.29.7
npm error       node_modules/@babel/preset-env
npm error         @babel/preset-env@"^7.11.0" from workbox-build@7.4.1
npm error         node_modules/workbox-build
npm error     @babel/helper-create-regexp-features-plugin@"^7.29.7" from @babel/plugin-transform-dotall-regex@7.29.7
npm error     node_modules/@babel/plugin-transform-dotall-regex
npm error       @babel/plugin-transform-dotall-regex@"^7.29.7" from @babel/preset-env@7.29.7
npm error       node_modules/@babel/preset-env
npm error         @babel/preset-env@"^7.11.0" from workbox-build@7.4.1
npm error         node_modules/workbox-build
npm error     6 more (...)
npm error   73 more (@babel/helper-define-polyfill-provider, ...)
npm error
npm error Could not resolve dependency:
npm error dev @vitejs/plugin-react@"6.1.1" from the root project
npm error
npm error Conflicting peer dependency: @babel/core@8.0.1
npm error node_modules/@babel/core
npm error   peer @babel/core@"^8.0.0" from @babel/plugin-transform-runtime@8.0.1
npm error   node_modules/@babel/plugin-transform-runtime
npm error     peerOptional @babel/plugin-transform-runtime@"^7.29.0 || ^8.0.0-rc.1" from @rolldown/plugin-babel@0.2.3
npm error     node_modules/@rolldown/plugin-babel
npm error       peerOptional @rolldown/plugin-babel@"^0.1.7 || ^0.2.0" from @vitejs/plugin-react@6.1.1
npm error       node_modules/@vitejs/plugin-react
npm error         dev @vitejs/plugin-react@"6.1.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-08-31T18_19_09_611Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-08-31T18_19_09_611Z-debug-0.log
### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: webapp/frontend/package-lock.json ``` npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: quest-board@0.1.0 npm error Found: @babel/core@7.29.7 npm error node_modules/@babel/core npm error peer @babel/core@"^7.0.0" from @babel/helper-create-class-features-plugin@7.29.7 npm error node_modules/@babel/helper-create-class-features-plugin npm error @babel/helper-create-class-features-plugin@"^7.29.7" from @babel/plugin-transform-class-properties@7.29.7 npm error node_modules/@babel/plugin-transform-class-properties npm error @babel/plugin-transform-class-properties@"^7.29.7" from @babel/preset-env@7.29.7 npm error node_modules/@babel/preset-env npm error @babel/preset-env@"^7.11.0" from workbox-build@7.4.1 npm error node_modules/workbox-build npm error @babel/helper-create-class-features-plugin@"^7.29.7" from @babel/plugin-transform-class-static-block@7.29.7 npm error node_modules/@babel/plugin-transform-class-static-block npm error @babel/plugin-transform-class-static-block@"^7.29.7" from @babel/preset-env@7.29.7 npm error node_modules/@babel/preset-env npm error @babel/preset-env@"^7.11.0" from workbox-build@7.4.1 npm error node_modules/workbox-build npm error 2 more (@babel/plugin-transform-private-methods, @babel/plugin-transform-private-property-in-object) npm error peer @babel/core@"^7.0.0" from @babel/helper-create-regexp-features-plugin@7.29.7 npm error node_modules/@babel/helper-create-regexp-features-plugin npm error @babel/helper-create-regexp-features-plugin@"^7.18.6" from @babel/plugin-syntax-unicode-sets-regex@7.18.6 npm error node_modules/@babel/plugin-syntax-unicode-sets-regex npm error @babel/plugin-syntax-unicode-sets-regex@"^7.18.6" from @babel/preset-env@7.29.7 npm error node_modules/@babel/preset-env npm error @babel/preset-env@"^7.11.0" from workbox-build@7.4.1 npm error node_modules/workbox-build npm error @babel/helper-create-regexp-features-plugin@"^7.29.7" from @babel/plugin-transform-dotall-regex@7.29.7 npm error node_modules/@babel/plugin-transform-dotall-regex npm error @babel/plugin-transform-dotall-regex@"^7.29.7" from @babel/preset-env@7.29.7 npm error node_modules/@babel/preset-env npm error @babel/preset-env@"^7.11.0" from workbox-build@7.4.1 npm error node_modules/workbox-build npm error 6 more (...) npm error 73 more (@babel/helper-define-polyfill-provider, ...) npm error npm error Could not resolve dependency: npm error dev @vitejs/plugin-react@"6.1.1" from the root project npm error npm error Conflicting peer dependency: @babel/core@8.0.1 npm error node_modules/@babel/core npm error peer @babel/core@"^8.0.0" from @babel/plugin-transform-runtime@8.0.1 npm error node_modules/@babel/plugin-transform-runtime npm error peerOptional @babel/plugin-transform-runtime@"^7.29.0 || ^8.0.0-rc.1" from @rolldown/plugin-babel@0.2.3 npm error node_modules/@rolldown/plugin-babel npm error peerOptional @rolldown/plugin-babel@"^0.1.7 || ^0.2.0" from @vitejs/plugin-react@6.1.1 npm error node_modules/@vitejs/plugin-react npm error dev @vitejs/plugin-react@"6.1.1" from the root project npm error npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /tmp/renovate/cache/others/npm/_logs/2026-08-31T18_19_09_611Z-eresolve-report.txt npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-08-31T18_19_09_611Z-debug-0.log ```
renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from c79f958d42
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 24s
Details
CI / Bot/backend version sync (pull_request) Successful in 31s
Details
CI / Backend lint (ruff) (pull_request) Successful in 40s
Details
CI / Docker image build (pull_request) Failing after 24s
Details
CI / Bot tests and audit (pull_request) Successful in 1m17s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 3m33s
Details
to 4378d4fcb3
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 34s
Details
CI / Backend lint (ruff) (pull_request) Successful in 30s
Details
CI / Bot/backend version sync (pull_request) Successful in 23s
Details
CI / Bot tests and audit (pull_request) Successful in 1m38s
Details
CI / Docker image build (pull_request) Failing after 23s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 4m40s
Details
2026-08-24 12:11:43 +00:00 Compare
renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from 4378d4fcb3
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 34s
Details
CI / Backend lint (ruff) (pull_request) Successful in 30s
Details
CI / Bot/backend version sync (pull_request) Successful in 23s
Details
CI / Bot tests and audit (pull_request) Successful in 1m38s
Details
CI / Docker image build (pull_request) Failing after 23s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 4m40s
Details
to 85957ac61d
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 37s
Details
CI / Bot/backend version sync (pull_request) Successful in 23s
Details
CI / Backend lint (ruff) (pull_request) Successful in 25s
Details
CI / Docker image build (pull_request) Failing after 16s
Details
CI / Bot tests and audit (pull_request) Successful in 1m58s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m54s
Details
2026-08-26 00:11:18 +00:00 Compare
renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from 85957ac61d
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 37s
Details
CI / Bot/backend version sync (pull_request) Successful in 23s
Details
CI / Backend lint (ruff) (pull_request) Successful in 25s
Details
CI / Docker image build (pull_request) Failing after 16s
Details
CI / Bot tests and audit (pull_request) Successful in 1m58s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m54s
Details
to ed7168b918
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 43s
Details
CI / Docker image build (pull_request) Failing after 19s
Details
CI / Bot/backend version sync (pull_request) Successful in 21s
Details
CI / Backend lint (ruff) (pull_request) Successful in 27s
Details
CI / Bot tests and audit (pull_request) Successful in 1m43s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m23s
Details
2026-08-26 06:11:07 +00:00 Compare
renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from ed7168b918
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 43s
Details
CI / Docker image build (pull_request) Failing after 19s
Details
CI / Bot/backend version sync (pull_request) Successful in 21s
Details
CI / Backend lint (ruff) (pull_request) Successful in 27s
Details
CI / Bot tests and audit (pull_request) Successful in 1m43s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m23s
Details
to 8de6d4740c
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 28s
Details
CI / Bot/backend version sync (pull_request) Successful in 26s
Details
CI / Backend lint (ruff) (pull_request) Successful in 1m9s
Details
CI / Bot tests and audit (pull_request) Successful in 2m39s
Details
CI / Docker image build (pull_request) Failing after 2m39s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 8m0s
Details
2026-08-28 06:10:31 +00:00 Compare
renovate-bot changed title from chore(deps): update dependency @vitejs/plugin-react to v6.1.0 to chore(deps): update dependency @vitejs/plugin-react to v6.1.1 2026-08-28 06:10:32 +00:00
renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from 8de6d4740c
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 28s
Details
CI / Bot/backend version sync (pull_request) Successful in 26s
Details
CI / Backend lint (ruff) (pull_request) Successful in 1m9s
Details
CI / Bot tests and audit (pull_request) Successful in 2m39s
Details
CI / Docker image build (pull_request) Failing after 2m39s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 8m0s
Details
to 4182676b1e
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 1m10s
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m51s
Details
CI / Backend lint (ruff) (pull_request) Successful in 42s
Details
CI / Bot/backend version sync (pull_request) Successful in 55s
Details
CI / Docker image build (pull_request) Failing after 45s
Details
CI / Bot tests and audit (pull_request) Successful in 2m50s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m13s
Details
2026-08-29 00:12:39 +00:00 Compare
renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from 4182676b1e
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 1m10s
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m51s
Details
CI / Backend lint (ruff) (pull_request) Successful in 42s
Details
CI / Bot/backend version sync (pull_request) Successful in 55s
Details
CI / Docker image build (pull_request) Failing after 45s
Details
CI / Bot tests and audit (pull_request) Successful in 2m50s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m13s
Details
to e9ee8b3b2b
Some checks failed
renovate/artifacts Artifact file update failure
CI / Bot/backend version sync (pull_request) Successful in 56s
Details
CI / Frontend tests, audit, and build (pull_request) Failing after 1m6s
Details
CI / Backend lint (ruff) (pull_request) Successful in 1m9s
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m47s
Details
CI / Docker image build (pull_request) Failing after 2m17s
Details
CI / Bot tests and audit (pull_request) Successful in 2m29s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 7m35s
Details
2026-08-29 12:09:41 +00:00 Compare
renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from e9ee8b3b2b
Some checks failed
renovate/artifacts Artifact file update failure
CI / Bot/backend version sync (pull_request) Successful in 56s
Details
CI / Frontend tests, audit, and build (pull_request) Failing after 1m6s
Details
CI / Backend lint (ruff) (pull_request) Successful in 1m9s
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m47s
Details
CI / Docker image build (pull_request) Failing after 2m17s
Details
CI / Bot tests and audit (pull_request) Successful in 2m29s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 7m35s
Details
to 5764608d83
Some checks failed
renovate/artifacts Artifact file update failure
CI / Backend lint (ruff) (pull_request) Successful in 27s
Details
CI / Docker image build (pull_request) Failing after 34s
Details
CI / Bot/backend version sync (pull_request) Successful in 35s
Details
CI / Frontend tests, audit, and build (pull_request) Failing after 41s
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 45s
Details
CI / Bot tests and audit (pull_request) Successful in 1m15s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m2s
Details
2026-08-30 00:27:42 +00:00 Compare
renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from 5764608d83
Some checks failed
renovate/artifacts Artifact file update failure
CI / Backend lint (ruff) (pull_request) Successful in 27s
Details
CI / Docker image build (pull_request) Failing after 34s
Details
CI / Bot/backend version sync (pull_request) Successful in 35s
Details
CI / Frontend tests, audit, and build (pull_request) Failing after 41s
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 45s
Details
CI / Bot tests and audit (pull_request) Successful in 1m15s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m2s
Details
to 5459059b28
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 26s
Details
CI / Backend lint (ruff) (pull_request) Successful in 25s
Details
CI / Docker image build (pull_request) Failing after 20s
Details
CI / Bot tests and audit (pull_request) Successful in 1m21s
Details
CI / Bot/backend version sync (pull_request) Successful in 53s
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 2m18s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 12m30s
Details
2026-08-31 06:23:45 +00:00 Compare
claude-bot commented 2026-08-31 18:16:12 +00:00
Collaborator
Copy link

This one is not the runner-disk problem that was failing the other Renovate PRs (those were OSError: [Errno 28] No space left on device, now fixed). It has failed identically across six runs — 7173, 7320, 7417, 7502, 7581, 7719 — and would keep failing on any number of retries.

What is actually wrong. package.json on this branch says @vitejs/plugin-react: 6.1.1; package-lock.json still says 6.0.5. The renovate/artifacts: failure status on this PR is the cause, not a side effect — Renovate's lockfile-update step failed, so it pushed the manifest bump with a stale lock, and CI then can't install:

npm error Found: @vitejs/plugin-react@6.0.5
npm error   dev @vitejs/plugin-react@"6.1.1" from the root project
npm error Conflicting peer dependency: @babel/core@8.0.1
npm error   peer @babel/core@"^8.0.0" from @babel/plugin-transform-runtime@8.0.1
npm error     peerOptional @babel/plugin-transform-runtime@"^7.29.0 || ^8.0.0-rc.1" from @rolldown/plugin-babel@0.2.3
npm error       peerOptional @rolldown/plugin-babel@"^0.1.7 || ^0.2.0" from @vitejs/plugin-react@6.1.1

6.1.1 added @rolldown/plugin-babel as an optional peer, and npm tries to satisfy that chain, landing on @babel/plugin-transform-runtime@8.0.1, which needs @babel/core@^8. The tree has @babel/core@7.29.7.

It is not an upstream block, though — it is an artifact of incremental resolution. Reproduced locally, then tested the distinction:

  • npm install --package-lock-only against the existing lock → the ERESOLVE above.
  • Same package.json, lockfile deleted, resolved from scratch → succeeds.

The from-scratch resolution keeps @babel/core at 7.29.7 and does not pull in @rolldown/plugin-babel or @babel/plugin-transform-runtime at all — the optional peers stay unresolved, which is the correct outcome. npm only hits the conflict when it tries to reconcile against the pinned 6.0.5 tree instead of re-planning.

Verified fix — bump package.json to 6.1.1, delete package-lock.json, regenerate, on Node 22 as CI uses:

  • npm ci — clean
  • npm run lint — 0 errors (1 pre-existing react-hooks/exhaustive-deps warning, also present on main)
  • npm test — 43 files, 465 tests passed
  • npm run build — succeeds, PWA precache generated
  • 0 vulnerabilities

Cost of the fix: a full regen touches 62 transitive versions, but adds 0 packages and removes 0 — all patch/minor drift in @rollup/* and @rolldown/* platform bindings, @csstools/*, @jridgewell/sourcemap-codec and similar. No structural change to the tree.

That is a wider diff than a single-dependency PR should carry, so it is a judgement call whether to land it here or as a deliberate lockfile-maintenance change. Note renovate.json already has lockFileMaintenance enabled on the Monday schedule, which is exactly the mechanism for the 62-package half of it.

Also worth noting: this branch is a long way behind main now, so it needs a rebase regardless of the lockfile.

This one is **not** the runner-disk problem that was failing the other Renovate PRs (those were `OSError: [Errno 28] No space left on device`, now fixed). It has failed identically across six runs — 7173, 7320, 7417, 7502, 7581, 7719 — and would keep failing on any number of retries. **What is actually wrong.** `package.json` on this branch says `@vitejs/plugin-react: 6.1.1`; `package-lock.json` still says `6.0.5`. The `renovate/artifacts: failure` status on this PR is the cause, not a side effect — Renovate's lockfile-update step failed, so it pushed the manifest bump with a stale lock, and CI then can't install: ``` npm error Found: @vitejs/plugin-react@6.0.5 npm error dev @vitejs/plugin-react@"6.1.1" from the root project npm error Conflicting peer dependency: @babel/core@8.0.1 npm error peer @babel/core@"^8.0.0" from @babel/plugin-transform-runtime@8.0.1 npm error peerOptional @babel/plugin-transform-runtime@"^7.29.0 || ^8.0.0-rc.1" from @rolldown/plugin-babel@0.2.3 npm error peerOptional @rolldown/plugin-babel@"^0.1.7 || ^0.2.0" from @vitejs/plugin-react@6.1.1 ``` 6.1.1 added `@rolldown/plugin-babel` as an optional peer, and npm tries to satisfy that chain, landing on `@babel/plugin-transform-runtime@8.0.1`, which needs `@babel/core@^8`. The tree has `@babel/core@7.29.7`. **It is not an upstream block, though — it is an artifact of incremental resolution.** Reproduced locally, then tested the distinction: - `npm install --package-lock-only` against the existing lock → the ERESOLVE above. - Same `package.json`, **lockfile deleted**, resolved from scratch → succeeds. The from-scratch resolution keeps `@babel/core` at 7.29.7 and does **not** pull in `@rolldown/plugin-babel` or `@babel/plugin-transform-runtime` at all — the optional peers stay unresolved, which is the correct outcome. npm only hits the conflict when it tries to reconcile against the pinned 6.0.5 tree instead of re-planning. **Verified fix** — bump `package.json` to 6.1.1, delete `package-lock.json`, regenerate, on Node 22 as CI uses: - `npm ci` — clean - `npm run lint` — 0 errors (1 pre-existing `react-hooks/exhaustive-deps` warning, also present on `main`) - `npm test` — 43 files, 465 tests passed - `npm run build` — succeeds, PWA precache generated - 0 vulnerabilities **Cost of the fix:** a full regen touches 62 transitive versions, but **adds 0 packages and removes 0** — all patch/minor drift in `@rollup/*` and `@rolldown/*` platform bindings, `@csstools/*`, `@jridgewell/sourcemap-codec` and similar. No structural change to the tree. That is a wider diff than a single-dependency PR should carry, so it is a judgement call whether to land it here or as a deliberate lockfile-maintenance change. Note `renovate.json` already has `lockFileMaintenance` enabled on the Monday schedule, which is exactly the mechanism for the 62-package half of it. Also worth noting: this branch is a long way behind `main` now, so it needs a rebase regardless of the lockfile.
renovate-bot force-pushed renovate/vitejs-plugin-react-6.x from 5459059b28
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 26s
Details
CI / Backend lint (ruff) (pull_request) Successful in 25s
Details
CI / Docker image build (pull_request) Failing after 20s
Details
CI / Bot tests and audit (pull_request) Successful in 1m21s
Details
CI / Bot/backend version sync (pull_request) Successful in 53s
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 2m18s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 12m30s
Details
to b7d081e8f2
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 47s
Details
CI / Bot/backend version sync (pull_request) Successful in 32s
Details
CI / Backend lint (ruff) (pull_request) Successful in 35s
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m15s
Details
CI / Bot tests and audit (pull_request) Successful in 1m18s
Details
CI / Docker image build (pull_request) Failing after 28s
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m31s
Details
2026-08-31 18:19:20 +00:00 Compare
claude-bot commented 2026-08-31 20:11:13 +00:00
Collaborator
Copy link

Superseded by #471, merged as 03ca81c. @vitejs/plugin-react is on 6.1.1 on main, so this branch has nothing left to do — closing.

To be explicit for Renovate's benefit: this is not a rejection of the update. The update itself has landed. Closing a Renovate PR is normally the "don't offer this again" signal, which is why I left this PR alone until the replacement was actually merged rather than closing and reopening it earlier to force a CI re-run.

The one-line summary of why it could never go green on its own: Renovate could not regenerate the lockfile (renovate/artifacts failed on every attempt, including after the post-disk-fix rebase), so the branch carried package.json at 6.1.1 against a lockfile still pinning 6.0.5. #471 fixes the underlying resolution failure with a single overrides entry, which keeps the lockfile diff to just the plugin instead of the 61 transitive bumps a full regen would have brought.

Worth expecting: with that override on main, Renovate's artifact step should now succeed on future @vitejs/plugin-react bumps rather than failing this same way again. If a future one does fail like this, the override in webapp/frontend/package.json is the first thing to look at — it is documented under "Important constraints" in webapp/CLAUDE.md, including the condition for removing it (the frontend moving to Babel 8).

Superseded by #471, merged as `03ca81c`. `@vitejs/plugin-react` is on 6.1.1 on `main`, so this branch has nothing left to do — closing. **To be explicit for Renovate's benefit:** this is not a rejection of the update. The update itself has landed. Closing a Renovate PR is normally the "don't offer this again" signal, which is why I left this PR alone until the replacement was actually merged rather than closing and reopening it earlier to force a CI re-run. The one-line summary of why it could never go green on its own: Renovate could not regenerate the lockfile (`renovate/artifacts` failed on every attempt, including after the post-disk-fix rebase), so the branch carried `package.json` at 6.1.1 against a lockfile still pinning 6.0.5. #471 fixes the underlying resolution failure with a single `overrides` entry, which keeps the lockfile diff to just the plugin instead of the 61 transitive bumps a full regen would have brought. Worth expecting: with that override on `main`, Renovate's artifact step should now succeed on future `@vitejs/plugin-react` bumps rather than failing this same way again. If a future one does fail like this, the override in `webapp/frontend/package.json` is the first thing to look at — it is documented under "Important constraints" in `webapp/CLAUDE.md`, including the condition for removing it (the frontend moving to Babel 8).
claude-bot closed this pull request 2026-08-31 20:11:14 +00:00
Some checks failed
renovate/artifacts Artifact file update failure
CI / Frontend tests, audit, and build (pull_request) Failing after 47s
Required
Details
CI / Bot/backend version sync (pull_request) Successful in 32s
Required
Details
CI / Backend lint (ruff) (pull_request) Successful in 35s
Required
Details
CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 1m15s
Required
Details
CI / Bot tests and audit (pull_request) Successful in 1m18s
Required
Details
CI / Docker image build (pull_request) Failing after 28s
Required
Details
CI / Backend migration, tests, and audit (pull_request) Successful in 5m31s
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
backend
Issue related to the backend

  
bot
Issue related to the bot

  
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
frontend
Issue related to the frontend

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
recording
Issue related to the recording system

  
security
Security hardening / vulnerability work

  
wontfix
This won't be fixed

No labels
backend
bot
bug
duplicate
enhancement
frontend
help wanted
invalid
question
recording
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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
rbrooks/Quest-Board!316
No description provided.