Skip to content

[Chore] Cut framework release v2.3.0 (dev → main) #508

@atlas-apex

Description

@atlas-apex

Driver

18 commits have landed on dev since v2.2.0 (non-breaking; 6 feats → MINOR). Cut v2.3.0 to ship them to main + adopters.

Scope

  • Add the ## [2.3.0] CHANGELOG entry (premium-scrubbed — no MCP / apexyard-search / premium-component references).
  • Bump site/index.html version strings 2.2.0 → 2.3.0 (softwareVersion, dateModified, hero pill, version link + href, releases range/count).
  • Open the release/v2.3.0 → main PR (multi-close), Rex + CEO, merge, tag v2.3.0, then mandatory /release-sync.

Acceptance Criteria

  • CHANGELOG has the v2.3.0 entry; test_site_counts.sh version guard passes (site == CHANGELOG top)
  • Non-breaking; no premium-feature references in CHANGELOG / site / release notes
  • Tag v2.3.0 on main; sync-back PR filed

Glossary

Term Definition
release-cut The dev → main squash-merge + tag flow (AgDR-0007) that ships a framework version.
release-sync The mandatory main → dev sync-back after a release that keeps the squash commit an ancestor of dev.

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreMaintenance / non-feature work

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions