mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-19 16:29:42 +01:00
<!-- 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.1110.0-beta.0.md` from master when it starts. It publishes that exact revision. > - The notes on master show v2026.1113.0 and the date 2026-11-13. That version did not ship. > - The promotion of `2026.1110.0-beta.0` starts on 2026-11-17, so the version is `2026.1117.0`. > - An audit of the release range also found an incorrect contributor count, user-facing changes that the notes do not cite, and one line that names Cloud deployments. > - This pull request corrects all of these before the stable release starts. > - The benefit is that the release page shows the correct version, date, counts and changes. ## Linked Issues or Issue Description Refs #20610 (the curated notes for the `2026.1110.0-beta.0` soak). **Problem** The stable notes for the promotion of `2026.1110.0-beta.0` show `# Paperclip v2026.1113.0` and `> Released: 2026-11-13`. `scripts/release.sh stable --print-version --date 2026-11-17` on master gives `2026.1117.0`. The Contributors line says 37 contributors. The range has 40. About 70 user-facing PRs in the range are not in the notes. **Expected result** The notes show `# Paperclip v2026.1117.0` and `> Released: 2026-11-17`. The intro names v2026.1117.0. The counts match the range. The notes describe the user-facing changes for self-hosted installs. **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 incorrect data. ## What Changed - Set the H1 to `# Paperclip v2026.1117.0`, the release line to `> Released: 2026-11-17`, and the version in the intro to v2026.1117.0. - Set the contributor count to 40. The credited handles do not change. - Add user-facing fixes that the notes did not cite to the existing **Fixes** groups: Runs, Messages, Costs, Permissions, Workspaces, Adapters, Chat and task UI, Connections, and Server and CLI. - Add seven **Improvements** lines: an experimental Cursor Cloud provider on the Runner, refreshed model catalogs and CLI pins, AI account and connector sign-in changes, task page and composer changes, routine task links, the standalone phone app, and the skill update diff endpoint. - Add one line to the Upgrade Guide: first-agent onboarding offers only Claude and Codex. - Change the `0437`/`0440` migration sentence so it does not name Cloud deployments. - One file changes. No text outside `releases/` changes. ## Verification - `scripts/release.sh stable --print-version --date 2026-11-17` on master gives `2026.1117.0`. - The file has no `1113` or `2026-11-13` strings after the change. - Audit against `v2026.1106.0..09e24dd12c36251dd12af2d73dbc715ce990f922` (the `beta/v2026.1110.0-beta.0` source): - `git rev-list --count` = 1,586. This matches the notes. - All 362 cited PR numbers are in the range. - Every PR in the range that the notes do not cite was classified as internal, covered by an existing line, Paperclip Cloud only (kept out), or user-facing. The user-facing ones are added here. - `git shortlog -sn` without `github-actions[bot]` gives 40 contributors. This is the same method as the v2026.1106.0 notes. The 31 credited handles are the same. - The range adds migrations `0375`–`0451` (77 files). This matches the Upgrade Guide. The new environment variables and their defaults match the code at the source commit. - The file on this branch has blob `dff612e41f915a5a2d9f3e572142e2fee56068a8`. ## Risks - Low risk. This is a change to documentation only, in one file. - If the UTC date changes before the release starts, the release workflow keeps `stable_date=2026-11-17` to match this header. ## Model Used - Claude Opus 5.5 (`claude-opus-5-5`), Anthropic, with tool use (shell, git, GitHub API) and parallel subagents (Claude Sonnet 5.5) for the PR classification. Used to compute the version, audit the range, and write the change. ## 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: devinfoley <139239+devinfoley@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>