Skip to content

Bump service-manager from 0.7.1 to 0.11.0#180

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/service-manager-0.11.0
Open

Bump service-manager from 0.7.1 to 0.11.0#180
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/service-manager-0.11.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Mar 1, 2026

Bumps service-manager from 0.7.1 to 0.11.0.

Changelog

Sourced from service-manager's changelog.

[0.11.0] - 2026-02-18

Changed

  • BREAKING CHANGE: Extended RestartPolicy::OnFailure with two new fields to prevent infinite restart loops:
    • max_retries: Option<u32> — Maximum number of restart attempts before the service stops. When None, the service restarts indefinitely (previous behavior).
    • reset_after_secs: Option<u32> — Duration in seconds after which the failure counter resets. If the service runs successfully for this long, previous failures are forgotten and the retry counter starts fresh. When None, the platform default is used.
    • Migration: Add max_retries: None, reset_after_secs: None to existing RestartPolicy::OnFailure { delay_secs } constructions to preserve current behavior.

Added

  • WinSW: When max_retries is set, the WinSW backend generates multiple <onfailure action="restart"/> elements (one per retry) followed by <onfailure action="none"/> to stop the service after exhausting retries. When reset_after_secs is set, a <resetfailure> element is generated (unless a WinSW-specific reset_failure_time is already configured).
  • Other service managers (systemd, launchd, sc, OpenRC, rc.d) do not yet implement max_retries or reset_after_secs, but there is potential to extend them in the future (e.g., systemd's StartLimitBurst / StartLimitIntervalSec).
  • Added a fail subcommand to the system test binary for simulating crashing services.
  • Added a Windows system test (should_stop_winsw_service_after_max_retries) that verifies a failing WinSW service stops after exhausting its retry limit.

[0.10.0] - 2025-12-14

Changed

  • BREAKING CHANGE: Launchd services with restart policies (RestartPolicy::Always, OnFailure, or OnSuccess) no longer auto-start when install() is called. Services must now be explicitly started using start(). This provides cross-platform consistency where install() registers the service definition without starting it, matching the behavior of systemd and other service managers.
    • Services with KeepAlive configured are now installed with Disabled=true in the plist
    • The start() function removes the Disabled key and reloads the service
    • The autostart parameter continues to control only RunAtLoad (whether service starts on OS boot), not initial install behavior
    • Migration: Add explicit manager.start(ctx)? call after manager.install(ctx)? if you need the service to start immediately

Fixed

  • Fixed incorrect Launchd restart policy implementation for RestartPolicy::OnFailure and RestartPolicy::OnSuccess:
    • OnFailure now correctly uses KeepAlive dictionary with SuccessfulExit=false (restart on non-zero exit) instead of KeepAlive=true (always restart)
    • OnSuccess now correctly uses SuccessfulExit=true (restart on zero exit) instead of SuccessfulExit=false

[0.9.0] - 2025-11-22

... (truncated)

Commits
  • c5464bb chore(release): v0.11.0
  • ed3a02a chore: add .claude directory to the .gitignore
  • d6bca3f chore: add changelog entry for restart retry limits
  • 3795290 feat!: add restart retry limits to the on-failure restart policy
  • 840a78d Provide More Intuitive Behaviour for Launchd Services (#40)
  • 6eba67e chore(release): bump to version 0.9.0
  • 763b82e feat!: provide generic RestartPolicy enum
  • 0294d3b Merge pull request #34 from mickvandijke/fix-launchd-commands
  • 6479303 Bump to version 0.8.0
  • 88ba039 fix(launch): fix launchd_for_system
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Mar 1, 2026
Bumps [service-manager](https://github.com/chipsenkbeil/service-manager-rs) from 0.7.1 to 0.11.0.
- [Changelog](https://github.com/chipsenkbeil/service-manager-rs/blob/main/CHANGELOG.md)
- [Commits](chipsenkbeil/service-manager-rs@v0.7.1...v0.11.0)

---
updated-dependencies:
- dependency-name: service-manager
  dependency-version: 0.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/cargo/service-manager-0.11.0 branch from fd67ef8 to 36934f9 Compare March 1, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants