发布

  • test(paths): gate #401 paths-array test on a live PathJail
    Release / SDK release gate (push) Has been cancelled
    Release / Build aarch64-apple-darwin (push) Has been cancelled
    Release / Build x86_64-apple-darwin (push) Has been cancelled
    Release / Build aarch64-unknown-linux-musl (push) Has been cancelled
    Release / Build aarch64-unknown-linux-gnu (push) Has been cancelled
    Release / Build x86_64-unknown-linux-musl (push) Has been cancelled
    Release / Build x86_64-pc-windows-gnu (push) Has been cancelled
    Release / Build x86_64-unknown-linux-gnu (push) Has been cancelled
    Release / Build x86_64-pc-windows-msvc (push) Has been cancelled
    Release / Create Release (push) Has been cancelled
    Release / Publish to crates.io (push) Has been cancelled
    Release / Publish to npm (push) Has been cancelled
    Release / Update Homebrew (push) Has been cancelled
    Release / Announce on Twitter (push) Has been cancelled

    frostbyte_neo 发布于 2026-06-13 08:22:59 +00:00

    CI runs cargo test --all-features, which enables the no-jail feature.
    That compiles PathJail out, so resolve_tool_paths resolves every path and
    the new explicit_unresolvable_paths_array_errors test never saw the
    out-of-scope rejection it asserts — failing the "Run tests" step on every
    release builder.

    Gate the test with #[cfg(not(feature = "no-jail"))], matching the existing
    PathJail unit tests in core::pathjail, and drive it with an absolute path
    whose only existing ancestor is / so the jail decision is deterministic and
    independent of allow-list state left behind by other tests. The test still
    runs (and passes) under the default feature set, giving real #401 coverage.

    Co-authored-by: Cursor cursoragent@cursor.com

    下载附件