Conversation
fengmk2
force-pushed
the
chore/upgrade-vite-plus-0.3.1
branch
from
September 11, 2026 15:36
45747f7 to
a66b9d9
Compare
* perf(cache): reduce response store Durable Object load * refactor(cache): remove response store compatibility shims * fix(cache): batch response store purge parameters * fix(cache): preserve coalesced response store writes * fix(cache): preserve concurrent response store writes * fix(cache): fence response store tag purges * fix(cache): order tag purge fences durably * fix(cache): migrate response store metadata schema * fix(cache): preserve coalesced purge semantics * fix(cache): isolate coalesced cleanup failures * fix(cache): harden coalesced response store writes * fix(cache): isolate coalesced purge failures * fix(cache): isolate post-commit alarm failures * fix(cache): continue cleanup after alarm errors * fix(cache): fence expired response store cleanup * fix(cache): retain durable cleanup ownership * fix(cache): retain cleanup fences across deletion
fengmk2
force-pushed
the
chore/upgrade-vite-plus-0.3.1
branch
from
September 14, 2026 17:07
a66b9d9 to
91b14b6
Compare
…#3249) * feat(cloudflare): scaffold response store wrangler config * fix(cache): stabilize response store validation * fix(cloudflare): harden response store setup * fix(cloudflare): simplify response store scaffolding * fix(init): reference response store deploy script * test(init): expect response store deploy script
fengmk2
force-pushed
the
chore/upgrade-vite-plus-0.3.1
branch
from
September 14, 2026 17:17
91b14b6 to
353bd25
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Upgrade
vite-plusand thevitealias from0.2.6to0.3.1. Updatevitestand@vitest/coverage-istanbulfrom4.1.10to4.1.11. Dependabot now groups these packages into one update.The release includes Rolldown
1.2.7and Oxc0.148.0. Rolldown PR #10809 fixes the default-parameter scope analysis reported in issue #10779. This error could prevent removal of a dead dynamic import from a server build. The existing production branch-pruning regression passes with the released version.The bundled
tsdownversion changes to0.23.0. The package configurations usedeps.neverBundleand selectdts.generatorexplicitly. They preserve the previous dependency-subpath resolution behavior.Oxlint changes from
1.75.0to1.81.0. Since1.79.0,no-redeclarealso checks ES modules (PR #25691). Two existingnext/documentdeclaration merges therefore need narrow ignores. The upgrade also reports an unused underscore parameter (PR #25663) and React diagnostics that fail withdenyWarnings: true.The lint fixes derive benchmark controls from URL state, reset component state when its input changes, and assert hook values inside test components. Narrow exceptions preserve router ref timing, committed snapshots, client-only mount behavior, and Next.js legacy
Linkref handling. Formatting follows the bundled Oxfmt version.The error overlay resets frame visibility when the error ID changes, without remounting the dialog. This preserves keyboard focus on the pagination buttons, as Next.js does. A browser regression test checks consecutive
Enterpresses in both directions and frame visibility after each error change. The test fails with the earlierkey={current.id}implementation and passes with this fix.The first CI run passed every browser test and integration shard. One unit test exceeded its five-second limit while starting a Vite server. Move
tests/dynamic-requests-build.test.tsto the integration project, which already provides a 30-second limit and bounded parallelism. All 46 tests pass locally without assertion changes.The latest fork CI run passes every unit shard, integration shard, and browser project, including the focus regression. Performance and security checks also pass. Local checks, the package build, 16 overlay browser tests, and 14 overlay unit tests pass. One existing browser test remains skipped.
All ten example builds pass. Their deployment jobs fail because the fork has no Cloudflare credentials. Submitted upstream as cloudflare/vinext#3215.