chore(release): bump to 5.5.0

[Jaro-c]

Summary

Bumps to 5.5.0, MINOR. Everything in it is already on main; this is the version stamp so the tag can be cut.

What 5.5.0 contains

User-facing

• podup update no longer overwrites a Homebrew or Scoop install (fix(update): detect Homebrew and Scoop, not only apt #1609). It refused only for dpkg, and off Linux did not look at all, so on those two it rewrote the binary underneath a manifest that still claimed to know the contents.
• On an apt install, the refusal also says when apt will never do it either (feat(update): say so when nothing will ever update an apt-installed podup #1612).
• The package now also requires glyndor-archive-keyring (fix(packaging): require glyndor-archive-keyring #1607), which ships the rule pointing unattended-upgrades at Glyndor.
• podup is no longer published to crates.io (chore: stop publishing podup to crates.io #1606).

Not user-facing: the seven rust/cleartext-logging alerts, all now closed as fixed (#1611); Dependabot covering the two excluded lockfiles (#1604); two files split off the line-limit cap (#1605); README corrections (#1601).

MINOR, and why not MAJOR

No pull request in this release carries the breaking label, which standards/releases makes the marker, and no command's flags or output changed.

The one arguable case is podup update now refusing on Homebrew and Scoop where it previously overwrote. What it did before corrupted the manager's record of the file, so this is a fix rather than a withdrawal of function — and the refusal names that manager's own upgrade command.

Three manifests, not two

Cargo.lock stamps the version too, and --locked refuses to update it during a build. A bump touching only Cargo.toml and debian/changelog leaves the lock claiming 5.4.0, and the release build then fails at the gate rather than at review. Caught here rather than at tag time:

error: cannot update the lock file … because --locked was passed

Test plan

• All three manifests agree at 5.5.0: Cargo.toml, Cargo.lock, debian/changelog
• dpkg-parsechangelog reads the new entry: Source podup, Version 5.5.0
• cargo fmt --all --check and cargo clippy --locked --all-targets --all-features -- -D warnings, both clean
• cargo test --locked --all-features --lib --tests exits 0: 2400 passed, 0 failed
• cargo build --locked succeeds, which is what proves the lock was updated rather than assumed

Checklist

• Targets develop
• Commits are signed off (DCO, git commit -s) and signed
• Labels applied
• No secrets, keys or credentials in code, logs or fixtures
• Cargo.toml and debian/changelog are at the same version — the release gate compares them
• Docs updated if behaviour changed. The behaviour changes shipped with their own pull requests

Signed-off-by: Jaro-c 75870284+Jaro-c@users.noreply.github.com