mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-21 00:05:49 +02:00
Devin Foleyandgithub-actions[bot]
b5fd13e09f
## 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's GitHub Release body comes from `releases/beta/v<beta-version>.md` on `master` > - The `draft_stable_notes` job seeded this file as a raw commit-log skeleton when `2026.828.0-beta.0` published > - The stable preflight fails without the merged file, and the skeleton is not fit to publish as release notes > - This pull request rewrites the skeleton into finished stable notes for the v2026.831.0 promotion > - The benefit is that the stable release ships with accurate, readable, user-facing notes on time ## Linked Issues or Issue Description **Issue type** Missing content **Where is the issue?** `releases/beta/v2026.828.0-beta.0.md` — the drafted stable-notes skeleton for the `2026.828.0-beta.0` soak. **What's wrong?** The file holds the auto-generated skeleton (grouped commit subjects with nested PR summaries). The stable promotion publishes this file verbatim as the GitHub Release body, so it must be rewritten into release-notes voice before the stable dispatch. **Suggested fix** Rewrite the skeleton at full stable depth per `.agents/skills/release-changelog/SKILL.md`: verified breaking changes with upgrade paths, delta-aware highlights, grouped improvements and fixes with inline PR attribution, an upgrade guide covering migrations and new environment variables, and a contributors section. ## What Changed - Rewrote `releases/beta/v2026.828.0-beta.0.md` from the generated skeleton into finished notes titled `# Paperclip v2026.831.0` - Six breaking changes, led by the Node.js 24.11.0 minimum; each has an upgrade path - Five highlights: runtime skill delivery to agents, the Kimi Code adapter, operator settings-visibility controls, the HTTP/2 sandbox callback bridge, and the shortened onboarding arc - Upgrade guide covers migrations `0223`–`0230` (each attributed from its SQL) and the new `PAPERCLIP_HIDDEN_SETTINGS`, `PAPERCLIP_SETTING_DEFAULTS`, `SENTRY_DSN`, and `PAPERCLIP_WORKSPACE_REAPER_COOLDOWN_DAYS` variables - Entries already shipped to stable users in v2026.824.1 are noted as such instead of re-announced - Contributors section lists 7 verified community handles; core maintainers and bots are excluded per the canonical list ## Verification - Range verified as `664052f8e..dbf052577` (baseline v2026.824.1 merge-base to the `beta/v2026.828.0-beta.0` source commit); every entry traces to a commit in that range - Stable version confirmed with `./scripts/release.sh stable --date 2026-08-31 --print-version` → `2026.831.0` - Migration list confirmed with `git diff --name-only 664052f8e..dbf052577 -- packages/db/src/migrations/` and each file's SQL read at the source commit - Environment variable names confirmed against `docs/deploy/environment-variables.md` and source at `dbf052577` - Contributor handles confirmed via `gh pr view <n> --json author` for each attributed community PR ## Risks - Low risk: a single markdown file; no source changes. The main risk is a factual error in the notes — mitigated by verifying each claim against the source commit rather than commit messages alone. If the promotion date slips past 2026-08-31 UTC, the title needs a re-date (the beta-keyed filename makes this harmless). ## Model Used - Claude (Anthropic), model ID `claude-fable-5` (Claude Fable 5), extended thinking enabled, tool use (git/GitHub CLI research against the release range) 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 --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>