Files
codex/.github
Dmitriy Kovalenko 2f1e4f99e0 Require Bazel release artifacts and publish DotSlash manifests (#58196)
## Why

Desktop consumers require successful Cargo and Bazel release artifacts, so Bazel release jobs must no longer be advisory.

## What changed

- Remove Bazel-specific `continue-on-error` settings from release build, signing, packaging, symbol, and macOS verification jobs.
- Add `codex-bazel`, `codex-command-runner-bazel`, and `codex-windows-sandbox-setup-bazel` DotSlash outputs for the corresponding Bazel release assets.
- Extend provisioned macOS signing and verification to both Cargo and Bazel packages on both architectures, keeping Bazel artifacts and reports distinct with a `-bazel` suffix.
- Add a `codex-provisioned-bazel` DotSlash output for provisioned macOS packages.

## Testing

Run the existing provisioned package smoke tests, including sandboxed code mode, for each build system using its matching CLI, app-server, and symbols archives.

GitOrigin-RevId: c951a3eb4557b539d53a12040237d5ef947f6bdf
2026-10-30 00:08:25 +00:00
..