chore(#491): bump marketing-site framework version to 2.2.0#492
Conversation
- JSON-LD softwareVersion 1.3.0 → 2.2.0; dateModified → 2026-05-29 (v2.2.0 release date) - Hero pill apexyard v1.1 → v2.2; hero version link v1.1.0 → v2.2.0 (release-tag href + text) - Releases metric 7 → 12, range (v0.1 → v1.3) → (v0.1 → v2.2) — 12 releases per CHANGELOG - Historical version strings (CHANGELOG entry, migration scripts, AgDRs) left untouched Closes #491 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
atlas-apex
left a comment
There was a problem hiding this comment.
Code Review: PR #492
Commit: 2fe1ac0795b7cad0af59a3b69048107e0263e6cb
Summary
Content-only bump of the public marketing site (site/index.html) framework version from stale 1.3.0/v1.1 to current 2.2.0. Five version-string locations updated across 6 hunks; no logic, markup, or other files touched. Closes #491.
Checklist Results
- ✅ Architecture & Design: N/A (content change, no code)
- ✅ Code Quality: Pass
- ✅ Testing: Pass (site-counts test green)
- ✅ Security: Pass (no secrets, no auth surface)
- ✅ Performance: Pass (payload-size meta within 5% after 7→12)
- ✅ PR Description & Glossary: Pass
- ✅ Summary Bullet Narrative: Pass (narrative + rationale per bullet)
- ✅ Technical Decisions (AgDR):N/A (content bump, not a technical decision)
- ✅ Adopter Handbooks: N/A (no handbooks triggered by
.htmlcontent diff)
Verification performed
-
Only intended changes — diff is exactly the five expected edits and nothing else:
- JSON-LD
softwareVersion1.3.0 → 2.2.0 - JSON-LD
dateModified2026-05-24 → 2026-05-29 - Hero pill
apexyard v1.1 → v2.2 - Hero version link text +
releases/tag/hrefv1.1.0 → v2.2.0 - Releases metric
7 → 12and range(v0.1 → v1.3) → (v0.1 → v2.2)
gh pr diff --name-only→site/index.htmlonly. No layout/markup damage; no stale1.3.0/v1.1strings left behind. - JSON-LD
-
2.2.0 is current — CHANGELOG top entry is
## [2.2.0] — 2026-05-29;v2.2.0tag exists onme2resh/apexyard(local +refs/tags/v2.2.0remote).dateModifiedmatches the 2.2.0 release date — structured data is internally coherent. -
Release count 12 correct —
grep -cE '^## \[[0-9]' CHANGELOG.md→ 12 (0.1.0 … 2.2.0). -
Hero link target resolves —
releases/tag/v2.2.0tag confirmed present; link-check safe. -
Historical strings untouched —
## [1.3.0]CHANGELOG entry (line 163),.claude/migrations/v1.2.0-to-v1.3.0.sh, and AgDR examples all intact and outside the diff. Correct history preserved. -
CI safety —
test_site_counts.sh→ PASS; per-page payload-size meta stays within 5% after the +1 char (7→12). -
PR body — narrative Summary, Testing section, Glossary,
Closes #491all present.
Issues Found
None.
Suggestions
- The PR's own follow-up note is the right call: making
/releasetouch the site version strings would stop this ~5-cycle drift from recurring. Out of scope here.
Verdict
APPROVED
🤖 Reviewed by Rex (Code Reviewer Agent)
📌 Reviewed commit: 2fe1ac0795b7cad0af59a3b69048107e0263e6cb
- JSON-LD softwareVersion 1.3.0 → 2.2.0; dateModified → 2026-05-29 (v2.2.0 release date) - Hero pill apexyard v1.1 → v2.2; hero version link v1.1.0 → v2.2.0 (release-tag href + text) - Releases metric 7 → 12, range (v0.1 → v1.3) → (v0.1 → v2.2) — 12 releases per CHANGELOG - Historical version strings (CHANGELOG entry, migration scripts, AgDRs) left untouched Closes #491 Co-authored-by: me2resh <ahmed.abdelaliem@gmail.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Summary
site/index.html, served at yard.apexscript.com). The CEO spotted the JSON-LD advertising1.3.0while the framework is at2.2.0; the hero also still readapexyard v1.1/ linked thev1.1.0release. The labels had drifted ~5 release cycles because/releasedoesn't bump the site.softwareVersion1.3.0 → 2.2.0;dateModified2026-05-24 → 2026-05-29(the v2.2.0 release date) so the structured data is internally coherent.apexyard v1.1 → v2.2; version link text +releases/tag/hrefv1.1.0 → v2.2.0(tag verified to exist).7 → 12and range(v0.1 → v1.3) → (v0.1 → v2.2); 12 matches the CHANGELOG release-entry count (0.1.0 … 2.2.0).## [1.3.0]CHANGELOG entry,v1.2.0-to-v1.3.0.shmigration-script names, and AgDR examples are correct history, not drift.Follow-up (out of scope): make
/releaseupdate the site version strings so this can't drift again — noted on the ticket.Testing
bash .claude/hooks/tests/test_site_counts.sh→ PASS (skills/hooks/roles counts unchanged; per-page payload-size meta within 5%).gh release view v2.2.0confirms the hero link target resolves (link-check safe).Glossary
softwareVersionCloses #491