## Summary
The release notes template that CI prefills into every release draft,
the structure sketch of the same sections in RELEASING.md, and the quick
start's upgrade recipe still described the 0.1.13 finish line. Since
then both installers end by opening Raven in the browser, where
first-run setup now happens; `raven upgrade` installs the plugin wheels
too; rerunning the installer cannot pick up a pre-release, since it
resolves `releases/latest`; and a release ships three plugin wheels plus
`raven-constraints.txt` and `raven-plugins.txt` beside the wheel and
sdist. Both files now say so.
The Upgrade section of the template and the "Update a one-line install"
recipe in docs-site/docs/quick-start.md and quick-start.zh.md are
written to match the upgrade code: stop the page, run `raven upgrade`,
and start Raven again only after the upgrade has finished. On Linux and
macOS the command execs the helper in the foreground and returns when
the install is done; on native Windows it spawns the helper and returns
at once, and a `raven web` started before the completion message runs
into the install marker and exits 75. `raven upgrade` installs the
latest stable release unless the install has joined the beta channel, in
which case it installs that channel's pre-release.
Each claim was checked against the v0.2.0 tree: the launch sections of
install.sh and install.ps1, the `web` command and
`_refuse_incomplete_install` in raven/cli/serve_commands.py,
`_handoff_upgrade` and `fetch_latest_for_channel` in
raven/updates/upgrade.py, the first-run gate in ui-web/src/app/boot.ts,
and the asset list in .github/workflows/release.yml.
The 0.2.0 draft is edited in place; this change only reaches the drafts
CI creates from now on. The `__VERSION__` and `__TAG__` placeholders and
the two TODO markers the release job and the notes step rely on are
unchanged.
## Type
- [ ] Fix
- [ ] Feature
- [x] Docs
- [ ] CI / tooling
- [ ] Refactor
- [ ] Other
## Verification
- `git diff --stat origin/main..HEAD`:
.github/release-notes-template.md, RELEASING.md,
docs-site/docs/quick-start.md, docs-site/docs/quick-start.zh.md
- `npx commitlint --from origin/main --to HEAD --config
commitlint.config.cjs`: exit 0
- `PYTHONPATH=. python scripts/check_commit_messages.py
origin/main..HEAD`: exit 0
- `PYTHONPATH=. python scripts/check_source_language.py
origin/main..HEAD`: exit 0
- Non-ASCII scan of the template and RELEASING.md: nothing found (the zh
quick start page is Chinese by design)
- No tests run: markdown only; the one code consumer is the sed in
release.yml, whose placeholders are unchanged. The docs build runs in
CI.
- [ ] Relevant tests pass locally
- [x] Relevant lint / type checks pass locally
- [x] User-facing docs or screenshots are updated when needed
## Risk
Documentation only. Rollback is reverting the commits; the next tagged
release then prefills the old text again.
- [ ] Security impact considered
- [x] Backward compatibility considered
- [x] Rollback path is clear for risky changes
## Related Issues
N/A
---------
Co-authored-by: Claude (claude-fable-5-1) <noreply@anthropic.com>