Skip to content

chore(release): promote staging to premain (rc cut)#65

Closed
aron23 wants to merge 11 commits intopremainfrom
staging
Closed

chore(release): promote staging to premain (rc cut)#65
aron23 wants to merge 11 commits intopremainfrom
staging

Conversation

@aron23
Copy link
Copy Markdown
Contributor

@aron23 aron23 commented Jan 29, 2026

Summary

  • Promote latest staging into premain so the prerelease pipeline can cut the next RC.
  • Brings in M0 stable-metadata alignment + release-flow alignment (so premain -> main promotes the premain RC baseline).

What to do after merge

  • Merge the release-please prerelease PR that will be opened on premain (typically chore(premain): release ...).
  • That merge triggers the Prerelease (premain) workflow to publish the RC tag + assets.

Test plan

  • CI on this PR

paytheory and others added 11 commits January 22, 2026 21:40
Sync stable manifest + changelog with the existing v1.2.1 tag so downstream repos can reliably pin to the latest stable release.
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.
…-2-1

chore(release): align stable metadata to 1.2.1
Back-merge premain into staging to keep version lines and changelog aligned, so staging can promote cleanly to premain (RC) and then to main (release).
@paytheory paytheory closed this Jan 29, 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