Prepare 3.2.0

[allenap]

Release preparation for 3.2.0, on a branch rather than straight onto master so that the new Package job gets a run before any of it is tagged.

The Package job, and why --all-features

The interesting piece. cargo package packs each crate, unpacks it again, and builds that copy — so anything the build needs but the archive lacks fails right there. This crate has exactly such a dependency: the macros read the words/ lists from disk at compile time, so a list missing from the archive breaks every downstream build while the repository itself keeps working perfectly.

The catch is that cargo package verifies with default features only, and those reach words/{small,medium,large} and nothing else. Excluding words/luxembourgish/ on purpose shows the difference:

cargo package --workspace                 →  passes, omission unnoticed
cargo package --workspace --all-features  →  error: proc macro panicked
    could not read .../target/package/petname-3.2.0/words/luxembourgish/adjectives.txt

So the job runs the --all-features form, and the release checklist gains the same step ahead of the version-bump commit. This seemed better than writing a test that asserts a file list, which would check the manifest rather than whether the result actually builds.

Trimming the published crate

exclude drops development scaffolding — CI workflows, editor settings, scripts/, AGENTS.md, dotfiles — taking the archive from 44 files to 34, 778 KiB.

It's a deny-list rather than an include allow-list on purpose, and there's a comment in Cargo.toml saying why: a wrong deny-list ships a few stray files, whereas a wrong allow-list silently drops a words/ directory. The failure modes are not symmetric. The Package job covers the residual risk in the direction that matters.

The other two commits

The Luxembourgish caveat previously lived only in the headers of the word list files, where nobody consuming the crate would ever see it. It's now in the README's Languages section and in the lang::luxembourgish module docs, so 3.2.0 doesn't present one non-native speaker's guesses at gender as settled. It comes out again once the lists have had a native pass.

The Upgrading section loses "From 3.0.0 to 3.0.1", which existed mainly to say that nothing was required in order to upgrade. Releases within a major version are additive here, so the section now says that once at the top and carries the major transitions alone. Nothing linked to the removed anchor.

Verification

cargo fmt --check; cargo clippy --workspace --all-features --all-targets -D warnings; the full test suite; cargo hack --workspace --feature-powerset build and test (426 passing groups, 0 failures); scripts/doc; scripts/semver-checks, which reads this as 3.1.0 -> 3.2.0 (minor change) and confirms the bump is adequate; and cargo package --workspace --all-features. The -h block in the README is byte-identical to actual -h output.

After merging

Tag v3.2.0 on master, push tags, then cargo publish --workspace. Pushing the tag fires the Release workflow, which builds with --all-features, so Luxembourgish lands in the binaries and the Homebrew bottle without any further change.