Repository navigation
chore(release): 0.2.0 - #1086
Merged
Merged
Conversation
Contributor
Author
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview compatibility and document any required migration steps before releasing. |
|
Note To use Codex here, create a Codex account and connect to github. |
Contributor
Author
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview compatibility and document any required migration steps before releasing. |
|
Note To use Codex here, create a Codex account and connect to github. |
Contributor
Author
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview compatibility and document any required migration steps before releasing. |
|
Note To use Codex here, create a Codex account and connect to github. |
Contributor
Author
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview compatibility and document any required migration steps before releasing. |
|
Note To use Codex here, create a Codex account and connect to github. |
Contributor
Author
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview migration steps for these breaking changes:
|
|
Note To use Codex here, create a Codex account and connect to github. |
Contributor
Author
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview migration steps for these breaking changes:
|
|
Note To use Codex here, create a Codex account and connect to github. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Contributor
Author
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview migration steps for these breaking changes:
|
|
Note To use Codex here, create a Codex account and connect to github. |
Contributor
Author
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview migration steps for these breaking changes:
|
|
Note To use Codex here, create a Codex account and connect to github. |
mldangelo-oai
approved these changes
Oct 6, 2026
mldangelo-oai
left a comment
mldangelo-oai
left a comment
Collaborator
There was a problem hiding this comment.
Reviewed the release proposal and curated the highlights and upgrade notes against all 124 merged pull requests in this release cycle. The release-only diff is approved.
Release-note validation, formatting, edited-section preservation, and all 85 focused release automation checks passed. The production dependency audit reports zero vulnerabilities. Standard and Deep scan, saved-result/export, and installed-package smoke checks passed on the unchanged runtime base f230f76. Normal CI and protected publication gates still apply.
github-actions
Bot
added
the
skip-release-notes
mldangelo-oai
approved these changes
Oct 6, 2026
mldangelo-oai
left a comment
mldangelo-oai
left a comment
Collaborator
There was a problem hiding this comment.
Reviewed the revised release highlights and upgrade guidance against the merged changes. The notes use plain language and retain the compatibility steps readers need. Release-note parsing, Markdown formatting, edited-section preservation, and whitespace checks passed on this commit. This update changes only release-note prose; the prior runtime smoke results and 85 release-automation checks still apply. Required CI must finish before merging.
mldangelo-oai
approved these changes
Oct 6, 2026
mldangelo-oai
left a comment
mldangelo-oai
left a comment
Collaborator
There was a problem hiding this comment.
Reviewed the release updater changes. The two added changes update evaluation-tool dependencies only; the shipped CLI/SDK runtime and reviewed release notes are unchanged. The release metadata correctly preserves both edited note sections. Approval remains subject to passing CI on this commit.
mldangelo-oai
approved these changes
Oct 6, 2026
mldangelo-oai
left a comment
mldangelo-oai
left a comment
Collaborator
There was a problem hiding this comment.
Reviewed the newly included MCP dependency update: proxy-addr moves from 2.0.7 to 2.0.8 in the lockfile, with no source or public API changes. The release highlights and upgrade guidance remain accurate. The earlier release candidate passed CI; this updated commit must pass its own checks before merging.
stonersdash26
approved these changes
Oct 12, 2026
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
2 participants
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.
Summary
Prepare Codex Security 0.2.0 with six release highlights and upgrade guidance, based on a review of the changes merged since 0.1.32.
Changes
Testing
f230f7621d47cf38ca38e05cfb850f497889de42: live Standard and one-worker Deep scans, saved history, SARIF/CSV/threat-model export, and artifact integrity.Risk and rollout
The breaking threat-model API change requires a minor version bump under the pre-1.0 release policy. SDK integrations must handle document paths that can be null and both Markdown and structured models. Existing saved results need no migration. Custom findings-service clients must send a JSON content type. Diagnostic text can include sensitive values, so review output before sharing it.
Merging starts the existing protected release process. Required CI and release gates still apply. The smoke checks above cover Linux and the listed paths; they are not a full cross-platform regression run.
Public disclosure review