chore: merge production v1.1.0 into staging#714
Merged
Conversation
…nches--production--components--OcotilloAPI chore(production): release 1.1.0
Contributor
There was a problem hiding this comment.
Pull request overview
Back-merges the v1.1.0 production release state into staging, aligning staging with the new stable baseline for subsequent staging work and RCs.
Changes:
- Bumps the Python package version in
pyproject.tomlto1.1.0. - Adds the
v1.1.0release notes toCHANGELOG.md. - Updates
.release-please-manifest.jsonto1.1.0.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
pyproject.toml |
Updates project version to the released stable 1.1.0. |
CHANGELOG.md |
Introduces the 1.1.0 changelog content brought in from production. |
.release-please-manifest.json |
Advances the stable release-please manifest version to 1.1.0. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c0ae4d73c0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
release-please bumps pyproject.toml but not uv.lock; tests run uv sync --locked which asserts the lockfile is unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated back-merge after release
v1.1.0.staging..release-please-manifest.staging.jsonto1.1.0so 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.