chore: release main#1768
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ff897ed5a1
ℹ️ 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".
2bbed40 to
044dff2
Compare
Performance BenchmarksCompared
|
eff3955 to
8edf9b8
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 05fcb12250
ℹ️ 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.51" | ||
| version = "0.2.52" |
There was a problem hiding this comment.
Require picklescan 0.1.10 for this release
When users upgrade modelaudit to 0.2.52 in an environment that already has modelaudit-picklescan==0.1.9, the unchanged dependency floor at pyproject.toml:55 still satisfies the new root wheel; pip install --help confirms the default upgrade strategy is only-if-needed, so dependencies are upgraded only when they no longer satisfy requirements. That leaves those upgraded root installs without the picklescan fix advertised in this release, so the coordinated root release should raise the floor to modelaudit-picklescan>=0.1.10,<0.2.0.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Confirmed: the refreshed release branch bumps picklescan to 0.1.10 but the root requirement remains >=0.1.9,<0.2.0, so only-if-needed upgrades can retain 0.1.9. I am leaving this thread unresolved and will raise the floor/regenerate the root lock on the final refreshed release branch after the pending security/cache merges; updating the current generated branch now would be overwritten by the next release-please refresh.
53db33b to
22db7d5
Compare
2f3710a to
715458e
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 26f38fb3d3
ℹ️ 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".
| "protobuf>=5.29.0", | ||
| "msgpack>=1.2.1,<2.0", | ||
| "modelaudit-picklescan>=0.1.9,<0.2.0", | ||
| "modelaudit-picklescan>=0.1.10,<0.2.0", |
There was a problem hiding this comment.
Update every mirror of the picklescan floor
With this requirement raised to 0.1.10, tests/test_dependency_lock.py:17 still defines REQUIRED_PICKLESCAN_RELEASE as the exact 0.1.9 requirement and line 85 asserts that old string is present, so the mandatory pytest suite deterministically fails. The canonical root and picklescan agent guides and docs/agents/release-process.md:14 also still publish the old floor; update these mirrors with the dependency bump.
AGENTS.md reference: AGENTS.md:L14-L21
Useful? React with 👍 / 👎.
| - avoid logging file-derived header-format values while preserving format-mismatch detections, and clean up CodeQL quality findings | ||
| - inspect LZ4-compressed Joblib payloads with bounded decompression and preserve fail-closed optional dependency handling; thanks to @PowerliftLog for the report | ||
|
|
||
| ## [0.2.52](https://github.com/promptfoo/modelaudit/compare/v0.2.51...v0.2.52) (2026-07-22) |
There was a problem hiding this comment.
Clear released fixes from Unreleased
When this section declares 0.2.52 released, the fixes at lines 12–15 remain under ## [Unreleased]; the sibling changelog likewise leaves its 0.1.10 fix under Unreleased at lines 14–18. The root [unreleased] reference at line 2555 also still compares from v0.2.51, so the published changelogs describe already-shipped fixes as pending and link to a range containing this release; clear the promoted entries and advance the comparison reference.
AGENTS.md reference: AGENTS.md:L82-L82
Useful? React with 👍 / 👎.
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
0.2.52
0.2.52 (2026-07-22)
Bug Fixes
modelaudit-picklescan: 0.1.10
0.1.10 (2026-07-22)
Bug Fixes
This PR was generated with Release Please. See documentation.