Michael Bolin 2eeeb56d02 ci: block new workspace crate features ...

## Why

We already enforce workspace metadata and lint inheritance for `codex-rs` manifests, but we still allow new crate features to slip into the workspace. That makes it too easy to add more Cargo-only feature permutations while we are trying to eliminate them.

## What changed

- extend `verify_cargo_workspace_manifests.py` to reject new `[features]` tables in workspace crates
- reject new optional dependencies that create implicit crate features
- reject new workspace-to-workspace `features = [...]` activations and `default-features = false`
- add a narrow temporary allowlist for the existing feature-bearing manifests and internal feature activations
- make the allowlist self-shrinking so a follow-up removal has to delete its corresponding exception

2026-04-01 10:52:38 -07:00

..

build-zsh-release-artifact.sh

fix: keep zsh-fork release assets after removing shell-tool-mcp (#15644)

2026-03-24 12:56:26 -07:00

install-musl-build-tools.sh

Fix linux-musl release link failures caused by glibc-only libcap artifacts (#11556)

2026-02-12 08:08:32 +00:00

run-argument-comment-lint-bazel.sh

ci: run Windows argument-comment-lint via native Bazel (#16120)

2026-03-30 15:32:04 -07:00

run-bazel-ci.sh

ci: run Windows argument-comment-lint via native Bazel (#16120)

2026-03-30 15:32:04 -07:00

rusty_v8_bazel.py

V8 Bazel Build (#15021)

2026-03-19 18:05:23 -07:00

verify_bazel_clippy_lints.py

ci: sync Bazel clippy lints and fix uncovered violations (#16351)

2026-03-31 17:09:48 -07:00

verify_cargo_workspace_manifests.py

ci: block new workspace crate features

2026-04-01 10:52:38 -07:00