Skip to content

chore: merge production v1.2.0 into staging - #792

Merged
chasetmartin merged 8 commits into
stagingfrom
merge/production-into-staging-1.2.0
Jul 22, 2026
Merged

chore: merge production v1.2.0 into staging#792
chasetmartin merged 8 commits into
stagingfrom
merge/production-into-staging-1.2.0

Conversation

@jirhiker

Copy link
Copy Markdown
Member

Automated back-merge after release v1.2.0.

  • Brings the release commit and tag history into staging.
  • Syncs .release-please-manifest.staging.json to 1.2.0 so the next staging RC versions from the new stable baseline.

If version files conflict with in-flight staging work, accept either side — release-please rewrites them on the next Release PR.

jirhiker and others added 8 commits July 20, 2026 14:31
The back-merge kept the stale root package version (1.1.0) in uv.lock while
pyproject.toml is 1.1.5, so `uv sync --locked` failed in CI. Regenerated.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…fix-v1.1.5-to-production

chore: back-merge hotfix/v1.1.5 into production
chore(release): promote staging to production for v1.2._
…nches--production--components--OcotilloAPI

chore(production): release 1.2.0
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@chasetmartin
chasetmartin merged commit 42f03b2 into staging Jul 22, 2026
9 checks passed
@chasetmartin
chasetmartin deleted the merge/production-into-staging-1.2.0 branch July 22, 2026 20:40
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