Skip to content

chore: version packages - #1759

Merged
james-elicx merged 2 commits into
mainfrom
changeset-release/main
Jun 8, 2026
Merged

chore: version packages#1759
james-elicx merged 2 commits into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

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

Build

Pages Router

Misc

Performance

Contributors

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 4 times, most recently from 41befeb to 398ba5c Compare June 5, 2026 14:12
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 398ba5c to d6562ac Compare June 5, 2026 14:17
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
github-actions Bot force-pushed the changeset-release/main branch from d6562ac to e805c0a Compare June 5, 2026 14:19
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from e805c0a to 5b4f4f9 Compare June 5, 2026 14:34
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
github-actions Bot force-pushed the changeset-release/main branch 18 times, most recently from 59d8f0d to 9c206f6 Compare June 6, 2026 12:36
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 4de8e57 to b190b9b Compare June 6, 2026 23:19
@james-elicx

james-elicx commented Jun 6, 2026

Copy link
Copy Markdown
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
github-actions Bot force-pushed the changeset-release/main branch 17 times, most recently from 4970b03 to aeb0fca Compare June 7, 2026 22:17
Comment thread packages/vinext/CHANGELOG.md
Comment thread packages/vinext/CHANGELOG.md Outdated
Comment thread packages/vinext/CHANGELOG.md Outdated
@pkg-pr-new

pkg-pr-new Bot commented Jun 8, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@vinext/cloudflare@1759
npm i https://pkg.pr.new/vinext@1759

commit: b2f3dd9

@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor Author
Example Preview Production Original
app-router-cloudflare preview production
pages-router-cloudflare preview production
app-router-playground preview production original
realworld-api-rest preview production
nextra-docs-template preview production
benchmarks preview production
hackernews preview production original
workers-cache preview production
web preview production

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 67ec90a to 007b886 Compare June 8, 2026 09:40
@james-elicx
james-elicx enabled auto-merge (squash) June 8, 2026 09:43
@james-elicx
james-elicx merged commit 2b2ed00 into main Jun 8, 2026
51 checks passed
@james-elicx
james-elicx deleted the changeset-release/main branch June 8, 2026 09:45
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.

1 participant