Skip to content

feat(container): update image ghcr.io/kimdre/doco-cd ( 0.81.0 ➔ 0.83.0 )#1803

Merged
pwyde merged 2 commits intomainfrom
renovate/ghcr.io-kimdre-doco-cd-0.x
Apr 28, 2026
Merged

feat(container): update image ghcr.io/kimdre/doco-cd ( 0.81.0 ➔ 0.83.0 )#1803
pwyde merged 2 commits intomainfrom
renovate/ghcr.io-kimdre-doco-cd-0.x

Conversation

@deploy-demon
Copy link
Copy Markdown
Contributor

@deploy-demon deploy-demon Bot commented Apr 27, 2026

This PR contains the following updates:

Package Update Change
ghcr.io/kimdre/doco-cd minor 0.81.00.83.0

Release Notes

kimdre/doco-cd (ghcr.io/kimdre/doco-cd)

v0.83.0

Compare Source

What's Changed

🌟 Improvements
🐛 Bug Fixes
📦 Dependencies

Full Changelog: kimdre/doco-cd@v0.82.2...v0.83.0

v0.82.2

Compare Source

In the Media

For german users: Doco-CD was featured by Heise in a heise+ article, which will also be printed in the next issue of c't magazine, c't 10/2026.

What's Changed

When force_image_pull is set to true, the check for a changed image digest against the container image registry now returns correct results for mutable tags like latest.

🌟 Improvements
📦 Dependencies
📚 Miscellaneous

Full Changelog: kimdre/doco-cd@v0.82.1...v0.82.2

v0.82.1

Compare Source

What's Changed

There was a typo in the Reconciliation settings documentation that has been fixed: reconciliation.enable -> reconciliation.enabled.
If you have reconciliation.enable configured, you will need to adjust it. Sorry for that!

Reconciliation now handles one-time services correctly according to their restart policy:

  • Services with restart: always or restart: unless-stopped are expected to stay running.
  • Services with no explicit restart policy are treated as restart: "no".
  • Services with restart: on-failure may remain exited after success, and restart: "no" is treated as one-time behavior and is not reconciled back to running.
  • Swarm handling is separate and uses Swarm service modes and deploy.restart_policy behavior.

More information on the restart policies can be found in the Docker Compose specification.

🌟 Improvements
📚 Miscellaneous

Full Changelog: kimdre/doco-cd@v0.82.0...v0.82.1

v0.82.0

Compare Source

What's Changed

Periodic reconciliation

doco-cd now runs automatic reconciliation of deployed services to restore their desired state.

You can find more information on the Deploy Config wiki page:

[!Tip]
To keep a service/container stopped, you need to scale it down in you docker compose config, see Removing a container service.

[!Note]
Currently this is done in a fixed interval. In the future it is planned to trigger this by listening on specific events from the Docker daemon.

Shallow cloning

Shallow cloning is now supported to

  • speed up syncs
  • reduce network usage and the size of cloned repositories on the filesystem

You can enable shallow cloning in two ways:

  • Globally in the App Config with the GIT_CLONE_DEPTH env var
  • Per deployment in the Deploy Config with the git_depth setting (overrides the global config)

Setting these settings to 0 means "no depth limit" for global, and "use global value" for deploy config.

[!Note]

  • If a requested tag/SHA is not reachable in current shallow history, doco-cd deepens automatically before trying a full fetch.
  • Changing depth on an existing local repo triggers an automatic re-clone to keep repository state consistent.
Usage overview
  • Set global default:
    • GIT_CLONE_DEPTH=1 for shallow clone behavior across deployments.
    • GIT_CLONE_DEPTH=0 for full clone behavior.
  • Override per deployment with git_depth:
    • git_depth: 1 to force shallow for that deployment.
    • git_depth: 0 to use global GIT_CLONE_DEPTH.
✨ Features
🌟 Improvements
  • fix(swarm): implement retry logic for service update to handle "update out of sequence" errors by @​qianlongzt in #​1242
  • fix: normalize error messages in no such image checks by @​kimdre in #​1250
🐛 Bug Fixes
  • fix(external-secrets): prevent webhook body corruption during template rendering in newRequest by @​kimdre in #​1247
📦 Dependencies
📚 Miscellaneous

New Contributors

Full Changelog: kimdre/doco-cd@v0.81.0...v0.82.0


Configuration

📅 Schedule: (in timezone Europe/Stockholm)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.

| datasource | package                | from   | to     |
| ---------- | ---------------------- | ------ | ------ |
| docker     | ghcr.io/kimdre/doco-cd | 0.81.0 | 0.83.0 |


Signed-off-by: deploy-demon[bot] <188457976+deploy-demon[bot]@users.noreply.github.com>
@deploy-demon deploy-demon Bot force-pushed the renovate/ghcr.io-kimdre-doco-cd-0.x branch from c9f204b to b4db24a Compare April 28, 2026 07:55
@deploy-demon deploy-demon Bot added the area/truenas Changes made in the truenas directory. label Apr 28, 2026
@pwyde pwyde enabled auto-merge (squash) April 28, 2026 07:56
@pwyde pwyde merged commit f2255ea into main Apr 28, 2026
10 checks passed
@pwyde pwyde deleted the renovate/ghcr.io-kimdre-doco-cd-0.x branch April 28, 2026 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/truenas Changes made in the truenas directory. renovate/container type/minor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant