Files
PaperClipAI/releases/beta
ce8006de3c docs(release): stable notes for the 2026.1120.0-beta.0 soak (v2026.1123.0) (#22372)
## 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.1120.0-beta.0` published in workflow run 44647487455. Its
`draft_stable_notes` job pushed a commit-log skeleton to this branch
> - The skeleton is a raw commit list. It is not usable as release notes
> - This pull request replaces the skeleton with curated stable notes.
Each claim traces to a pull request in `v2026.1117.0..28043f8b`
> - The benefit is that the stable promotion for this beta
(v2026.1123.0) finds finished notes on `master`

## Linked Issues or Issue Description

**Issue type**

Missing content

**Where is the issue?**

`releases/beta/v2026.1120.0-beta.0.md` is the stable-notes file for the
`2026.1120.0-beta.0` soak. At the branch head before this commit, it
holds only the auto-generated commit-log skeleton.

**What's wrong?**

The stable promotion reads this file from `master` and publishes it as
the GitHub Release body. A raw commit list is not suitable as a release
body.

**Suggested fix**

Merge the curated notes. Correct the H1 and the `> Released:` line in a
follow-up if the promotion date moves.

## What Changed

- Replaced the skeleton in `releases/beta/v2026.1120.0-beta.0.md` with
curated stable notes for v2026.1123.0, in the same layout as
`releases/v2026.1117.0.md`: overview, Breaking Changes, Highlights,
Improvements, Fixes, Upgrade Guide, Contributors
- The notes are delta-framed against `releases/v2026.1117.0.md`.
Features that the previous stable already describes are not repeated
- The Upgrade Guide lists migrations `0452` through `0499` with
one-phrase effects, the new environment variables with defaults, and the
bundled harness pins
- 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.1120.0-beta.0`,
tag `beta/v2026.1120.0-beta.0` points at
`28043f8b93fa208ac83f96946953d05e7ba1dfd3`, and `publish_beta`, both
`smoke_beta` jobs and `draft_stable_notes` in run 44647487455 succeeded.
The beta Docker build (run 44679279012) succeeded
- `git rev-list --count
v2026.1117.0..28043f8b93fa208ac83f96946953d05e7ba1dfd3` returns 1222,
which matches the overview and Contributors section
- Contributors are the 16 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
- Every `#NNNN` link in the file traces to a commit in the range (294
cited pull requests)
- 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 diff changes one file under `releases/` and no source files

## Risks

- Low risk: a single markdown file, no source changes. If the promotion
date moves past 2026-11-23, the H1 and `> Released:` line need a
one-line update before the stable dispatch
- The `draft_stable_notes` job force-pushes this branch name. A rerun of
that job replaces this commit with the skeleton. Do not rerun it for
this beta

## 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
- [ ] I have run tests locally and they pass
- [ ] 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: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: devinfoley <139239+devinfoley@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 23:06:37 -08:00
..