chore: version packages - #3511
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
12 times, most recently
from
September 27, 2026 23:24
69edb61 to
0cbbf21
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 28, 2026 08:15
0cbbf21 to
739ae6d
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 28, 2026 08:30
739ae6d to
07318f9
Compare
@vinext/cloudflare
create-vinext-app
@vinext/types
vinext
@cloudflare/workers-response-store
commit: |
Contributor
Author
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
10 times, most recently
from
September 28, 2026 12:51
9a36d29 to
0d8dd12
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 28, 2026 12:57
0d8dd12 to
752beaa
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@vinext/cloudflare@1.0.0
Features
useSearchParams()and client pagesearchParamson cacheable App Router pages: server rendering shows the nearest<Suspense>fallback and the browser renders the real query after hydration (feat(app-router): gate SSR useSearchParams() in cache-candidate renders #3455, fix(app-router): build client page searchParams in SSR and the browser #3457)revalidate = false, never store a render that used a dynamic API, and send Next.js's never-cache header on pages that can't be static (fix(app-router): only full-page cache routes Next.js classifies as static or SSG #3451, fix(app-router): default static and SSG routes to revalidate = false #3452, fix(app-router): send Next.js's never-cache header for known-dynamic App pages #3453, feat(app-router): track dynamic usage in a per-request sticky latch #3454, feat(app-router): skip core cache writes without a negative searchParams proof #3456, feat(app-router): admit rendered App pages only with a negative searchParams proof #3461, fix(app-router): skip the core ISR cache for a path Workers Cache never admits #3489, fix(fetch-cache): leave a revalidate = false page indefinite after a fetch without a numeric revalidate #3500)Bug Fixes
Cloudflare
Misc
ttlSeconds, includingrevalidate = falsepages, raising values below 60 to KV's minimum, and stop expiring tag invalidation markers (fix(cloudflare): give every KV entry the configured TTL #3488)Contributors
create-vinext-app@1.0.0
Features
Contributors
@vinext/types@1.0.0
vinext@1.0.0
Features
useSearchParams()and client pagesearchParamson cacheable App Router pages: server rendering shows the nearest<Suspense>fallback and the browser renders the real query after hydration (feat(app-router): gate SSR useSearchParams() in cache-candidate renders #3455, fix(app-router): build client page searchParams in SSR and the browser #3457)revalidate = false, never store a render that used a dynamic API, and send Next.js's never-cache header on pages that can't be static (fix(app-router): only full-page cache routes Next.js classifies as static or SSG #3451, fix(app-router): default static and SSG routes to revalidate = false #3452, fix(app-router): send Next.js's never-cache header for known-dynamic App pages #3453, feat(app-router): track dynamic usage in a per-request sticky latch #3454, feat(app-router): skip core cache writes without a negative searchParams proof #3456, feat(app-router): admit rendered App pages only with a negative searchParams proof #3461, fix(app-router): skip the core ISR cache for a path Workers Cache never admits #3489, fix(fetch-cache): leave a revalidate = false page indefinite after a fetch without a numeric revalidate #3500)Bug Fixes
Check
Cloudflare
Misc
generateStaticParamsthe parent params from a route's own layouts rather than from a sibling page (fix(app-router): take a route's parent params from its layouts, not a sibling page #3493)Contributors
@cloudflare/workers-response-store@1.0.0