NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1072 by repository stars
Latest stable
v0.136.0
Last release today
21 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
482 releases · first in 2024
Drag across the ruler to compare, or tap a release to open it.
<!-- Release notes generated using configuration in .github/release.yml at fix/improve-image-comparision -->
<!-- Release notes generated using configuration in .github/release.yml at fix/improve-image-comparision -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.82.1...v0.82.2-rc.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
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:
restart: always or restart: unless-stopped are expected to stay running.restart policy are treated as restart: "no".restart: on-failure may remain exited after success, and restart: "no" is treated as one-time behavior and is not reconciled back to running.deploy.restart_policy behavior.More information on the restart policies can be found in the Docker Compose specification.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.82.0...v0.82.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
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 is now supported to
You can enable shallow cloning in two ways:
GIT_CLONE_DEPTH env vargit_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.
GIT_CLONE_DEPTH=1 for shallow clone behavior across deployments.GIT_CLONE_DEPTH=0 for full clone behavior.git_depth:
git_depth: 1 to force shallow for that deployment.git_depth: 0 to use global GIT_CLONE_DEPTH.no such image checks by @kimdre in https://github.com/kimdre/doco-cd/pull/1250Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.81.0...v0.82.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.81.0...v0.82.0-rc.1
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
The doco-cd documentation has a new home at doco.cd. The old Github repository wiki was fine for the beginning but it was showing its limitations more and more and with the new documentation, users can now finally also contribute to the wiki.
The wiki source code can be found at the /wiki/ directory if you are interested.
The version check, that runs when doco-cd is starting, now also sends a notification when Apprise is configured.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.80.1...v0.81.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.81.0-rc.1...v0.81.0-rc.2
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.80.1...v0.81.0-rc.1
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.80.0...v0.80.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
The custom webhook external secrets provider has been rewritten and is much more useful now.
If you use this provider, you have to change your configuration in the doco-cd container and in your .dooc-cd.yml deploy config files as the old configuration will no longer work.
See here: https://github.com/kimdre/doco-cd/wiki/External-Secrets#webhook
With the changes to the webhook provider, it is now possible to use more sophisticated APIs. I added a section to the external secrets wiki page how to use it for Bitwarden Vault / Vaultwarden users. See here: https://github.com/kimdre/doco-cd/wiki/External-Secrets#bitwarden-vault--vaultwarden
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.79.0...v0.80.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
This release adds the ability to write environment variables for variable interpolation directly in the deployment configuration.
For example
# .doco-cd.yml
name: demo
environment:
KEY: value
# docker-compose.yml
services:
test:
image: nginx:latest
labels:
- test=$KEY
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.78.0...v0.79.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Authorization header. More info in the wiki.*_FILE environment variable files (such as GIT_ACCESS_TOKEN_FILE). More info in the wiki.ssh://git@host:2222/user/repo.git) .Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.77.0...v0.78.0
<!-- Release notes generated using configuration in .github/release.yml at feat/decrypt-file-based-env-vars -->
<!-- Release notes generated using configuration in .github/release.yml at feat/decrypt-file-based-env-vars -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.77.0...v0.78.0-rc.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
You can now avoid service recreation and send signals to services when configs, secrets or bind mounts change. Useful for applications than can read config changes during runtime without having to restart or recreate the container or services that need to mount an entire filesystem.
Example use-cases:
/ to /host; since / always reflects repository changes, this causes unnecessary recreations.More info in the wiki: https://github.com/kimdre/doco-cd/wiki/Deploy-Settings#service-labels
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.76.0...v0.77.0
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.77.0-rc.1...v0.77.0-rc.2
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
When using docker compose with configs, secrets or bind mounts, changes to these resources will trigger a recreation of the service containers by default. To avoid this, you can set the new cd.doco.deployment.recreate.ignore service label to a YAML list of scopes that should be ignored for recreation.
More info in the wiki: https://github.com/kimdre/doco-cd/wiki/Deploy-Settings#service-labels
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.76.0...v0.77.0-rc.1
Nothing published for this version
Nothing published for this version
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
This Release adds a new API endpoint to manually trigger Poll jobs.
See also in the wiki.
| Endpoint | Method | Description | Query Parameters |
|---|---|---|---|
/v1/api/poll/run |
POST | Trigger a poll run for all polling targets in the body (JSON). | - wait (boolean, default: true): Wait for the poll run to finish before responding. |
The request body must be a JSON array of poll configurations, each containing at least a url field containing the Git clone URL to the repository.
The fields run_once and interval will be ignored for poll runs triggered via the API, as they are only relevant for the scheduled poll runs.
Minimal example using the default settings:
curl --request POST \
--url 'https://cd.example.com/v1/api/poll/run?wait=true' \
--header 'content-type: application/json' \
--header 'x-api-key: your-api-key' \
--data '[
{
"url": "https://github.com/your/repo.git",
}
]'
Example with custom reference and inline deployment configuration:
curl --request POST \
--url 'https://cd.example.com/v1/api/poll/run?wait=true' \
--header 'content-type: application/json' \
--header 'x-api-key: your-api-key' \
--data '[
{
"url": "https://github.com/your/repo.git",
"reference": "dev",
"deployments": [
{
"name": "my-app",
"working_dir": "/app",
"env_files": [
".env"
]
}
]
}
]'
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.75.0...v0.76.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.76.0-rc.1...v0.76.0-rc.2
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
This PR adds a new API endpoint to manually trigger Poll jobs.
See also in the wiki.
| Endpoint | Method | Description | Query Parameters |
|---|---|---|---|
/v1/api/poll/run |
POST | Trigger a poll run for all polling targets in the body (JSON). | - wait (boolean, default: true): Wait for the poll run to finish before responding. |
The request body must be a JSON array of poll configurations, each containing at least a url field containing the Git clone URL to the repository.
The fields run_once and interval will be ignored for poll runs triggered via the API, as they are only relevant for the scheduled poll runs.
Minimal example using the default settings:
curl --request POST \
--url 'https://cd.example.com/v1/api/poll/run?wait=true' \
--header 'content-type: application/json' \
--header 'x-api-key: your-api-key' \
--data '[
{
"url": "https://github.com/your/repo.git",
}
]'
Example with custom reference and inline deployment configuration:
curl --request POST \
--url 'https://cd.example.com/v1/api/poll/run?wait=true' \
--header 'content-type: application/json' \
--header 'x-api-key: your-api-key' \
--data '[
{
"url": "https://github.com/your/repo.git",
"reference": "dev",
"deployments": [
{
"name": "my-app",
"working_dir": "/app",
"env_files": [
".env"
]
}
]
}
]'
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.75.0...v0.76.0-rc.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
More bug fixes and minor improvements.
Fixed the issue with bind mounts throwing an symlink target X escapes the repository root Y.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.74.0...v0.75.0
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
This release improves the change detection and file decryption.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.73.2...v0.74.0
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.73.2...v0.74.0-rc.1
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
More bug fixes for the change detection logic.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.73.1...v0.73.2
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
This version fixes errors with certain field types in the Docker Compose specification when hashing the compose configuration for the change detection logic.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.73.0...v0.73.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
I rewrote the entire change detection logic to hopefully solve the issues with constant and/or inconsistent redeployments. I hope I was able to fix the issues with this change, if not please document it in the issue https://github.com/kimdre/doco-cd/issues/1055.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.72.3...v0.73.0
<!-- Release notes generated using configuration in .github/release.yml at fix/1055-redeploy-of-all-services-if-one-thing-changes -->
<!-- Release notes generated using configuration in .github/release.yml at fix/1055-redeploy-of-all-services-if-one-thing-changes -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.72.2...v0.73.0-rc.1
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
no such image error in image cleanup job by @kimdre in https://github.com/kimdre/doco-cd/pull/1104Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.72.2...v0.72.3
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
/ by @qianlongzt in https://github.com/kimdre/doco-cd/pull/1087Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.72.1...v0.72.2
<!-- Release notes generated using configuration in .github/release.yml at fix/resolve-paths -->
<!-- Release notes generated using configuration in .github/release.yml at fix/resolve-paths -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.72.1...v0.72.2-rc.1
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
The previous release contained a bug that caused deployments to fail when no custom compose file names were used.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.72.0...v0.72.1
Doco-cd now uses Docker Client v29 and Docker Compose v5, which brings some breaking changes and deprecations:
<!-- Release notes generated using configuration in .github/release.yml at main -->
extends: or include: definitions now should be able to detect changes correctly.extends: or include: definitions by @kimdre in https://github.com/kimdre/doco-cd/pull/1070Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.71.0...v0.72.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.70.0...v0.71.0
<!-- Release notes generated using configuration in .github/release.yml at fix/1057-external-secrets-with-retry -->
<!-- Release notes generated using configuration in .github/release.yml at fix/1057-external-secrets-with-retry -->
Pre-release to test the new external secrets request retrier
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.70.0...v0.71.0-rc.1
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
The new app setting PASS_ENV (boolean, default: false) controls whether environment variables from the doco-cd container should be passed to the deployment environment for docker compose variable interpolation. Use with caution, as this may expose sensitive information to the deployment environment.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.69.1...v0.70.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.69.0...v0.69.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.68.0...v0.69.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Deployments now run as concurrent task, grouped by repository and Git reference (e.g. branch or tag). Multiple deployments with the same repository but different references run sequentially, while those with the same repository and reference run in parallel.
MAX_CONCURRENT_DEPLOYMENTS (default: 4) app setting to change how many deployments can run concurrently.deployments_active: Number of currently active deploymentsdeployments_queued: Number of queued deployments waiting to startFull Changelog: https://github.com/kimdre/doco-cd/compare/v0.67.1...v0.68.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.67.0...v0.67.1
Nothing published for this version
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
This release adds a generic webhook provider for retrieving external secrets.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.66.0...v0.67.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.65.1...v0.66.0
<!-- Release notes generated using configuration in .github/release.yml at ci/fix -->
<!-- Release notes generated using configuration in .github/release.yml at ci/fix -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.65.2-rc.1...v0.65.2-rc.2
<!-- Release notes generated using configuration in .github/release.yml at ci/fix -->
<!-- Release notes generated using configuration in .github/release.yml at ci/fix -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.65.1...v0.65.2-rc.1
Nothing published for this version
One column per month.