Skip to content

fix(deps): update rust crate bollard to 0.21.0#294

Merged
renovate[bot] merged 1 commit intomasterfrom
renovate/bollard-0.x
May 4, 2026
Merged

fix(deps): update rust crate bollard to 0.21.0#294
renovate[bot] merged 1 commit intomasterfrom
renovate/bollard-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 4, 2026

This PR contains the following updates:

Package Type Update Change
bollard dependencies minor 0.20.00.21.0

Release Notes

fussybeaver/bollard (bollard)

v0.21.0

Compare Source

What's Changed

New Contributors

Full Changelog: fussybeaver/bollard@v0.20.2...v0.21.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot enabled auto-merge (squash) May 4, 2026 13:27
@claude
Copy link
Copy Markdown

claude Bot commented May 4, 2026

Dependency Update Review: bollard 0.20.0 → 0.21.0

This is a Renovate-generated minor version bump. The changes are straightforward — Cargo.toml version pin and the corresponding Cargo.lock updates (bollard, bollard-stubs, windows-sys cascade).

Notable upstream changes relevant to dtop

Potential improvements:

  • Log parsing fix (fix: Parse logs where there is no trailing newline — bollard #714): Directly benefits dtop's log streaming (docker/logs.rs). Logs that previously had truncation or parsing issues should now be handled correctly.
  • Docker API 1.53 support (bollard-stubs bumped from 1.52.1 to 1.53.1): Keeps the client current with newer Docker daemon versions.

Potential risk to watch:

  • New "stopping" container state added via Podman support (fix(codegen): add Podman "stopping" state — bollard #715): dtop's container state handling in core/types.rs and action availability logic (docker/actions.rs) may encounter this state from Docker daemons as well. If the state is unhandled or falls through to a default arm, the UI might show an unexpected state or the action menu might not offer the right options. Worth verifying ContainerState handles unknown/new states gracefully.

Assessment

The diff is minimal and correct — only the version pin in Cargo.toml and the lock file update. No application code changes. The log parsing fix is a net improvement. The main item to verify before merging is that CI passes cleanly (build + tests), which will surface any API breakage from the stubs update. Auto-merge is already enabled, so this should be fine to let through once CI is green.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 4, 2026

Docker Image Built Successfully

docker pull ghcr.io/amir20/dtop:pr-294

@renovate renovate Bot force-pushed the renovate/bollard-0.x branch from 4779a2d to 997985b Compare May 4, 2026 13:34
@renovate renovate Bot merged commit 593987f into master May 4, 2026
9 of 10 checks passed
@renovate renovate Bot deleted the renovate/bollard-0.x branch May 4, 2026 13:38
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.

0 participants