Skip to content

feat(signals): deprecate legacy shutdown API - #4

Merged
josecelano merged 1 commit into
torrust:mainfrom
josecelano-bot:3-deprecate-legacy-shutdown-api
Nov 6, 2026
Merged

josecelano merged 1 commit into
torrust:mainfrom
josecelano-bot:3-deprecate-legacy-shutdown-api

Conversation

@josecelano-bot

Copy link
Copy Markdown
Contributor

Closes #3

Deprecates the legacy shutdown API in torrust_server_lib::signals (Halted, shutdown_signal, shutdown_signal_with_message, global_shutdown_signal) since 0.5.0, with removal planned for 0.6.0. No behaviour change, nothing removed. Started and cancellation_signal are untouched.

  • #[deprecated] notes name the replacement and the planned removal release.
  • #[allow(deprecated)] with a reason where the crate and its test still use the symbols; the crate builds warning-free.
  • New CHANGELOG.md entry: migration steps, support window (0.5.x), removal in a later breaking release.
  • Version bumped to 0.5.0. Not published to crates.io; that is the maintainer's action.

Checked: cargo fmt --check, linter all, clippy -D warnings, cargo test, cargo doc.

🤖 Generated with Claude Code

Deprecate Halted, shutdown_signal, shutdown_signal_with_message and
global_shutdown_signal since 0.5.0, planned for removal in 0.6.0.
Add CHANGELOG.md and bump the version to 0.5.0. No behaviour change.

Closes torrust#3

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@josecelano

Copy link
Copy Markdown
Member

ACK 2df974f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deprecate legacy shutdown API in signals (prerequisite for torrust-tracker SI-18)

2 participants