This repository was archived by the owner on Oct 26, 2026. It is now read-only.
Repository navigation
chore(deps): lock vite 8.3.5 and pin next 16.3.8, with no manifest range moved (takes over #13288, #11845) - #13399
Merged
Conversation
…nge moved Takes over Dependabot's objectui#13288 (vite 8.2.2 -> 8.3.4) and objectui#11845 (next 16.3.6 -> 16.3.8), both red since 2026-10-20. - `apps/site` pins `next` 16.3.8, as #11845 did. - vite moves in the lockfile only. Every manifest keeps `"vite": "^8.2.1"`, which already admits 8.3.x. Raising the range, as #13288 did, makes the docs and skill pages that teach the plugin skeleton stale (`doc-version-claims`, `create-plugin` templates), and one of them, `skills/objectui/guides/project-setup.md`, is a governed surface, which is why #13288 could never go green on its own. - `pnpm update -r vite@8.3.4 --no-save`, then `pnpm dedupe`, which lands the whole tree on vite 8.3.5 with postcss and nanoid at one copy each: `check-lockfile-integrity` reads no package gaining a copy (1774 resolutions before and after), where #13288's lock added a second autoprefixer and nanoid. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UBfoEFdVTZ9yyEX5HxsHe4
Contributor
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Tesla · project thread
Takes over two Dependabot PRs that have been red since 2026-10-20 with nobody on them: #13288 (vite 8.2.2 → 8.3.4) and #11845 (next 16.3.6 → 16.3.8). #11844 is the older copy of #11845's bump. Dependabot closes all three by itself once
maincarries these versions.What changes
apps/site/package.json:next16.3.6 → 16.3.8, as chore(deps): Bump next from 16.3.8 to 16.4.1 #11845 did.pnpm-lock.yaml: vite 8.2.2 → 8.3.5 everywhere, next 16.3.8. No manifest's vite range moves: all 31 keep"vite": "^8.2.1", which already admits 8.3.x.Why the vite range stays
#13288 raised every
"vite": "^8.2.1"to"^8.3.4". Measured on that shape, re-applied on currentmain3a73c07b3:scripts/__tests__/doc-version-claims.test.ts› "pins the skeleton toolchain to the range the in-repo plugin packages declare" goes red:content/docs/guide/plugins.md:425andskills/objectui/guides/project-setup.md:48both teach^8.2.1.packages/create-plugin/src/__tests__/templates.test.ts› "sources every devDependency range from this repo instead of inventing them" goes red:templates.ts:109(andpackages/cli/src/utils/scaffold-dependencies.ts:146) hard-code^8.2.1.skills/**, whichcheck-governed-queue-guard.mjs --testreads as GOVERNED, so the whole PR would wait on an authorized approver.So the floor stays where the repo states it, and the upgrade happens in the lockfile. Raising the published floor (
@object-ui/cliand@object-ui/create-pluginhand^8.2.1to scaffolded apps) is a separate change with its own governed page edit, if anyone wants it.Lockfile
pnpm update -r vite@8.3.4 --no-save, thenpnpm dedupe. Dedupe lands the tree on vite 8.3.5 (the newest in range) with one postcss, autoprefixer and nanoid.node scripts/check-lockfile-integrity.mjs --base-ref origin/main:VERDICT clean — no package gained a copy(1774 resolutions, base and head). chore(deps): bump vite from 8.2.2 to 8.3.4 #13288's lock added a second autoprefixer and nanoid, which is the red it carried.node scripts/check-lockfile-dedupe.mjs --report-only:VERDICT deduped.Local verification (head
097db08c0, pin830a63a6built bypnpm run setup)pnpm turbo run type-check --concurrency=2: 81 of 81 tasks successful.vitest run --project unit --maxWorkers=2: Test Files 1656 passed, 3 skipped (1659); Tests 31722 passed, 65 skipped. Thedomanddom-heavyprojects were not run here; CI's 16 shards run them.doc-version-claims.test.ts: 29 of 29 passed.No changeset: only
apps/site(private) and the lockfile change, andcheck-changeset-presencedoes not read dependency fields.🤖 Generated with Claude Code
https://claude.ai/code/session_01UBfoEFdVTZ9yyEX5HxsHe4