release: bump Codex Security to 0.1.17

[mldangelo-oai]

Summary

Prepare the @openai/codex-security patch release 0.1.17.

This release includes the 39 commits merged since npm-v0.1.16, led by custom validation workflows and SDK finding validation, plus reliability and portability fixes across Windows, the workbench, plugin startup, scan reporting, runtime recovery, and session cost attribution.

Changes

• Bump @openai/codex-security from 0.1.16 to 0.1.17.
• Add custom validation workflow support, including SDK and CLI integration and runnable examples.
• Add SDK finding validation with documented typed inputs and results.
• Improve Windows and path handling for worktrees, portable paths, multiscan history and publication paths, stdin and UTF-8 process boundaries, tar listings, hard-link fallback, and disappearing ACL entries.
• Improve plugin and scan reliability through managed Node MCP startup, optional security app access, preserved root-cause references, scan instruction persistence before Deep workers start, credential-home lock recovery, and clearer failure and status reporting.
• Align scan session and cost attribution, harden authentication and runtime recovery, and use SemVer precedence for update notices.
• Keep the release-specific pull request diff limited to the package version field; the release contents come from current main.

Testing

Validated locally at exact head f0e3ecc138:

• git diff --check origin/main...HEAD
• Release automation contract: stable 0.1.17, matching npm-v0.1.17, greater than 0.1.16 and all published npm versions, publish mode
• Focused SDK API and release automation suites: 319 passed, 2 Windows-only skips, 0 failed
• Full randomized Bun suite: 1,595 passed, 28 platform/opt-in skips, 0 failed (seed 198997079)
• pnpm run types
• pnpm run format
• Release build, pack, archive validation, and installed-consumer smoke for public import, NodeNext types, CLI, bundled plugin and Codex, and nested-worker startup

Fresh GitHub checks and an automatic Codex code review are running for the new exact head. Recheck their results before merge.

Risk and rollout

At the time of this update, main and npm latest still declare 0.1.16, and no npm-v0.1.17 tag exists. The release branch includes exact current main; merging applies only the version bump to those release contents. Recheck the release delta, required checks, mergeability, and approvals immediately before merge.

After merge, the normal release workflow cuts the matching tag at the successful merged CI commit and requests approval through the protected npm environment. This pull request does not publish a package on its own.

Public disclosure review

Reviewed the public pull request material, release tarball, and available CI logs. No screenshots or attachments are present.

• No customer, partner, prospect, or user identities, data, or identifying details are included.
• No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
• I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-22T15:01:39.851424Z	f0e3ecc	New commits
🔒 Security Review	✅ Completed 2026-08-20T12:20:44.421050Z	9e6700a	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[mldangelo-oai]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: 9e6700a4b3

ℹ️ 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".