Pierre Warnier bf0550374d shadow-core: name the package uu_shadow_core, as crates.io knows it (#316) ...

The library was published as uu_shadow_core (0.2.1) because shadow-core
on crates.io belongs to an unrelated project, but the manifest still
said shadow-core, so a publish from a checkout could not work and the
crates.io copies fell three minor versions behind. The package is now
uu_shadow_core; its Rust name stays shadow_core through [lib] name, and
every dependant reaches it through the same `shadow-core` dependency
key with `package = "uu_shadow_core"`, so no code changes. The fuzz
workspace, the lockfile and the two `-p` invocations in ci.yml follow.

CONTRIBUTING gains the publish order: the library, the tool crates, the
five thin crates that wrap another tool's crate, then the multicall.

`cargo publish --dry-run -p uu_shadow_core` packages 32 files;
`make check` in the container is green.

2026-09-15 12:44:02 +02:00

..

corpus

tests: one binary, spawn the real tool, and assert on what it prints (#273)

2026-09-04 16:46:07 +02:00

fuzz_targets

tests: one binary, spawn the real tool, and assert on what it prints (#273)

2026-09-04 16:46:07 +02:00

.gitignore

tests: add proptest, edge cases, fuzz targets, integration tests, docs

2026-03-23 14:11:19 +01:00

Cargo.toml

shadow-core: name the package uu_shadow_core, as crates.io knows it (#316)

2026-09-15 12:44:02 +02:00