Skip to content

[AAASM-3849] 📝 (docs): Sync version refs to rc.2 (matrix + labels + Node @rc)#47

Merged
Chisanan232 merged 4 commits into
mainfrom
v0.0.1/AAASM-3849/docs_rc2_version_sync
Jun 27, 2026
Merged

[AAASM-3849] 📝 (docs): Sync version refs to rc.2 (matrix + labels + Node @rc)#47
Chisanan232 merged 4 commits into
mainfrom
v0.0.1/AAASM-3849/docs_rc2_version_sync

Conversation

@Chisanan232

Copy link
Copy Markdown
Contributor

Description

Sync the documentation hub's version references to the current rc.2 release
line (PyPI 0.0.1rc2, npm @rc0.0.1-rc.2, go-sdk v0.0.1-rc.2). Three
related doc bugs were combined into one PR because they edit overlapping files
(compatibility.toml / docs/src/compatibility.md / docs/src/README.md):

  • AAASM-3849 — Regenerate the core↔SDK compatibility matrix. Added
    beta.3, beta.4, rc.1, rc.2 rows to compatibility.toml and marked
    rc.2 as current (removing the stale beta.2 "current" mislabel),
    regenerated compatibility.md, and refreshed the "Last verified" date.
  • AAASM-3850 — Relabeled product maturity from alpha/beta to
    release candidate: the source-of-truth.md maturity label + area map
    (v0.0.1-alphav0.0.1-rc) and the hub README.md prose
    ("in beta (v0.0.1-beta)" → "in release candidate (v0.0.1-rc)").
  • AAASM-3851 — Switched Node SDK references from the @beta to the @rc
    npm dist-tag (install one-liners, quickstart pnpm add, npm version badges,
    and dist-tag prose). Python --pre and Go @latest already track rc.2.

Type of Change

  • 🐛 Bug fix (correcting inaccurate or missing content)

Related Issues

  • Related Jira tickets: Closes AAASM-3849, Closes AAASM-3850, Closes AAASM-3851

Documentation Checklist

  • cd docs && mdbook build passes locally with no warnings
  • All internal cross-links verified
  • Page registered in docs/src/SUMMARY.md (no new pages added)
  • Self-hosted instructions not included (SaaS-only scope)
  • "Last reviewed" footer updated with today's date
  • Commits follow GitEmoji convention and are small / atomic
  • docs/scripts/generate_compatibility.py --check passes (page matches manifest)

🤖 Generated with Claude Code

Chisanan232 and others added 4 commits June 27, 2026 19:59
Add beta.3, beta.4, rc.1 and rc.2 rows to compatibility.toml and mark
rc.2 as the current product line (demoting the stale beta.2 "current"
label to supported). Regenerate docs/src/compatibility.md and refresh
the "Last verified" date.

Closes AAASM-3849

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019mSz31RysZF6DYToUoBWLf
The product line is now v0.0.1-rc, so the status map's maturity label and
every area row that read "alpha"/"v0.0.1-alpha" now read "release
candidate"/"v0.0.1-rc". Refresh the "Last reviewed" footer.

Closes AAASM-3850

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019mSz31RysZF6DYToUoBWLf
The hub landing page described the project as "in beta (v0.0.1-beta)";
the current line is the release candidate v0.0.1-rc. Refresh the
"Last reviewed" footer.

Closes AAASM-3850

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019mSz31RysZF6DYToUoBWLf
The release-candidate line publishes under npm's `rc` dist-tag
(@agent-assembly/sdk@rc resolves to 0.0.1-rc.2). Update the install
one-liner (manifest + regenerated requirements table), the quickstart
pnpm command, the npm version badges, and the dist-tag prose from @beta
to @rc. (Python --pre and Go @latest already track rc.2.)

Closes AAASM-3851

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019mSz31RysZF6DYToUoBWLf
@Chisanan232

Copy link
Copy Markdown
Contributor Author

🤖 Claude Code — PR Review

Verdict: ✅ APPROVE

Scope (AAASM-3849 / 3850 / 3851): Complete. Compatibility matrix regenerated through rc.2 with rc.2 marked current (stale beta.2 "current" demoted to supported); maturity labels updated alpha→release candidate across source-of-truth.md + README.md; Node SDK references switched @beta@rc (resolves 0.0.1-rc.2). Combined into one PR because the three tickets edit shared files.

No side-effects: Docs-only. mdbook build clean (no new warnings) and the compatibility generator --check passes (page in sync with the manifest).

Note for tracking: the matrix scope listed beta.3/beta.4/rc.1/rc.2 — a beta.5 dist-tag exists but no row was added (out of the tickets' stated scope); a follow-up row may be warranted if beta.5 was a coordinated published release.

CI: Green.

@Chisanan232 Chisanan232 marked this pull request as ready for review June 27, 2026 12:58
@Chisanan232 Chisanan232 merged commit 0551985 into main Jun 27, 2026
3 checks passed
@Chisanan232 Chisanan232 deleted the v0.0.1/AAASM-3849/docs_rc2_version_sync branch June 27, 2026 13:23
@sonarqubecloud

Copy link
Copy Markdown

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.

1 participant