chore: version packages - #1759
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
June 5, 2026 14:12
41befeb to
398ba5c
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 5, 2026 14:17
398ba5c to
d6562ac
Compare
james-elicx
added a commit
that referenced
this pull request
Jun 5, 2026
…es get entries (#1761) version.mts computed the changelog/contributor commit range from a tag ref derived from the package's pre-bump package.json version (`tagRefFor(name, before[name])`). For a brand-new package that has never been released there is no matching tag, so this produced a non-existent ref (e.g. `v0.0.1`); `git log v0.0.1..HEAD` throws, the catch returns [], and the package gets an empty `## <version>` changelog section with zero entries and zero contributors. This happened for real in #1759: the new @vinext/cloudflare package got an empty `## 1.0.0` heading while vinext (with a real tag) got a full changelog. Reuse `releaseRangeStart(name)` from create-changeset.mts, which resolves the range from the latest *existing* tag (scoped `<name>@<version>` or legacy global `v<version>`) and falls back to the first commit when none exists. This makes version.mts consistent with the changeset generator and supports new/untagged packages. The now-unused `tagRefFor` import is dropped. Extracts the pure tag-selection logic into `latestTagVersionFromTags` and adds focused unit tests for the scoped/global/new-package/no-tag cases.
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 5, 2026 14:19
d6562ac to
e805c0a
Compare
This was referenced Jun 5, 2026
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 5, 2026 14:34
e805c0a to
5b4f4f9
Compare
james-elicx
added a commit
that referenced
this pull request
Jun 5, 2026
…every vinext bump (#1764) Changesets' shouldBumpMajor rule force-bumps a dependent to MAJOR when a peerDependency receives any non-patch bump. Combined with workspace:* being resolved as an exact version pin (always out of range on any vinext change), @vinext/cloudflare was majored on essentially every release (e.g. 0.0.1 -> 1.0.0 in PR #1759), even with zero cloudflare changes. Fix is two parts: - .changeset/config.json: enable onlyUpdatePeerDependentsWhenOutOfRange so peer-dependent bumps respect the declared range instead of force-majoring. - packages/cloudflare/package.json: widen the published peer range off the exact-pin (workspace:* -> >=0.0.0). devDependencies.vinext: workspace:* is kept so local linking is unaffected.
github-actions
Bot
force-pushed
the
changeset-release/main
branch
18 times, most recently
from
June 6, 2026 12:36
59d8f0d to
9c206f6
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 6, 2026 23:19
4de8e57 to
b190b9b
Compare
Member
|
header before merge: Today's release contains several app router bundling improvements like code splitting and lazy loading for faster cold starts, and minification by default for smaller bundles. Several CLI crashes were fixed for large projects, and more Next.js parity gaps were addressed. Vinext now supports additional configuration for caching -- the Vite plugin supports a cache object, where adapters for a data cache and a cdn cache can be supplied. The cdn adapter is intended to be used for route-level caching, while the data adapter is used for everything else, and is used for route caching in the absence of a cdn adapter. This is intended to replace manual setup in the Worker. import vinext from "vinext";
import { kvDataAdapter } from "@vinext/cloudflare/cache/kv-data-adapter";
vinext({
cache: { data: kvDataAdapter() },
}) |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
17 times, most recently
from
June 7, 2026 22:17
4970b03 to
aeb0fca
Compare
james-elicx
reviewed
Jun 8, 2026
james-elicx
reviewed
Jun 8, 2026
james-elicx
reviewed
Jun 8, 2026
commit: |
Contributor
Author
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 8, 2026 09:40
67ec90a to
007b886
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@0.1.0
Features
Contributors
vinext@0.1.0
Features
Cache
Misc
Bug Fixes
App Router
</body></html>suffix #1532) (fix(app-router): ensure streamed SSR body ends with </body></html> (#1532) #1624)Build
Pages Router
api.bodyParser.sizeLimitandbodyParser: falsenot enforced #1479) (fix(pages-router): make req async-iterable for bodyParser: false (#1479) #1678)instrumentation-client.tshook does not execute before hydration #1474) (fix(pages-router): run instrumentation-client.ts before hydration (#1474) #1671)Misc
revalidatePathdoes not invalidate cached pages (including rewritten ones) #1486) (fix(cache): attach path tags to prerender-seeded entries so revalidatePath invalidates them #1688)Performance
Contributors