Skip to content

chore(release): promote staging to premain (rc)#67

Merged
paytheory merged 13 commits intopremainfrom
staging
Jan 29, 2026
Merged

chore(release): promote staging to premain (rc)#67
paytheory merged 13 commits intopremainfrom
staging

Conversation

@aron23
Copy link
Copy Markdown
Contributor

@aron23 aron23 commented Jan 29, 2026

Summary

After merge

  • Merge the release-please prerelease PR opened on premain (e.g. chore(premain): release ...) to publish the RC tag + assets.

Test plan

  • CI on this PR (rubric + unit + ts + py)

paytheory and others added 13 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).
Staging is promoted into premain to cut RCs. Keep TS/Py package versions aligned to the premain prerelease manifest so promotion PRs don’t fail version-alignment checks.
…ment

fix(release): keep staging aligned with premain RC line
@paytheory paytheory merged commit fc629fc into premain Jan 29, 2026
15 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