Skip to content

chore(release): align stable metadata to 1.2.1#62

Merged
aron23 merged 4 commits intostagingfrom
fix/m0-version-consistency-1-2-1
Jan 29, 2026
Merged

chore(release): align stable metadata to 1.2.1#62
aron23 merged 4 commits intostagingfrom
fix/m0-version-consistency-1-2-1

Conversation

@aron23
Copy link
Copy Markdown
Contributor

@aron23 aron23 commented Jan 29, 2026

Summary

  • Align stable-channel .release-please-manifest.json to the existing v1.2.1 tag.
  • Add the missing 1.2.1 section to CHANGELOG.md so 'latest stable' is unambiguous.

Test plan

  • go test ./...
  • GITHUB_REF_NAME=premain bash ./scripts/verify-branch-version-sync.sh

Sync stable manifest + changelog with the existing v1.2.1 tag so downstream repos can reliably pin to the latest stable release.
paytheory
paytheory previously approved these changes Jan 29, 2026
Resolves npm-audit vulnerability (GHSA-p5wg-g6qr-c7cg) by upgrading ESLint and moving to an ESLint v9-compatible flat config.
Compute and pass a release-as value on main so stable release PRs promote the current premain RC baseline (e.g., 1.3.0-rc.1 -> 1.3.0). Extend branch-release verifiers and docs to match the staging -> premain -> main supply chain.
Remove repo-root AI/agent helper docs that are not part of the library and ignore local .pai artifacts.
@aron23 aron23 merged commit 8036a6c into staging Jan 29, 2026
8 checks passed
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