Skip to content

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

Closed
Weimr2627 wants to merge 2 commits into
loopx-project:mainfrom
Weimr2627:weimr/release-timeline-v220
Closed

Weimr2627 wants to merge 2 commits into
loopx-project:mainfrom
Weimr2627:weimr/release-timeline-v220

Conversation

@Weimr2627

Copy link
Copy Markdown
Contributor

Goal And Delivered Outcome

  • Outcome basis / optional anchor: the nightly Full Public Smokes repository-hygiene-smoke.py failure with release timeline is missing version entries: v2.2.0.
  • Goal/source and gap: v2.2.0 is tagged and the public stable ref points at the same commit, but the maintained release timeline stopped at v2.1.1. Before: the smoke rejects the timeline because the tag is absent from the document. After: the timeline records the release and the smoke passes.
  • Observable before → after, with the validation row that proves it: with a local v2.2.0 tag (the hosted checkout carries it), python3 examples/repository-hygiene-smoke.py fails on base and prints repository-hygiene-smoke ok on this head.
  • Issue/task and intended base: no issue; self-contained documentation repair. Intended base is loopx-project/loopx:main.

Author Declaration

  • Written by: model_agent — Qoder AI assistant, at the contributor's direction; no human review has occurred.

Implemented against

  • Specification and revision: examples/repository-hygiene-smoke.py at 4d8b79692d13ea17a43d2369d35282b023be311e, validate_release_timeline() at lines 346-360; the timeline admission rule at docs/product/release-readiness.md:988.
  • Criteria:
Criterion (spec clause) Disposition Symbol / path Test or command
Every version tag after the first public release appears in the timeline implemented docs/product/release-readiness.md python3 examples/repository-hygiene-smoke.py
The entry names the tag, the commit, the public release and the versioned note implemented same same
The timeline keeps its maintainer admission rule implemented line 988 same
  • Self-check before submission: verified the annotated tag dereferences to 2c3524857e8a3dd553335b79444333786f492c43, the public stable ref points at that commit, the GitHub release is published on 2026-11-01, and the versioned note exists at the tag. The entry states only those facts and defers artifact/native-host claims to the release note; it does not add a new qualification claim.

Scope And Continuation

  • Completed scope and remaining work: complete within this scope; the release history and product behavior are unchanged.
  • Slice boundary / successor: N/A — the timeline entry is the whole exit.

Validation

  • Tested revision: 8fa34b20057b042be4a5fdf8619f71cb9c8741c1
  • Run state: finished
  • Input classes: synthetic
Check kind Result Public-safe evidence / limitation
integration passed With a local v2.2.0 tag, python3 examples/repository-hygiene-smoke.py → repository-hygiene-smoke ok. The hosted nightly checkout carries the same tag.
regression_parity passed The same command on base 4d8b79692d13ea17a43d2369d35282b023be311e raises release timeline is missing version entries: v2.2.0.
static passed git diff --check; the hygiene smoke also runs the public/private boundary scan over the changed document.
unit not_run Documentation-only; no unit test covers the timeline prose.
  • Coverage and gaps: documentation-only. The nightly workflow is intentionally not a PR-required check, so this PR does not attach a hosted CI run. The local tag was created only to exercise the smoke and was deleted afterwards; no tag is pushed by this PR.

Frontend / Visual Evidence

  • UI impact: none
  • Before: N/A
  • After: N/A
  • First viewport and preview: N/A
  • States and viewports shown: N/A
  • Source data: none
  • Attention review: N/A
  • Craft review: N/A

Type of Change

  • Documentation update

LoopX Area

  • Build, packaging, installer, or CI

Technical Direction

  • Direction / acceptance reference, when applicable: N/A

Shared-authority RFC fixture impact

  • Production-scale fixture schema: N/A
  • Semantic dimensions changed, or reviewed no-impact rationale: N/A
  • Provider conformance arms run: N/A
  • Read-only legacy/file/PostgreSQL three-arm rehearsal (required for promotion, runtime-routing, or compatibility-projection changes): N/A

Boundary Checklist

  • Neither the diff nor this PR body/comments/attachments disclose private state, credentials, raw traces or verifier output, internal links, or local machine paths (including .loopx/, .codex/goals/, and live ACTIVE_GOAL_STATE.md).
  • I did not duplicate maintainer-owned benchmark work unless a maintainer split out a public issue for it.
  • I kept the change scoped to the linked issue/task.
  • Existing English/Chinese RFC pairs both have a diff, and the local premerge check passes, or no paired RFC changed (no RFC changed here).
  • I completed the visual evidence section for UI changes, or marked UI impact none.
  • Every commit includes a DCO Signed-off-by trailer (git commit -s).

Signed-off-by: Weimr2627 <134630546+Weimr2627@users.noreply.github.com>
@loopx-agent loopx-agent closed this Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants