release: bump Codex Security to 0.1.8 - #315
Merged
Merged
Conversation
ianw-oai
approved these changes
Aug 7, 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
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
@openai/codex-securityfrom0.1.7to0.1.8with a one-line change on the latestmain.npm-v0.1.7while keeping the frozen dependency lockfile and protected release workflows unchanged.Validation
mainand npmlatestare both0.1.7.npm-v0.1.8tag.Release
After review and merge, the existing
node-release-cutworkflow observes the higher version onmain, createsnpm-v0.1.8on the exact merged commit, and dispatches the protected, provenance-enablednode-releaseworkflow.Opening or merging this PR does not itself publish the package; publication still requires the protected
npmdeployment approval.