chore: release v0.28.5

[fxrdhan]

Summary

Prepares v0.28.5 from dev at a975736 (#136 through #151). It does three things before the version bump: automates the rest of the release, brings the docs in line with the binary, and bumps the version. The twelve commits are meant to land as they are, so please use Rebase and merge rather than squash.

Release automation

1. ci(release): take the release notes from CHANGELOG.md
   • The GitHub release notes came from git-cliff over commit titles. Once a pull request is squashed, that leaves one line per PR, so the 45 fixes in test: audit the suite against independent oracles, and fix what it turned up #149 would have shown up as one.
   • The notes are now the version's section of CHANGELOG.md.
   • A Release notes job fails when that section is missing, and, on a tag, when the tag is not the version in Cargo.toml. It runs in the dry run too.
2. ci(release): bump the Homebrew formula in a job of its own
   • A tap token that cannot write, as on v0.28.4, now fails that job alone, instead of the job that creates the release.
3. ci(release): publish the crate to crates.io
   • Every release so far reached crates.io through a cargo publish run by hand. The workflow now publishes once the GitHub release is out, so cargo binstall never sees a version without binaries.
   • It authenticates by Trusted Publishing (OIDC), so no registry token is stored.
   • A dry run runs cargo publish --dry-run. For a version that is already published, that only warns, which I checked against 0.28.4.
4. ci(release): drop a stale note on --no-default-features builds
   • The header said that build does not work. It does, and CI checks it.

Docs checked against the binary

Every flag, environment variable, colour code, config key and theme key in the README, the three man pages, docs/ and the contributor guides was checked against the parser and the built binary.

• docs(theme)
  • The schema's filekinds.symlink used oneOf. A plain style such as { foreground: Cyan } matches two of its branches, so every theme that styled symlinks failed validation, including the README's own schema example. It is anyOf now, and the schema test pins that.
  • The examples now use is_bold and is_underline, the names the schema and the man pages use.
• fix(options): -O's help text and the completions said "Mac, BSD, and Windows only". Linux has been supported for a while.
• docs(readme):
  • --spacing also applies in the long view, and caps at 1000, not 255.
  • There is no recent alias. There is an undocumented relative-recent:DAYS.
  • CLICOLOR, CLICOLOR_FORCE and LEZ_OVERRIDE_AUTO_COLOR are not read at all.
  • The "Syntax highlighting" claim is gone.
  • The duplicate Installation section is merged into one.
• docs(man) for lez(1):
  • Corrects --spacing, and adds relative-recent and relative-recent:DAYS.
  • --git-repos draws no ~ symbol.
  • Adds --git-ignore to what --no-git overrides. LEZ_OVERRIDE_GIT acts as --no-git in full.
  • An empty NO_COLOR does not turn colours off.
  • Corrects the config precedence: LEZ_CONFIG_FILE replaces discovery, and all four global file names are listed.
  • Adds exit status 2 and LEZ_DEBUG.
  • Moves --stdin and --stdin0 to the meta options.
  • Fixes the auto sentence, which had it backwards ("if run while in a tty").
• docs(man) for lez_colors(5):
  • Drops ic, which nothing reads.
  • Adds hw and the Finder-tag keys Tn to To.
  • ff covers every platform, and LS_COLORS takes twelve codes, not eleven.
  • Lists every ANSI code the parser accepts, including blink, reverse, backgrounds and 24-bit colour.
• docs(man) for lez_colors-explanation(5):
  • Adds the theme keys the outline was missing.
  • theme.yaml is read too, music is cyan, and data files get a colour line.
• docs: Fixes TESTING.md's test path, adds the REUSE command CONTRIBUTING.md promised and the branch to work from, and corrects SECURITY.md's development branch.

The version

• chore: lez v0.28.5 changelogs, version bump
  • Cargo.toml, Cargo.lock and the AUR and Homebrew packaging files move to 0.28.5.
  • CHANGELOG.md gains the 0.28.5 section, including a Behaviour Changes part for what test: audit the suite against independent oracles, and fix what it turned up #149 changed on purpose.
  • packaging/homebrew/lez.rb keeps v0.28.4's sha256 until the tag exists, as in the v0.28.4 release.

Before tagging: one setting on crates.io

On crates.io, open lez → Settings → Trusted Publishing → Add → GitHub and enter:

Field	Value
Repository owner	fxrdhan
Repository name	lez
Workflow filename	release.yml
Environment	empty

Without this, the crates.io job fails at authentication. The GitHub release and Homebrew are not affected, and cargo publish by hand still works.

After merging

git fetch origin
git push origin origin/dev:main                       # main fast-forwards; it has nothing dev lacks
git tag -a v0.28.5 -m "Release v0.28.5" origin/dev
git push origin v0.28.5                               # starts release.yml: GitHub release, crates.io, Homebrew

After that, update the sha256 in packaging/homebrew/lez.rb, as chore(homebrew) did for v0.28.4.

Found, but not changed here

• missing_target in theme.yml is ignored, while mi= works. The theme struct has no field for it, so this is code to add, not a typo.
• --time-style refuses locale and posix-STYLE. TIME_STYLE accepts them, and so does GNU ls --time-style.
• The powertest snapshots (tests/ptests) are stale. One help snapshot is missing --stdin0, --percent-digits and other flags. The suite does not run in CI, and they are regenerated with just idump, not by hand.
• --total-size is documented as "unix only", but the code computes it on Windows too. Every test of it is #[cfg(unix)], so that claim is unverified either way.

Type of Change

• 🐛 Bug fix (non-breaking change fixing an issue)
• ✨ New feature (non-breaking change adding functionality)
• ⚡ Performance improvement
• ♻️ Code refactor / clean-up
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 📝 Documentation / Man pages / Completions
• 🔧 Build / CI / Dependencies

Related Issues & Upstream References

• Resolves: none
• Upstream: none

Feature / Flag Checklist (if adding or modifying CLI flags)

No flags were added. -O's help text changed in src/options/parser.rs and in all five completions, along with their eza copies.

How Has This Been Tested?

• Testing commands executed, at every commit:
  • cargo fmt --check.
  • cargo clippy --locked --all-targets --features git,inspect-archives -- -D warnings.
  • cargo nextest run --locked --workspace --all-targets --features git,inspect-archives: 1497 passed at each.
• At HEAD:
  • cargo test --locked --doc.
  • reuse lint and actionlint.
  • cargo publish --dry-run --locked.
  • The README and docs/theme.yml theme examples validated against the schema with jsonschema. A key neither style knows is still rejected.
• The new notes step, run locally in four cases:
  • A dry run passes.
  • A v0.28.5 tag passes.
  • A v0.28.4 tag fails on the Cargo.toml mismatch.
  • A changelog without the section fails.
• Every doc correction above was checked against the built binary or the parser that reads the value.
• Platforms verified: CI on this PR, including the Release dry run (binaries, man pages, notes, and the crates.io package check).

Contributor Checklist

• Base branch is set to dev (unless this is a release PR targeting main)
• My commits follow Conventional Commits format
• Tests covering the changes have been added/updated
• cargo clippy --all-targets passes with no warnings
• cargo nextest run (or cargo test) passes
• cargo fmt --check / nix fmt passes
• License headers (SPDX / REUSE) are properly preserved/added

🤖 Generated with Claude Code

https://claude.ai/code/session_01K1zQZxjBx5aUYbEcuEkXjk