Files
PaperClipAI/releases
Devin Foleyandgithub-actions[bot] 081006bee4 docs(release): curate stable notes for v2026.915.0 (#13487)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work
> - The release system publishes canary, nightly, beta, and stable
channels; a stable promotion publishes its release notes as the GitHub
Release body
> - At beta publish time the workflow auto-drafts a raw commit-log
skeleton on this branch (`releases/beta/v2026.915.0-beta.0.md`) for
humans to edit
> - The skeleton is a 1,800-line commit dump; stable `v2026.915.0`
cannot ship user-facing notes in that form
> - This pull request replaces the skeleton with the curated changelog
for the `v2026.915.0` promotion: overview, breaking changes, highlights,
fixes, upgrade guide, and contributor credits for the 483-commit range
since `v2026.831.1`
> - The benefit is that the stable promotion reads finished, accurate
notes from master and publishes them as the release body

## Linked Issues or Issue Description

Refs #13403, #13247, #13248, #13268, #13256, #13038, #13299 — the
headline features this changelog describes.

The notes-drafting flow itself (skeleton branch at beta publish, stable
promotion reading the file from master, post-ship canonicalization) is
the standing release process; this PR is the curation step it expects.

## What Changed

- Replaced the auto-drafted skeleton in
`releases/beta/v2026.915.0-beta.0.md` with the curated release notes for
stable `v2026.915.0` (promoted from beta `2026.915.0-beta.0`, source
`667c79ded`)
- Sections: overview, Breaking Changes (5), Highlights (Connections
train leads), Improvements, Fixes, Upgrade Guide (migrations
`0231`–`0279`, new env vars, removed API surface), Contributors

## Verification

- Every PR link and claim was checked against the actual commit range
`dbf052577..667c79ded` (the same range the skeleton header names)
- Migration list enumerated from `git log --diff-filter=A` over that
range; only `0231` and `0236` discard data, called out as such
- New environment variables verified in code (`server/src/config.ts`):
announcement flags (default on), split Sentry DSNs with legacy fallback,
token-broker allowed hosts, cwd `.env` opt-out
- Contributor list built from commit authors plus co-author trailers;
core maintainers excluded per release-notes convention
- Docs-only change: no code paths, no tests to add

## Risks

- Low risk: documentation only. The stable promotion reads this file
from master at dispatch time; if wording needs a follow-up after merge,
the promotion pins the master revision it resolved, so edits must land
before the stable dispatch
- The file is renamed to `releases/v2026.915.0.md` by the post-ship
canonicalization step, as with previous promotions

## Model Used

Claude Fable 5 (`claude-fable-5`), extended thinking with tool use
(Claude Code). The commit-range analysis and draft were produced by a
subagent on the same model and human-review-style checked against the
range before commit.

## 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
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [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>
2026-09-15 11:31:44 -07:00
..
…
…
…
2026-03-12 11:05:31 -05:00
2026-04-04 07:44:23 -05:00