[Enrique Saurez (esaurez)]

Summary

nvx 0.1.0-alpha.2 was packaged from a working tree that core.autocrlf had checked out with CRLF line endings. cargo package packs the working tree's bytes, so 220 of the package's files differ from c9aa406, the commit that its .cargo_vcs_info.json names, which stores them with LF. Git reported that tree as clean, so the package isn't marked dirty either. Builds are unaffected, because rustc reads CRLF sources as LF and the crate embeds no files, but a consumer that checks a package against the commit it names rejects 0.1.0-alpha.2. 0.1.0-alpha.1 matched its commit byte for byte.

• .gitattributes: nvx-rs/** text=auto eol=lf checks the crate's directory out with LF on every platform, whatever core.autocrlf says. Every file under nvx-rs is already stored with LF, so no content changes.
• nvx-rs/Cargo.toml moves to 0.1.0-alpha.3, which aci_edge_sandboxes and aci_edge_sandboxes_model now require. In the three lockfiles, only nvx's version changes. Since 0.1.0-alpha.2, dev has added the strict GPT reader (nvx-rs: add a strict GPT reader for layered root disks #673).

Publishing

Git applies the new attribute only when it writes a file. A clone that already has CRLF copies keeps them for every file that this merge doesn't change, and git status still shows it as clean. Publish from a fresh clone of the merged dev commit, or refresh nvx-rs in the existing clone first:

git rm -r -q --cached nvx-rs
git reset -q --hard

Once 0.1.0-alpha.3 is out, 0.1.0-alpha.2 could be yanked.

Validation

On a Windows host, in fresh clones with core.autocrlf=true:

• At this branch, nvx-rs checks out with LF, while other directories check out with CRLF. cargo package --locked packages 230 files and verifies the build. All 228 files that come from nvx-rs, including Cargo.toml.orig, have the blobs of the commit that .cargo_vcs_info.json names, and none has CRLF.
• At dev (d945e27), the same steps package 226 files with CRLF.
• A clone checked out at dev and then switched to this branch still has 225 CRLF files in nvx-rs. After the two commands above, it has none.
• cargo metadata --locked succeeds in nvx-rs, aci_edge_sandboxes and tests/runtime-adapter.

[Copilot]

🟢 Approval recommended

The version updates are consistent, the LF rule is narrowly scoped, and no unresolved correctness issues were identified.

No open issues 🎉

What changed in this PR

Prepares nvx 0.1.0-alpha.3 for publication and enforces LF checkouts for its source directory so packaged files match the referenced Git commit across platforms.

Changes:

• Adds a scoped LF checkout rule for nvx-rs.
• Bumps the crate and both sandbox dependency requirements to 0.1.0-alpha.3.
• Synchronizes the nvx version in all three affected lockfiles.

File	Description
tests/​runtime-adapter/​Cargo.lock	Updates the locked nvx version.
nvx-rs/​Cargo.toml	Sets the crate version to 0.1.0-alpha.3.
nvx-rs/​Cargo.lock	Updates the crate’s lockfile version.
aci_edge_sandboxes/​model/​Cargo.toml	Updates the model’s nvx requirement.
aci_edge_sandboxes/​Cargo.toml	Updates the sandbox library’s nvx requirement.
aci_edge_sandboxes/​Cargo.lock	Synchronizes the locked nvx version.
.gitattributes	Enforces LF for crate text files and explains why.

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The narrowly scoped checkout, version, dependency, and test changes are consistent, with no unresolved blocking findings.

No open issues 🎉

_{Review effort: Balanced}