Skip to content

chore: sync staging with main (post-release)#74

Merged
paytheory merged 8 commits intostagingfrom
chore/sync-staging-with-main
Feb 14, 2026
Merged

chore: sync staging with main (post-release)#74
paytheory merged 8 commits intostagingfrom
chore/sync-staging-with-main

Conversation

@aron23
Copy link
Copy Markdown
Contributor

@aron23 aron23 commented Feb 14, 2026

Why

origin/staging is behind origin/main by 7 commits (release-please + changelog/version artifacts). Per docs/development/planning/theorydb-branch-release-policy.md, we need a post-release back-merge from main -> staging to keep the next staging -> premain promotion clean.

This PR also includes small dependency/toolchain bumps required to keep the SEC-2 dependency scans passing (GO-2026-4337, CVE-2026-26007, npm audit advisories).

What

Back-merges the latest stable release artifacts from main into staging:

  • .release-please-manifest.json
  • .release-please-manifest.premain.json
  • CHANGELOG.md
  • ts/package.json, ts/package-lock.json
  • py/src/theorydb_py/version.json

Plus security scan fixes:

  • Go toolchain go1.25.7 (root + contract-tests/runners/go + example modules)
  • npm audit lockfile updates (ts/, contract-tests/runners/ts)
  • Python deps: cryptography>=46.0.5, pip>=26.0 + refreshed py/uv.lock

paytheory and others added 7 commits January 29, 2026 17:56
chore(release): promote staging to premain (rc)
…emain

chore(premain): release 1.3.0-rc.2
chore(release): promote premain to main
Promote the premain RC baseline (1.3.0-rc.2) to a stable 1.3.0 release version across Go/TS/Py version files.
@paytheory paytheory merged commit 7128083 into staging Feb 14, 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