chore(deps-dev): bump rich from 14.2.0 to 15.0.0 - #3717
Conversation
Castiron custom code✅ No new custom-code files detected. 34 mixed files remain; 0 existing customizations changed. Compared 34 existing customizations unchanged
A changed generated baseline means this report cannot reliably identify which handwritten lines changed. Inspect the custom-code diffDownload the exact patch produced by this run (requires repository access): gh run download 33028822924 --repo openai/openai-python \
--name castiron-custom-code-33028822924-1 --dir /tmp/castiron-custom-code-33028822924-1
git apply --stat /tmp/castiron-custom-code-33028822924-1/custom-code.patch
cat /tmp/castiron-custom-code-33028822924-1/custom-code.patchOr reproduce it from an SDK checkout containing the vendored reporter: git fetch --no-tags origin 79c588bb3a40fb698c65e35c94ad96c0b44c30d4 555054df93a2fedcd72c35462e21c4d84b294abc
python3 scripts/castiron/custom_code_report.py report \
--base 79c588bb3a40fb698c65e35c94ad96c0b44c30d4 \
--head 555054df93a2fedcd72c35462e21c4d84b294abc --fetch --require-head-hash --public \
--out /tmp/castiron-custom-code-555054df93a2
cat /tmp/castiron-custom-code-555054df93a2/custom-code.patchThis is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 51e89bb096
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| [[package]] | ||
| name = "openai" | ||
| version = "3.3.1" # x-release-please-version | ||
| version = "3.3.1" |
There was a problem hiding this comment.
Restore the release-please version marker
When the next release is prepared, Release Please uses uv.lock as an extra version file (release-please-config.json:61-64) and relies on the removed x-release-please-version annotation to locate the value; the preceding automated release commit 753ab5c demonstrates that this annotated line is what gets updated. Without the marker, the lockfile remains at the old project version or the release update fails, and the repository's uv sync --locked CI jobs will block the release PR once pyproject.toml advances.
Useful? React with 👍 / 👎.
51e89bb to
fe04302
Compare
Bumps [rich](https://github.com/Textualize/rich) from 14.2.0 to 15.0.0. - [Release notes](https://github.com/Textualize/rich/releases) - [Changelog](https://github.com/Textualize/rich/blob/main/CHANGELOG.md) - [Commits](Textualize/rich@v14.2.0...v15.0.0) --- updated-dependencies: - dependency-name: rich dependency-version: 15.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
fe04302 to
555054d
Compare
Bumps rich from 14.2.0 to 15.0.0.
Release notes
Sourced from rich's releases.
... (truncated)
Changelog
Sourced from rich's changelog.
... (truncated)
Commits
6ac483ccorrection458a910Merge pull request #4080 from Textualize/bump150082e06e0changelogd6556bcbump to 15.0.0ffe2edcMerge pull request #4079 from Textualize/inline-table-codecf3b5a1changelog77f0edbremove comments7ef2d05fix inline code in table cells19c67b9Merge pull request #4077 from Textualize/isattry494b795changelog