[josecelano-bot]

Closes #5

Removes the legacy shutdown API deprecated since 0.5.0 and prepares release 0.6.0.

• Removed from torrust_server_lib::signals: Halted, shutdown_signal, shutdown_signal_with_message, global_shutdown_signal, and their test. Started and cancellation_signal are kept.
• Dropped the now-unused tokio signal feature and the derive_more dependency (Cargo.lock refreshed).
• Version bumped to 0.6.0; CHANGELOG.md has a ## 0.6.0 / ### Removed section pointing to the 0.5.0 migration steps.

Not published to crates.io: the maintainer publishes 0.6.0 as part of torrust-tracker SI-19 (EPIC 1488).

Checks: linter all, cargo clippy --all-targets -- -D warnings, cargo test pass.

🤖 Generated with Claude Code

[josecelano]

ACK 699132d

[Copilot]

🟢 Approval recommended

No active review issues are identified for the deprecated shutdown API removal and associated 0.6.0 updates.

No open issues 🎉

What changed in this PR

Prepares torrust-server-lib 0.6.0 by removing the shutdown API deprecated in 0.5.0, completing the migration to caller-owned cancellation described in issue #5. Publishing remains outside this PR’s scope.

Changes:

• Removes the four legacy shutdown symbols and their test while retaining Started and cancellation_signal.
• Drops derive_more and Tokio’s signal feature, updating the lockfile accordingly.
• Bumps the version to 0.6.0 and documents the breaking changes and migration guidance.

File	Description
src/​signals.rs	Removes the legacy shutdown API and test; updates cancellation documentation.
CHANGELOG.md	Adds the 0.6.0 removal notes and points to migration steps.
Cargo.toml	Bumps the version and removes unused dependencies and features.
Cargo.lock	Updates the crate version and removes unused dependency entries.

_{Review effort: Balanced}

[da2ce7]

Reviewed at 699132d271edbc8b49fa96e78889087de65bac42 (post-merge). Recomputed from the bytes at this head, against the merge base 0ad8ca094; git merge-tree against main 0ad8ca094 writes tree 587a4e64, identical to the head's own tree: no conflicts, the head is one commit directly on main.

Label: POST_MERGE_FINDINGS. The PR merged at 2026-11-10T13:14:34Z as 2dd04f494, while this round was running, so this review records no verdict and no ACK; the round found nothing blocking, and its one Suggestion stands at the merged head for a follow-up before the 0.6.0 release is published.

Process: with no review skills here, CHANGELOG.md, the CI workflow and the deprecation PR (#4) are the precedent, and the tracker's review-pr, commit-changes and open-pull-request skills apply by analogy.

The change against its claim: the four items carrying #[deprecated] at 0ad8ca094 (Halted, global_shutdown_signal, shutdown_signal, shutdown_signal_with_message) are removed with their legacy test, and nothing else public changes: Started and cancellation_signal keep declaration and body, and the derive_more::Display import and the one doc link to a removed item go too. Two dependency edges go away, torrust-server-lib -> derive_more and tokio -> signal-hook-registry (the signal feature); the nine packages removed from Cargo.lock are exactly those unreachable once both are cut, and no retained package changes version or checksum. 0.5.0 to 0.6.0 is the breaking bump on 0.x, and the changelog entry names every removed item and the feature and dependency drop, and points to the 0.5.0 migration steps in the earlier entry's format.

Downstream: the tracker's six manifests require "0.5.0", a caret range that excludes 0.6.0, so nothing moves until its planned removal step raises them; develop still imports Halted in eight files, shutdown_signal_with_message in axum-server and global_shutdown_signal in udp-server, all of which that step removes. Every tracker crate calling tokio::signal enables the feature itself.

Hygiene: Conventional subject with the ! marker; the body matches the diff; author equals committer; one attribution footer, which no rule in either tree forbids and which the earlier commits share; git diff --check is clean; the only closing keyword is Closes #5 in the description, which the diff implements.

Findings: F1 (Suggestion, inline, non-blocking).

Checked, no finding: no unused import or dead code is left; import grouping matches rustfmt.toml; tests go from ten to nine, minus the legacy test; no file outside the changelog names a removed item, README.md and src/lib.rs included; the description matches the diff, and its title's "release" is the version preparation it says is not yet published.

Checks

On the loop's compute node at this head, against main 0ad8ca094 (receipts server-gates-kranich-586 and -586b): cargo +nightly fmt --check, cargo build --locked --all-targets, cargo test --workspace --locked (9 passed; 10 at main, the difference being the removed legacy test), cargo clippy --all-targets --all-features --locked -- -D warnings, cargo doc --no-deps with warnings denied and linter all all exit 0, and the tree is left clean. Downstream, the tracker at develop 1df1ecdf0 with its six torrust-server-lib requirements raised to 0.6.0 and patched to this head stops at torrust-tracker-axum-server (E0432, unresolved signals::Halted and signals::shutdown_signal_with_message), as expected: its "0.5.0" requirements keep it on 0.5 until its own removal step (tracker issue 2801) lands. GitHub checks at this head at posting time: "Lint and Test: completed/success". At posting, main is 2dd04f494 (the merge of this PR).

[da2ce7]

[Suggestion][F1] Library code no longer needs tokio's macros, net or rt-multi-thread; 0.6.0 is the cheap window to trim them

After this change the non-test code uses only tokio::sync::Mutex (sync) and tokio::task::JoinHandle (rt). The last non-test use of macros was tokio::select! in the removed global_shutdown_signal and shutdown_signal; net and rt-multi-thread have no user at either commit. #[tokio::test] still needs macros and rt, which a dev-dependency can carry.

Dropping a feature from a published dependency is itself breaking for a consumer that relies on feature unification, so this release is the moment it costs nothing extra, for example tokio = { version = "1", features = [ "rt", "sync" ] } with [dev-dependencies] tokio = { version = "1", features = [ "macros", "rt" ] } and a changelog line. Optional: the tracker enables all of these itself, and keeping them is harmless.