[PR #124] [MERGED] docs(changelog): stage 0.1.9 for the timeout fix #127

New issue

Closed

opened 2026-10-31 22:04:49 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 22:04:49 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/comfy-typescript-sdk/pull/124
Author: @mattmillerai
Created: 9/4/2026
Status: ✅ Merged
Merged: 9/4/2026
Merged by: @mattmillerai

Base: main ← Head: matt/release-0-1-9

📝 Commits (2)

f42d3ef docs(changelog): section 0.1.8 and stage 0.1.9
d7001f2 Merge branch 'main' into matt/release-0-1-9

📊 Changes

1 file changed (+10 additions, -5 deletions)

View changed files

📝 CHANGELOG.md (+10 -5)

📄 Description

Changelog only, ahead of cutting v0.1.9. No code changes.

Rebased onto #112, which cut the 0.1.8 section while this was open. What
remains is the one thing #112 could not have known.

ELI-5

v0.1.8 is on npm. It was tagged at 2bc3f00 and published on 1 September.
The undici timeout fix (#123) merged after that, on 4 September, so it is
not in 0.1.8 and never can be — a published version is immutable. But the
changelog on main currently lists it under ## [0.1.8], which tells anyone
reading it to install 0.1.8 and expect a fix that isn't there.

This moves that entry to its own ## [0.1.9] heading, which is the release
that will actually carry it.

The change

The timeoutMs / undici headersTimeout entry moves from 0.1.8 to a new
## [0.1.9] - 2026-09-04. Everything else stays exactly where #112 put it.
Link references gain 0.1.9; [Unreleased] now compares against v0.1.9.
One sentence rewritten: the routerErrors note said routerErrors "has
never shipped (it is absent from v0.1.7, the latest release on npm)". That
was true when it was written against [Unreleased]. Sitting under a 0.1.8
heading it is wrong twice over — routerErrors ships in 0.1.8, and
v0.1.7 is no longer the latest on npm — so it is now phrased relative to
the release it sits under.

Why 0.1.9 is a patch

Five commits are on main since the v0.1.8 tag. Exactly one is
user-visible — the timeout fix. The other four are two vendored Router spec
syncs and two docs changes, none of which need a changelog entry per
CONTRIBUTING.

Verification

pnpm lint, pnpm format:check, pnpm typecheck, pnpm check:spec-drift
and node scripts/check-public-repo-hygiene.mjs all clean. No source file is
touched, so dist/ and the published surface are unchanged.

After this merges

Cut the GitHub Release v0.1.9 on main, which is what publishes to npm.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/comfy-typescript-sdk/pull/124 **Author:** [@mattmillerai](https://github.com/mattmillerai) **Created:** 9/4/2026 **Status:** ✅ Merged **Merged:** 9/4/2026 **Merged by:** [@mattmillerai](https://github.com/mattmillerai) **Base:** `main` ← **Head:** `matt/release-0-1-9` --- ### 📝 Commits (2) - [`f42d3ef`](https://github.com/Comfy-Org/comfy-typescript-sdk/commit/f42d3ef7b43e869f98986ecffc8aab791d9d57fd) docs(changelog): section 0.1.8 and stage 0.1.9 - [`d7001f2`](https://github.com/Comfy-Org/comfy-typescript-sdk/commit/d7001f287bad4836adabac321bd1d1d18085ecc0) Merge branch 'main' into matt/release-0-1-9 ### 📊 Changes **1 file changed** (+10 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `CHANGELOG.md` (+10 -5) </details> ### 📄 Description Changelog only, ahead of cutting `v0.1.9`. No code changes. Rebased onto #112, which cut the `0.1.8` section while this was open. What remains is the one thing #112 could not have known. ## ELI-5 `v0.1.8` is on npm. It was tagged at `2bc3f00` and published on 1 September. The undici timeout fix (#123) merged **after** that, on 4 September, so it is not in `0.1.8` and never can be — a published version is immutable. But the changelog on `main` currently lists it under `## [0.1.8]`, which tells anyone reading it to install `0.1.8` and expect a fix that isn't there. This moves that entry to its own `## [0.1.9]` heading, which is the release that will actually carry it. ## The change - The `timeoutMs` / undici `headersTimeout` entry moves from `0.1.8` to a new `## [0.1.9] - 2026-09-04`. Everything else stays exactly where #112 put it. - Link references gain `0.1.9`; `[Unreleased]` now compares against `v0.1.9`. - One sentence rewritten: the `routerErrors` note said `routerErrors` "has never shipped (it is absent from `v0.1.7`, the latest release on npm)". That was true when it was written against `[Unreleased]`. Sitting under a `0.1.8` heading it is wrong twice over — `routerErrors` ships *in* `0.1.8`, and `v0.1.7` is no longer the latest on npm — so it is now phrased relative to the release it sits under. ## Why 0.1.9 is a patch Five commits are on `main` since the `v0.1.8` tag. Exactly one is user-visible — the timeout fix. The other four are two vendored Router spec syncs and two docs changes, none of which need a changelog entry per CONTRIBUTING. ## Verification `pnpm lint`, `pnpm format:check`, `pnpm typecheck`, `pnpm check:spec-drift` and `node scripts/check-public-repo-hygiene.mjs` all clean. No source file is touched, so `dist/` and the published surface are unchanged. ## After this merges Cut the GitHub Release `v0.1.9` on `main`, which is what publishes to npm. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 22:04:49 +00:00