chore(main): release jacobian 0.12.0 - #1186
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: f62f200f5b
ℹ️ 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".
2bc3dac to
3e1f1db
Compare
morluto
left a comment
morluto
left a comment
There was a problem hiding this comment.
Post-cutover architecture audit
Disposition: close and regenerate; do not rebase this generated release PR.
This release candidate describes the pre-cutover 0.11.1 tree, including a managed-Skill fix for a surface deleted by #1252. #1252 and #1256 are breaking, net-deleting architecture changes and require a fresh version/changelog/lockfile snapshot from current main.
Because this is Release Please output, manual conflict resolution would also leave generated state with the wrong historical boundary. Close it and let the release workflow create a new post-cutover candidate after the retained PRs are settled.
github-actions
Bot
changed the title
0fac2b4 to
6cd9bff
Compare
|
Post-#1265 review: update/regenerate; do not treat this generated release PR as architecturally current yet. The release state was assembled before the latest tool/runtime simplifications completed. In particular, #1265 split local Recommendation: let release-please regenerate/rebase this PR from the final intended mainline rather than manually resolving generated changelog/lockfile conflicts. Then rerun the packaging/wheel/install/deployment checks, with special attention to both MCP entry points and the updated base Python backend set. Merge this last in the sequence, after the product PRs you actually want in the release are settled. |
2228ced to
8943e5e
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 201398f590
ℹ️ 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".
Release PR is current; workflow approval is the only blockerRelease Please has refreshed this branch through the latest merged fixes, including #934, #1244, #1247, #1203, and #1198. The PR is mergeable and remains the authoritative synchronized version/changelog update. Its associated CI, Benchmarks, and Container workflows report Disposition: retain; operational approval required before release landing. |
201398f to
90866c4
Compare
Release holdKeep this release PR open but do not merge it yet. Release Please has correctly regenerated it through current |
784cb82 to
47c500a
Compare
3b61210 to
023585b
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1fcf9a52a8
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4c0123d703
ℹ️ 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".
| * tighten domain diagnostics and Gaussian inputs ([6c269fe](https://github.com/morluto/jacobian/commit/6c269fee7c2550d07ac5ae7bab5122dac55e58d9)) | ||
|
|
||
|
|
||
| ### Bug Fixes |
There was a problem hiding this comment.
Fresh evidence beyond the earlier omitted-feature report is that this target now also adds _validate_strict_json_model and routes both request and result validation through it in capability_adapters.py and capability_dispatch.py, but the 0.12.0 Bug Fixes section has no corresponding entry. Tagging this tree will therefore publish the tuple-shaped JSON validation change without documenting it; regenerate the notes after including that fix.
Useful? React with 👍 / 👎.
|
🤖 Created releases: 🌻 |
1 participant
🤖 I have created a release beep boop
0.12.0 (2026-08-13)
Features
Bug Fixes
Performance Improvements
Dependencies
Documentation
This PR was generated with Release Please. See documentation.