[PR #152] [MERGED] docs(changelog): cut 0.3.0 #152

New issue

Closed

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

bsakaguchi commented

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

Owner

📋 Pull Request Information

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

Base: main ← Head: matt/changelog-cut-0-3-0

📝 Commits (1)

ec09f4f docs(changelog): cut 0.3.0

📊 Changes

1 file changed (+35 additions, -32 deletions)

View changed files

📝 CHANGELOG.md (+35 -32)

📄 Description

ELI-5

Before we tag a release, the changelog needs a heading that says "this is 0.3.0". Right now all the new entries sit under "Unreleased", which is where things wait before they ship. This PR draws the line: everything above that line is 0.3.0, dated today.

Nothing is reworded. The entries are the same ones #130, #132 and #150 already landed.

What changed

## [Unreleased] rolled into ## [0.3.0] - 2026-09-14, exactly as #144 cut 0.2.0.
The three subsections re-emitted in Keep a Changelog order: Added, Changed, Fixed.
[unreleased] compare link repointed — it was still stale at v0.1.9...HEAD after 0.2.0 shipped — and a [0.3.0] link added.

Why 0.3.0 and not 0.2.1

The release carries a new public surface and a behaviour change, so a patch bump would misreport it:

Added — the queued model surface (models.submit / subscribe / handle + RequestHandle), ComfyError.resend_refused, retry.may_have_claimed_key.
Changed — models.run now raises the failure that claimed the key on a refused same-key resend, narrowed to claim-capable failures and keeping the most recent rather than the first.
Fixed — a code-less 409 raises ComfyError instead of guessing HashMismatch.

No version bump here, deliberately

publish.yml is tag-driven: the release tag vX.Y.Z is injected into pyproject.toml at build time, and the committed version = "0.1.0" is a documented placeholder. Bumping it in-tree would be noise at best.

Provenance

Changelog-only. Verified on the merged tree before this cut: 866 passed / 4 skipped, ruff + ruff format --check + mypy clean, check_drift.py green on all three checks.

Release steps after this lands

Create a GitHub Release with tag v0.3.0.
Approve the pypi environment gate — publish sits behind required reviewers.

🤖 Generated with Claude Code

_{🔄 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-python-sdk/pull/152 **Author:** [@mattmillerai](https://github.com/mattmillerai) **Created:** 9/14/2026 **Status:** ✅ Merged **Merged:** 9/14/2026 **Merged by:** [@mattmillerai](https://github.com/mattmillerai) **Base:** `main` ← **Head:** `matt/changelog-cut-0-3-0` --- ### 📝 Commits (1) - [`ec09f4f`](https://github.com/Comfy-Org/comfy-python-sdk/commit/ec09f4f3c7571bb1b364e661ade36a7edba0b1d7) docs(changelog): cut 0.3.0 ### 📊 Changes **1 file changed** (+35 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `CHANGELOG.md` (+35 -32) </details> ### 📄 Description ## ELI-5 Before we tag a release, the changelog needs a heading that says "this is 0.3.0". Right now all the new entries sit under "Unreleased", which is where things wait before they ship. This PR draws the line: everything above that line is 0.3.0, dated today. Nothing is reworded. The entries are the same ones #130, #132 and #150 already landed. ## What changed - `## [Unreleased]` rolled into `## [0.3.0] - 2026-09-14`, exactly as #144 cut 0.2.0. - The three subsections re-emitted in Keep a Changelog order: Added, Changed, Fixed. - `[unreleased]` compare link repointed — it was still stale at `v0.1.9...HEAD` after 0.2.0 shipped — and a `[0.3.0]` link added. ## Why 0.3.0 and not 0.2.1 The release carries a new public surface and a behaviour change, so a patch bump would misreport it: - **Added** — the queued model surface (`models.submit` / `subscribe` / `handle` + `RequestHandle`), `ComfyError.resend_refused`, `retry.may_have_claimed_key`. - **Changed** — `models.run` now raises the failure that *claimed the key* on a refused same-key resend, narrowed to claim-capable failures and keeping the most recent rather than the first. - **Fixed** — a code-less `409` raises `ComfyError` instead of guessing `HashMismatch`. ## No version bump here, deliberately `publish.yml` is tag-driven: the release tag `vX.Y.Z` is injected into `pyproject.toml` at build time, and the committed `version = "0.1.0"` is a documented placeholder. Bumping it in-tree would be noise at best. ## Provenance Changelog-only. Verified on the merged tree before this cut: 866 passed / 4 skipped, ruff + `ruff format --check` + mypy clean, `check_drift.py` green on all three checks. ## Release steps after this lands 1. Create a GitHub Release with tag `v0.3.0`. 2. Approve the `pypi` environment gate — `publish` sits behind required reviewers. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

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