Skip to content

chore: prune matured release-age exclusions and align CLAUDE.md to 0.2.7 - #512

Merged
chensid merged 1 commit into
mainfrom
claude/dependency-updates-check-pnpfwm
Aug 1, 2026
Merged

chore: prune matured release-age exclusions and align CLAUDE.md to 0.2.7#512
chensid merged 1 commit into
mainfrom
claude/dependency-updates-check-pnpfwm

Conversation

@chensid

@chensid chensid commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Scope changed. This PR originally carried the vite-plus 0.2.7 upgrade and seven dev-dependency bumps. #511 landed the identical set first, so all of that is now on main and has been dropped here. What remains is the cleanup #511 left behind.

Prune minimumReleaseAgeExclude

#511 made those same upgrades while the versions were still inside pnpm's 24h minimumReleaseAge gate, so loose mode self-appended 24 entries to minimumReleaseAgeExclude.

Every one of them has since matured — checked individually against real publish times, 29–50h old at the time of this commit — which makes each entry a no-op. The list goes back to [].

Verified with vp install --frozen-lockfile, the CI path that re-validates the lockfile against the gate: it passes with no ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION.

Align CLAUDE.md to 0.2.7

#511 did not touch CLAUDE.md, so it still described the 0.2.6 toolchain. Updated to the 0.2.7 bundled pins — tsdown 0.22.13 → 0.22.14; Vite 8.1.5, Rolldown 1.2.0, Vitest 4.1.10, Oxfmt 0.60.0, Oxlint 1.75.0 and oxlint-tsgolint 7.0.2001 are unchanged.

TypeScript — retested, still blocked

typescript stays on ~6.0.3.

The note added in #508 said to revisit only when a Vite+ release bundles a newer tsdown, and 0.2.7 did exactly that — so 7.0.2 was retested against tsdown 0.22.14. It fails identically to 0.22.13:

warn: TypeScript 7.0 does not yet have a stable API and is experimental. Some options will be unavailable.
error: tsgo did not generate dts file for src/preset-full.ts

vp check and vp test both pass under TS 7 and cannot see this — tsgolint typechecks independently of the TypeScript API. Only vp pack catches it, and vp pack backs prepublishOnly. The note now records that the retry happened, so the next person does not repeat it.

Test plan

  • vp install --frozen-lockfile — pass, the gate re-validation that makes the prune safe
  • vp check — pass (132 files formatted, 89 typechecked)
  • vp test run --project unit — 292/292 pass
  • vp pack — all three entries built, attw + publint clean
  • vp run size — budgets unchanged (index 12.35/13 kB, registry 2.45/3 kB, preset-full 989 B/1.5 kB)

No changeset: housekeeping only, nothing about the published package changes — consistent with #506 and #507.

🤖 Generated with Claude Code

https://claude.ai/code/session_01R6AGGmoatgTmzaNWMALktH

@codecov

codecov Bot commented Aug 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (ed497b2) to head (7306111).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #512   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           20        20           
  Lines          648       648           
  Branches       150       150           
=========================================
  Hits           648       648           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

#511 landed the same dependency and vite-plus 0.2.7 upgrades while those
versions were still inside pnpm's 24h minimumReleaseAge gate, so loose
mode self-appended 24 entries to minimumReleaseAgeExclude. Every one of
them has since matured (29-50h at the time of this commit), which makes
the entries no-ops, so the list goes back to empty. Verified with
`vp install --frozen-lockfile` — the CI path that re-validates the
lockfile against the gate.

CLAUDE.md still described the 0.2.6 toolchain, since #511 did not touch
it. Updated to the 0.2.7 bundled pins (tsdown 0.22.13 -> 0.22.14; Vite,
Rolldown, Vitest, Oxfmt, Oxlint and oxlint-tsgolint unchanged).

Also records that TypeScript 7.0.2 was retested against the new tsdown
0.22.14 — the documented trigger for revisiting it — and still fails
`vp pack` with `tsgo did not generate dts file for src/preset-full.ts`,
identical to 0.22.13. typescript stays on ~6.0.3.

No changeset: housekeeping only, nothing about the published package
changes.
@chensid
chensid force-pushed the claude/dependency-updates-check-pnpfwm branch from 1f60493 to 7306111 Compare August 1, 2026 15:15
@chensid chensid changed the title chore: upgrade vite-plus to 0.2.7 and update dev deps chore: prune matured release-age exclusions and align CLAUDE.md to 0.2.7 Aug 1, 2026
@chensid
chensid merged commit c23d381 into main Aug 1, 2026
4 checks passed
@chensid
chensid deleted the claude/dependency-updates-check-pnpfwm branch August 1, 2026 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants