mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-04 11:01:16 +01:00
Devin FoleyandClaude Opus 5.5
ccee3e4493
<!-- Write all pull request text in Simplified Technical English (ASD-STE100): short sentences, one instruction per sentence, simple approved vocabulary, and the active voice. --> ## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work. > - Each stable release publishes curated release notes as its GitHub Release body. > - The stable release workflow reads `releases/beta/v2026.1023.0-beta.0.md` from master when it starts. It publishes that exact revision. > - The beta notes have a guessed version and date (v2026.1026.0, 2026-10-26). That version did not ship. > - An audit of the notes against the commit range also found a wrong contributor count and three missing fixes for self-hosted users. > - This pull request corrects the notes before the stable release starts. > - The benefit is that the v2026.1103.0 release page shows the correct version, date, counts, and fixes. ## Linked Issues or Issue Description Refs #17388 (the curated notes for the `2026.1023.0-beta.0` soak). **Problem** The stable notes for the promotion of `2026.1023.0-beta.0` show v2026.1026.0 and the date 2026-10-26. `scripts/release.sh stable --print-version --date 2026-11-03` on master gives `2026.1103.0`. The notes also have a contributor count that does not match the release convention, and they do not include three user-facing fixes. **Expected result** The notes show `# Paperclip v2026.1103.0` and `> Released: 2026-11-03`. The counts and the cited fixes match the range `v2026.1023.0..d69631b01b9c658f80bf8bed389863dce82643e1`. **Impact** The stable workflow publishes these notes as the GitHub Release body. If this pull request does not merge before the release starts, the release page shows the incorrect version and date. ## What Changed - Set the H1 to `# Paperclip v2026.1103.0`, the release line to `> Released: 2026-11-03`, and the version in the intro paragraph. - Changed the contributor count from 26 to 27. `git shortlog -sn v2026.1023.0..d69631b` without `github-actions[bot]` gives 27 authors. This is the same rule as the v2026.1023.0 and v2026.1012.0 notes, which count `dependabot[bot]`. The list of 21 credited handles does not change. - Added three fixes that self-hosted users can see and that the notes did not cite: - #16357: when you stop a queued run before it starts, its saved follow-up stays saved and does not run (Runs, recovery, and Retry). - #17259: if a sandbox has a preinstalled Claude CLI that is too old for the selected model, setup installs the required version privately (Adapters and CLI). - #16494: the Slack eyes reaction also works in direct messages (Slack highlight). - No other text changes. The diff is 7 lines in one file. ## Verification - `git rev-list --count v2026.1023.0..d69631b01b9c658f80bf8bed389863dce82643e1` = 515. This matches the notes. - All 255 cited PR numbers are in that range. Eight squash commits in the range have no `(#N)` suffix. The commits-to-pulls API maps them to #16356, #16976, #16441, #16403, #16404, #16401, #14180, and #16215. - Of the 260 PRs in the range that the notes do not cite, the audit found them to be tests, CI, refactors, docs, performance internals, or follow-up fixes to features that this release adds and the notes already describe. Six are Paperclip Cloud-only (#16953, #16907, #16876, #16254, #16033, #16259), and the notes do not include them. One is a hidden, default-off pilot (#16984). - The migrations in the range are `0334`–`0374` (41 files). This matches the Upgrade Guide. The defaults for the new environment variables in `server/src/config.ts` and `server/src/sentry-run-failure-policy.ts` match the Upgrade Guide. - The handles @lucktastic and @MindSyncHub come from the commit author records. - The file on this branch has blob `ef11a77a4b267b9f8d459900ba7b43098841c410`, which is identical to the locally checked edit. ## Risks - Low risk. This is a change to documentation only, in one file. - After this pull request merges, the stable workflow publishes the merged revision as the release body. If the release starts after 2026-11-03 UTC, the workflow uses `stable_date=2026-11-03` so that the version stays the same as the header. ## Model Used - Claude Opus 5.5 (`claude-opus-5-5`) through Claude Code, with tool use (shell, git, GitHub API). Used for the notes audit and the edits. ## 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 (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [ ] I have run tests locally and they pass (documentation only; no tests apply) - [ ] I have added or updated tests where applicable (not applicable) - [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 - [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>