* ci(release): share npm setup and verification
Use the same local composite action after checkout in both release jobs. Keep the Node and registry settings, Socket Firewall installation and next-step PATH verification in one place. Each job retains its own checkout, credentials and publication controls. Existing tags continue to use the workflow in their release commit. No public interface migration is required.
Both release suites pass (318 tests), including 312 tests with the separate bootstrap and release-history changes applied. Five mocked setup runs checked success and failures during installation, version validation and executable selection. Compared workflow selection for npm-v0.8.2 and npm-v0.8.3 and linted both workflows. These checks did not dispatch a release or publish a package.
* ci(release): scope the workflow lint exception to the verified npm path
Moving the shared setup into a composite action brings its existing PATH write under the github-env audit. Both release jobs install the pinned npm from the firewall, verify the executable in a fixed directory under RUNNER_TEMP and recheck it on PATH in the next step. Explain that input on the installation step.
Reproduced the initial diagnostic with zizmor 1.30.1. Its repository-wide workflow check now passes, and it still reports an unchecked PATH write added to a neighboring fixture step. Both release automation and release PR suites pass (429 tests).
The public package has already shipped 0.1.0 and npm permanently reserves
that name and version. Remove the first-publish token step and the local
adapter that treated an E404 as an empty release history. Both workflows
stop on lookup failure. Normal publication still uses trusted publishing.
Historical GitHub release verification keeps its original recovery path.
Across 22 synthetic release-cut and publisher comparisons, only the two
initial-404 cases changed. The candidate passed 407 release, Action, and
container tests. The historical 0.1.0 npm and GitHub archives matched
byte for byte. The pinned npm signature audit and both revisions'
provenance and publication checks accepted the same archive and run.
No package user or downstream release command needs to change.
* ci(deps): update Bun to 1.4.4
* test(ci): align the Bun workflow version assertion
* chore(deps): align remaining Bun toolchain pins
* fix(ci): preserve test timeouts with Bun 1.4 options
---------
Co-authored-by: Michael D'Angelo <mdangelo@openai.com>
Run release test shards and MCP verification in parallel, then gate publication on every verification result. Maintain a release PR progress comment across CI, approvals, and publication, including recovery through follow-up fix commits.
Give parameterized tests unique JUnit names so baseline, parallel, and sharded inventories can be compared.
## Summary
Update actions/download-artifact from 8.0.1 to 8.0.2 so CI and release downloads use the updated artifact client.
## Changes
- Replace existing download-artifact pins with the verified v8.0.2 commit and matching version comments.
- Preserve artifact names, IDs, patterns, merge settings, and extraction paths.
## Testing
- Reviewed the complete workflow diff, upstream source changes, and official tag-to-commit match.
- Native and packaged-artifact consumers passed CI.
- Reran the Windows test shard after it reached application tests and timed out. Required checks must pass before merge.
- The optional runner-inventory comparison fails on a duplicate JUnit test identity already present on main.
## Risk and rollout
Patch update within the existing action major version. Artifact selection and extraction behavior remain unchanged. No rollout steps are required.
## Public disclosure review
- [x] No customer, partner, prospect, or user identities, data, or identifying details are included.
- [x] No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
- [x] I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.
## Summary
Update actions/setup-node from 7.0.0 to 7.1.0 for CI and release Node setup.
## Changes
- Replace existing setup-node pins with the verified v7.1.0 commit and matching version comments.
- Preserve explicit Node versions and existing cache, architecture, and authentication inputs.
## Testing
- Reviewed the complete workflow diff, upstream source changes, and official tag-to-commit match.
- Required Linux, macOS, Windows, and PR-title checks passed. Native and installed-package CI passed across supported platforms and Node versions.
- Reran an optional Windows isolated-test timeout. The optional runner-inventory comparison also has a pre-existing duplicate JUnit test identity on main.
## Risk and rollout
Minor update within the existing action major version. Current callers continue to specify explicit Node versions; new version-file support does not alter those callers. No rollout steps are required.
## Public disclosure review
- [x] No customer, partner, prospect, or user identities, data, or identifying details are included.
- [x] No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
- [x] I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.
## Summary
Update actions/upload-artifact from 7.0.1 to 7.0.2 so CI and release uploads use the updated artifact client.
## Changes
- Replace all existing upload-artifact pins with the verified v7.0.2 commit and matching version comment.
- Preserve workflow inputs, artifact names, permissions, and release behavior.
## Testing
- Reviewed the complete workflow diff, upstream release, and tag-to-commit match.
- GitHub CI passed all required Linux, macOS, Windows, and PR-title checks, plus native builds, package checks, and artifact uploads.
- The optional runner-inventory comparison fails on a duplicate JUnit test identity already present on main; this dependency update does not change that test.
## Risk and rollout
Patch update within the existing action major version. Existing CI exercises artifact uploads and downstream consumption. No rollout steps are required.
## Public disclosure review
- [x] No customer, partner, prospect, or user identities, data, or identifying details are included.
- [x] No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
- [x] I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.
* ci: require workflow checks and production dependency audits
* test: select CI coverage gates by name
---------
Co-authored-by: mldangelo-oai <269034524+mldangelo-oai@users.noreply.github.com>
Update 23 actions/setup-node pins from 6.3.0 to 7.0.0 and correct their version comments. Preserve requested Node versions, architectures, registry URLs, cache settings, and publishing authentication.
Validated exact upstream compatibility, workflow YAML, patch scope, and integration with main. Current-head CI passed all 57 executed jobs, including the full Windows suites and inventory comparison. The shared Windows deadline fix is already present on main.
Update 27 actions/checkout pins from 6.0.2 to 7.0.1. Preserve workflow refs, inputs, and disabled credential persistence.
Allow Windows baseline and isolated test-quality suites 45 minutes after repeated 30-minute timeouts near completion. Other deadlines remain unchanged.
Validated exact upstream compatibility, workflow YAML, patch scope, and integration with main. Current-head CI passed all 57 executed jobs, including both full Windows suites and the inventory comparison.
* build(plugin): use pnpm for MCP app dependencies
* test: fix CI reports and Windows subprocess checks
---------
Co-authored-by: Michael D'Angelo <269034524+mldangelo-oai@users.noreply.github.com>
* fix: harden npm package lifecycle and Node support
* fix: make npm package lifecycle package-manager agnostic
* fix: test every supported minimum Node.js version
* fix: preserve required Node CI status checks
* ci: switch Codex Security workflows to Node
* fix(ci): set runner temp at the test step
* feat: bootstrap TypeScript public projection
* fix(ci): stabilize Windows SDK tests
* test: trace Windows authentication timeout
* fix(test): finish Windows fake-login processes
* fix(test): use Node for Windows login doubles
* fix: observe fast Windows login exits and refresh plugin
* test: inherit the Windows login environment
* fix: complete interactive login on process exit
* fix: make the TypeScript SDK Windows suite portable
* test: narrow Windows root-path assertion
* fix: preserve LF text files on Windows
* fix: harden public artifact and login boundaries
* fix: harden public package and process boundaries
* fix: encode scoped scan paths in prompts
* test: keep scoped-path regression portable
* fix: harden public package boundaries
* fix: enforce exact public artifact contents
* fix: reject unsafe public archive entries
* fix: escape scoped-path line separators
* docs: make SDK quickstarts valid on Node 22
* fix: reject hidden tar payloads in package gate
* fix: align projected CLI launcher and package gate