Release 4.3.0: production release + node24 CI fix - #76
Merged
Merged
Conversation
* feat(takumi): migrate to takumi-js v2 (2.0.1 stable) takumi-js graduated from beta — 2.0.1 is now the `latest` tag. Bump the pin across the library (dev + peer dep) and every example from 2.0.0-beta.14 to the stable release. No source changes needed: the public API is unchanged between beta.14 and 2.0.1. Verified — lib typecheck 0 errors, vitest 10/10 (incl. takumi render tests), all 8 examples build. * release(package): next version .16 * docs: takumi v2 note; document Deno prerendered-image 404 - usage/takumi: note takumi-js is stable v2 (^2.0.1). - runtime/deno: add Known Issue — prerendered image endpoints (`+server.ts` with prerender = true) are written to the static output but the Deno adapter only registers prerendered pages in its route manifest, not endpoint assets. Deno Deploy serves static from that manifest (not the filesystem), so the route 404s. Workaround: serve image endpoints dynamically on Deno. * fix(deno): patch adapter to serve prerendered image endpoints @deno/svelte-adapter@0.2.1 writes prerendered output to the static dir via writePrerendered(), but only registers builder.prerendered.pages in the deploy.json staticFiles manifest. Prerendered *endpoints* (e.g. /png/prerendered.png) are written to disk but never registered, and Deno Deploy serves static files from that manifest — so those routes 404. Add a pnpm patch that also registers builder.prerendered.assets. Verified: deploy.json now lists all three prerendered image routes, and `deno run -A .deno-deploy/server.ts` serves /png/prerendered.png with 200 (valid 1200x630 PNG). Docs known-issue updated to point at the patch. Upstream fix should land in @deno/svelte-adapter; drop the patch when it does. * fix(repo): pin packageManager to pnpm@10 Vercel's builder defaulted to pnpm@9, which hashes patchedDependencies differently than the pnpm@10-written lockfile, failing frozen install with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH. Pin pnpm 10 via packageManager so all hosts use the same version. * docs(takumi): install from beta tag, next channel retired v4.3 prerelease moved from the next tag to beta (4.3.0-next.16) and is ready for test deployments. * release(package): 4.3.0-beta.1 Retire the next prerelease channel; v4.3 ships from the beta tag now.
* feat(takumi): migrate to takumi-js v2 (2.0.1 stable) takumi-js graduated from beta — 2.0.1 is now the `latest` tag. Bump the pin across the library (dev + peer dep) and every example from 2.0.0-beta.14 to the stable release. No source changes needed: the public API is unchanged between beta.14 and 2.0.1. Verified — lib typecheck 0 errors, vitest 10/10 (incl. takumi render tests), all 8 examples build. * release(package): next version .16 * docs: takumi v2 note; document Deno prerendered-image 404 - usage/takumi: note takumi-js is stable v2 (^2.0.1). - runtime/deno: add Known Issue — prerendered image endpoints (`+server.ts` with prerender = true) are written to the static output but the Deno adapter only registers prerendered pages in its route manifest, not endpoint assets. Deno Deploy serves static from that manifest (not the filesystem), so the route 404s. Workaround: serve image endpoints dynamically on Deno. * fix(deno): patch adapter to serve prerendered image endpoints @deno/svelte-adapter@0.2.1 writes prerendered output to the static dir via writePrerendered(), but only registers builder.prerendered.pages in the deploy.json staticFiles manifest. Prerendered *endpoints* (e.g. /png/prerendered.png) are written to disk but never registered, and Deno Deploy serves static files from that manifest — so those routes 404. Add a pnpm patch that also registers builder.prerendered.assets. Verified: deploy.json now lists all three prerendered image routes, and `deno run -A .deno-deploy/server.ts` serves /png/prerendered.png with 200 (valid 1200x630 PNG). Docs known-issue updated to point at the patch. Upstream fix should land in @deno/svelte-adapter; drop the patch when it does. * fix(repo): pin packageManager to pnpm@10 Vercel's builder defaulted to pnpm@9, which hashes patchedDependencies differently than the pnpm@10-written lockfile, failing frozen install with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH. Pin pnpm 10 via packageManager so all hosts use the same version. * docs(takumi): install from beta tag, next channel retired v4.3 prerelease moved from the next tag to beta (4.3.0-next.16) and is ready for test deployments. * release(package): 4.3.0-beta.1 Retire the next prerelease channel; v4.3 ships from the beta tag now. * chore: format and lint * chore(cloudflare): Dev deployment test * chore(cloudflare): Dev deployment test * chore(examples): cloudflare workers dev deployment
Add release workflow triggered on push to main/dev. Channel is derived from branch + version: main + clean version -> latest dev + -beta.x -> beta any + -next.x -> next Skips when the version is already on npm, so no-bump merges are no-ops. Publishing uses npm Trusted Publishing (OIDC) with provenance — no NPM_TOKEN is stored in the repo. On publish, CI tags v<version> and generates GitHub release notes via changelogithub. Add `pnpm release` (bumpp) for version bumps and document the full release flow in CONTRIBUTING.md. Contributor PRs now target dev.
`npm install -g npm@latest` self-upgrade leaves an inconsistent global install (missing 'sigstore'), so `npm publish --provenance` crashed with MODULE_NOT_FOUND. Node 24 already bundles npm >= 11.5.1 with OIDC Trusted Publishing support, so pin Node 24 and remove the self-upgrade step.
✅ Deploy Preview for sveltekit-og-dev canceled.
|
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
sveltekit-og | 58c0dfa | Jul 10 2026, 01:05 PM |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for sveltekit-og canceled.
|
This branch was successfully deployed
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
1 participant
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.
Merges
devintomainto publish 4.3.0 to@latest.What reaches main
release.yml: pin Node 24 and drop the brokennpm i -g npm@latestself-upgrade (fixesCannot find module 'sigstore'onnpm publish --provenance).Everything else (release automation, takumi v2, 4.3.0 version bump) is already on
main— this PR's only content delta is the workflow fix.mainwas merged intodevfirst, so this merges cleanly with no conflicts.On merge
Push to
mainwith clean version4.3.0triggers the release workflow → publishes@latestvia OIDC Trusted Publishing (no token). Requires the trusted publisher (repo +release.yml) configured on npmjs.com.