From 8f8a0ab7effbd6a0584107d8038736c134ee5047 Mon Sep 17 00:00:00 2001 From: Devin Foley Date: Mon, 21 Sep 2026 13:40:22 -0700 Subject: [PATCH] docs(release): curate stable notes for v2026.916.1 (#13766) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Thinking Path > - Paperclip publishes stable releases from curated notes: the stable promotion reads `releases/beta/v.md` from `master` and publishes it as the GitHub Release body. > - Beta `2026.921.0-beta.0` was just published from a candidate branch carrying the 2026.916.0 source plus the cherry-picked composer fix #13562, headed for patch stable `2026.916.1`. > - Its `draft_stable_notes` job pushed the auto-generated scaffold; this PR rewrites it into release-notes voice so the stable promotion's preflight finds curated notes. ## Linked Issues or Issue Description Notes for the upcoming `2026.916.1` patch stable. The fix being shipped is [#13562](https://github.com/paperclipai/paperclip/pull/13562) (fixes #13561, the desktop chat composer send button starting out disabled). ## What Changed - Rewrote `releases/beta/v2026.921.0-beta.0.md` from the auto-generated commit list into the patch-release format used by `releases/v2026.831.1.md`: what the patch is, the user-facing composer fix, the rode-along document-conflict classification repair, and an upgrade guide (no migrations, no configuration changes). ## Verification - Docs-only change; no code paths affected. - Format matches the prior patch release notes (`releases/v2026.831.1.md`). - The stable promotion will resolve this file from `master` for beta `2026.921.0-beta.0` and canonicalize it to `releases/v2026.916.1.md` after publishing. ## Risks None — documentation only. If the wording needs adjusting during review, the stable dispatch simply waits until this is merged. ## Model Used Anthropic Claude Fable 5 (`claude-fable-5`) via Claude Code, with tool use and code execution. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change and contains no internal Paperclip ticket id or instance-derived details - [x] I have run tests locally and they pass (docs-only; no tests apply) - [x] I have added or updated tests where applicable (none apply) - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [ ] All Paperclip CI gates are green (pending on this fresh PR) - [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups (pending) - [x] I will address all Greptile and reviewer comments before requesting merge --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- releases/beta/v2026.921.0-beta.0.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 releases/beta/v2026.921.0-beta.0.md diff --git a/releases/beta/v2026.921.0-beta.0.md b/releases/beta/v2026.921.0-beta.0.md new file mode 100644 index 00000000000..12ad6b91c40 --- /dev/null +++ b/releases/beta/v2026.921.0-beta.0.md @@ -0,0 +1,14 @@ +# Paperclip v2026.916.1 + +> Released: 2026-09-21 + +A patch on top of [2026.916.0](https://github.com/paperclipai/paperclip/releases/tag/v2026.916.0) that fixes sending messages in the task conversation view. It carries one targeted fix (plus its regression tests and a small server error-classification repair that rode along in the same commit); everything else in 2026.916.0 is unchanged. + +## Fixes + +- **The chat composer's send button no longer starts out disabled on desktop.** The task page disables the composer while it checks whether the task is paused, and in React Query v5 that pending state is true from mount until the first *successful* response — so every desktop task page loaded with the send button disabled, and it stayed disabled for good if the pause-status request stalled. Sends are now allowed while the check is pending: the server remains authoritative and rejects messages to paused tasks with a 409 before saving a comment or waking an agent, and a confirmed pause hold or a failed status check still blocks the composer as before. ([#13562](https://github.com/paperclipai/paperclip/pull/13562)) +- **Duplicate document inserts wrapped by the ORM are classified as retryable conflicts again**, instead of surfacing as opaque database errors; unrelated database failures keep their original identity. (Part of [#13562](https://github.com/paperclipai/paperclip/pull/13562)) + +## Upgrade Guide + +- No migrations, no configuration changes, no API changes. Upgrade in place.