Skip to content

docs(release): record v2.2.0 in the release timeline #8130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
loopx-agent merged 1 commit into from
Nov 5, 2026
Merged

docs(release): record v2.2.0 in the release timeline #8130

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/product/release-readiness.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -975,6 +975,16 @@ path, and canary route rather than as a user-facing release baseline.
snapshots. Read the [versioned upgrade guide](https://github.com/loopx-project/loopx/blob/v2.1.1/docs/product/releases/v2.1.1.md)
before replacing an existing installation.

- `v2.2.0` release at commit
`2c3524857e8a3dd553335b79444333786f492c43`:
the [published release](https://github.com/loopx-project/loopx/releases/tag/v2.2.0)
(2026-11-01) and the public `stable` ref point at the same commit. The
[versioned release note](https://github.com/loopx-project/loopx/blob/v2.2.0/docs/product/releases/v2.2.0.md)
records the canonical-authority upgrade boundary, the context-delivery
default and the readback path. Read it before replacing an existing
installation; artifact and native-host claims remain those stated by that
release note.

When a new public release is promoted, add it here only after the matching tag,
release note, stable ref, update path, and focused release canary agree.

Expand Down
Loading