chore: release main#1718
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ed08c56119
ℹ️ 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".
| [project] | ||
| name = "modelaudit" | ||
| version = "0.2.49" | ||
| version = "0.2.50" |
There was a problem hiding this comment.
This release bump updates pyproject.toml to 0.2.50, but the committed lock file still has the root modelaudit package block at version = "0.2.49" in uv.lock. On this release/dependency path, the CI lock-consistency job runs uv lock --check, and any --locked install/metadata consumer will see the previous package version from the lock, so the release commit should include the uv lock update alongside this version change.
Useful? React with 👍 / 👎.
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
47e8ff5 to
22cb168
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6e62834a72
ℹ️ 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 = "modelaudit-picklescan-rust" | ||
| version = "0.1.8" # x-release-please-version | ||
| version = "0.1.9" # x-release-please-version |
There was a problem hiding this comment.
This release bump changes the Rust crate to 0.1.9, but packages/modelaudit-picklescan/Cargo.lock still records modelaudit-picklescan-rust as 0.1.7. On a clean checkout, Cargo treats that as a lockfile update; cargo check --help documents --locked as asserting the lock file remains unchanged, and the picklescan MSRV check in .github/workflows/test.yml:1003-1006 uses --locked. Please regenerate Cargo.lock with the version bump so locked builds and the committed release metadata agree.
Useful? React with 👍 / 👎.
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
a564f7d to
d8cc3b4
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
5948cb6 to
b241fe2
Compare
1 participant
🤖 I have created a release beep boop
0.2.50
0.2.50 (2026-07-02)
Bug Fixes
modelaudit-picklescan: 0.1.9
0.1.9 (2026-07-02)
Bug Fixes
This PR was generated with Release Please. See documentation.