chore(deps): bump sandogasa-rpmvercmp from 0.18.2 to 0.19.1

[dependabot]

Bumps sandogasa-rpmvercmp from 0.18.2 to 0.19.1.

Changelog

Sourced from sandogasa-rpmvercmp's changelog.

v0.19.1

Man pages for every tool

Each tool now ships a man page at tools/<tool>/man/<tool>.1, generated from its clap definition by the new sandogasa_cli::man module. One page per tool documents the whole CLI: the top-level options, then every subcommand as a subsection under COMMANDS, so man ebranch covers check-update and the rest rather than sending the reader to nine separate pages.

Generating from clap is what keeps the pages honest — the man page and --help are rendered from one definition, so they cannot disagree about what a tool accepts. A man_page_matches_cli test in each tool's main.rs fails when a committed page stops documenting a visible flag or subcommand, which makes drift a test failure rather than something a reader discovers. scripts/gen-man.sh regenerates every page.

The pages are committed and included in the published crates, so a packager can install them with install -m644 without building or running the binaries — a cross-build for another architecture cannot execute the tool to scrape its --help.

Man page rendering is behind a new man feature on sandogasa-cli, off by default and enabled only as a dev-dependency, so shipped binaries do not carry the roff renderer. New workspace dependency: clap_mangen.

Man page footers name the version

The pages carried no version, and their .TH fields were shifted: clap_mangen writes an unset date as bare whitespace, which groff reads as an absent field, so every later field moved down one — the source was parsed as the date and the manual as the source. The footer read Sandogasa Manual | sandogasa | koji-lag(1) and the header fell back to groff's generic "General Commands Manual".

Setting the date fixes the shift, and the footer now reads the way man bash does — sandogasa 0.19.0 at the left, the page's date in the centre, koji-lag(1) at the right — with "Sandogasa Manual" in the header.

Because the version is in the page, man_page_matches_cli also checks it, so a page that falls behind the workspace version is a test failure. Regeneration therefore has to follow the version bump at release time, and forgetting it can no longer ship a stale footer.

Regenerating preserves the committed date of any page whose content has not otherwise changed, so a one-tool CLI change does not restamp

... (truncated)

Commits

• 6a7e7a8 release: v0.19.1
• 89e60ae sandogasa-cli: name the version in man page footers
• 51e6a93 build: add a Makefile as a task runner
• 143a582 tools: ship a man page per tool
• 3b59d1b sandogasa-cli: render man pages from the clap definition
• f410391 ebranch: auto-vote Review Request bugs
• 8333d83 docs: add CONTRIBUTING.md and a vendor-neutral AGENTS.md
• 4cbf4b3 docs: record the README convention in CLAUDE.md
• 07de44e docs: READMEs describe the tools, not the changes
• 5e7f6d2 release: v0.19.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[plusky]

14/14 green. Worth recording why a 0.x minor bump of the RPM version comparison is safe here: sandogasa-rpmvercmp ships from a workspace that versions every crate in lockstep, and gh api repos/slopfest/sandogasa/compare/v0.18.2...v0.19.2 shows zero files matching rpmvercmp among the 112 changed. The upstream changelog has no rpmvercmp entries in that range either, so the comparison algorithm is byte-identical and RPMVersion's ordering — before/after verdicts, downgrade, the list_packages state column — cannot shift.