mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-13 07:12:00 +01:00
7b33384446
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work > - The release process promotes a soaked beta to stable. The stable GitHub Release body comes from `releases/beta/v<beta-version>.md` on `master` > - Beta `2026.1110.0-beta.0` published in workflow run 42763789753. Its `draft_stable_notes` job stopped at the 10-minute job timeout while it made the commit-log skeleton for 1,586 commits, so it did not push the skeleton branch > - Without a notes file on `master`, the stable promotion for this beta has no notes to publish > - This pull request adds the curated stable notes on the branch name that the job would have used. Each claim traces to a pull request in `v2026.1106.0..09e24dd` > - The benefit is that the earliest stable promotion (v2026.1113.0) finds finished notes on `master` on time ## Linked Issues or Issue Description **Issue type** Missing content **Where is the issue?** `releases/beta/v2026.1110.0-beta.0.md` is the stable-notes file for the `2026.1110.0-beta.0` soak. It does not exist yet, because the `draft_stable_notes` job in run 42763789753 timed out before it pushed the skeleton. **What's wrong?** The stable promotion reads this file from `master` and publishes it as the GitHub Release body. Until a notes file merges, the stable preflight has no notes to resolve. **Suggested fix** Merge the curated notes so the notes invariant holds for the v2026.1113.0 promotion. Correct the `> Released:` date in a follow-up if the promotion date slips. ## What Changed - Added `releases/beta/v2026.1110.0-beta.0.md` with curated stable notes for v2026.1113.0 in the same layout as `releases/v2026.1106.0.md`: overview, Breaking Changes, Highlights, Improvements, Fixes, Upgrade Guide, Contributors - The notes are delta-framed against `releases/v2026.1106.0.md`. Features that stable already describes are not repeated - Breaking Changes lists the Google Workspace connector gated off by default (#19247), one execution workspace per subtask (#19860), agent-created task trees limited to parent and child (#19312), native agents reporting status through `paperclip_finish`/`paperclip_block` (#18411, #18489), warm-by-default local Codex and OpenCode Runner agents with migration `0443` (#19888), skill packages moving out of PostgreSQL with this release as the rollback floor (#18082), Enter to submit (#19272), and the narrower `pi_local` environment (#14503) - Upgrade Guide enumerates migrations `0375` through `0451` with one-phrase effects, and the new environment variables with defaults - Release and CI internals, smoke specs, canary tooling, Paperclip Cloud work, dependency bumps, and test-only changes are left out ## Verification - Beta publish is complete: npm dist-tag `beta` is `2026.1110.0-beta.0`, tag `beta/v2026.1110.0-beta.0` points at `09e24dd12c36251dd12af2d73dbc715ce990f922`, `publish_beta` and both `smoke_beta` jobs in run 42763789753 succeeded, and the beta Docker build (run 42858086733) succeeded - Stable `v2026.1106.0` is an ancestor of `09e24dd`; `git rev-list --count v2026.1106.0..09e24dd12c36251dd12af2d73dbc715ce990f922` returns 1586, which matches the overview and Contributors section - Contributors are the 37 unique GitHub logins of the commit authors in the range, read from the GitHub API with `[bot]` accounts excluded. External handles are thanked by name - `./scripts/release.sh stable --date 2026-11-13 --print-version` returns `2026.1113.0` - Every `#NNNN` link in the file traces to a commit in `v2026.1106.0..09e24dd` - Migration numbers, setting keys, env var names, and defaults were checked in the code at the source commit, not in commit subjects - The file contains no internal ticket ids or instance-local links - The compare view for this branch shows one added file and no source changes ## Risks - Low risk: a single markdown file, no source changes. If the promotion date slips past 2026-11-13, the `> Released:` line and H1 need a one-line update before the stable dispatch - The `draft_stable_notes` job force-pushes this branch name. A rerun of that job would replace this commit with the skeleton. Do not rerun it for this beta - The notes assume the next stable is promoted from this beta. If a later beta is promoted instead, its own notes file supersedes this one ## Model Used - Claude (Anthropic), model ID `claude-opus-5-5` (Claude Opus 5.5), tool use via Claude Code ## 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 - [x] I have run tests locally and they pass - [x] I have added or updated tests where 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>