NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1091 by repository stars
Latest stable
v0.133.2
Last release 9 days ago
06 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
478 releases · first in 2024
Drag across the ruler to compare, or tap a release to open it.
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 -->
Webhooks that got triggered by branch or tag deletion events will now be skipped/ignored.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.62.0...v0.63.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Webhooks now trigger deployments asynchronously. Adding the wait=true query paramater to the webhook url brings back the old, synchronous behaviour which keeps the request open until the deployment is finished or the request times out.
E.g. /v1/webhook?wait=true
See https://github.com/kimdre/doco-cd/wiki/Endpoints#query-parameters
The API endpoints for Swarm stacks have been improved:
/v1/api/stack/{stackName}/runFull Changelog: https://github.com/kimdre/doco-cd/compare/v0.61.1...v0.62.0
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 fix/970-restart-replicated-job -->
<!-- Release notes generated using configuration in .github/release.yml at fix/970-restart-replicated-job -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.61.1...v0.62.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 -->
The DOCKER_SWARM_FEATURES app config is now handled correctly during deployments if set to false.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.61.0...v0.61.1
<!-- Release notes generated using configuration in .github/release.yml at fix/954-deploy-config-sha -->
<!-- Release notes generated using configuration in .github/release.yml at fix/954-deploy-config-sha -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.61.0...v0.61.1-rc.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
A couple of users requested a feature to run pre-deployment scripts within doco-cd, however this is out of the scope of this project. Such scripts should not be executed by the deployment tool directly but by the container runtime within the context of the containers/compose services. I added a new page to the wiki that explains how you can instead run init- and sidecar-containers and how to use container lifecycle hooks, that are already available in the compose specification: https://github.com/kimdre/doco-cd/wiki/Pre-Post-Deployment-Scripts
In the future I maybe extend this functionality for additional event hooks (e.g. such as the ones that ArgoCD provides) if more users ask for this.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.60.0...v0.61.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.61.0-rc.3...v0.61.0-rc.4
<!-- 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.61.0-rc.2...v0.61.0-rc.3
<!-- 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.60.0...v0.61.0-rc.2
<!-- Release notes generated using configuration in .github/release.yml at ci -->
<!-- Release notes generated using configuration in .github/release.yml at ci -->
Pre-release for testing new release build pipeline
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.60.0...v0.61.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 -->
This release adds support for Azure Devops repositories. Note, that the ADO-native webhooks (called Service Hooks) are not working. See the wiki for more information and a workaround using a CI pipeline.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.59.0...v0.60.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 contains a couple of fixes and improvements:
auto_discover inside the inline deployments block in your poll configs.DEPLOY_CONFIG_BASE_DIR app setting is now working as intended.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.58.0...v0.59.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Hey guys! I'm back from my long vacation with a new release. Doco-CD is now able to also clone and update any submodules in your repository before deployment.
Use the GIT_CLONE_SUBMODULES (boolean, default: true) app setting to toggle the submodule cloning.
Also, from now on, there are images available for devices using the ARMv7 (ARM 32bit) CPU architecture (like old raspberry pi). The only drawback is that the bitwarden secrets manager is not available in images for ARMv7.
I also fixed some issues with SSH cloning triggered by webhook events.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.57.0...v0.58.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.57.0...v0.58.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 -->
Okay, I said v0.55.0 was the last release this year but I still had some time, so I implemented the SSH support for repository cloning. See the new app settings to define the SSH private key for cloning:
SSH_PRIVATE_KEY -> the private key used for SSH cloningSSH_PRIVATE_KEY_FILE -> file containing the private keySSH_PRIVATE_KEY_PASSPHRASE -> passphrase for the private key (if key was generated with a passphrase)SSH_PRIVATE_KEY_PASSPHRASE_FILE -> file containing the passphraseAlso see Setup SSH Key in the wiki for a short tutorial how to generate and use a SSH key.
In the poll settings, you can then define a SSH clone url as the url value (e.g. git@github.com:kimdre/doco-cd.git)
Also in v0.56.0 I changed the container healthcheck command but I forgot to mention it in the release. If you have the healthcheck test key set in your docker-compose.yml, please change it so that the correct healthcheck command is being used.
healthcheck:
- test: [ "CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:80/v1/health" ] # Also change the port here if you change the default HTTP_PORT env var
+ test: [ "CMD", "/doco-cd", "healthcheck" ]
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.56.0...v0.57.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.55.0...v0.56.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 will probably be the last one this year. It contains lots of tweaks, improvements and preparations for upcoming features.
The force_image_pull deploy flag now checks for new images in the new pre-deploy stage without triggering a redeployment every time. This should reduce the noise in the logs and notifications.
Thank you all for your support. Enjoy your holidays and have a great start to the new year! 🎉
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.54.1...v0.55.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.54.0...v0.54.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 -->
prune_images (boolean, default: true) to toggle the image prune feature. If enabled, a job service runs on all Swarm nodes that executes a docker image prune.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.53.0...v0.54.0
<!-- Release notes generated using configuration in .github/release.yml at fix/830-swarm-empty-deployed-commit -->
<!-- Release notes generated using configuration in .github/release.yml at fix/830-swarm-empty-deployed-commit -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.53.0...v0.54.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 -->
doco-cd will now try to prune images, that are no longer in use after a deployment. Images, that are still in use by other containers, will be ignored/skipped.
You can use the prune_images (boolean, default: true) deploy setting to toggle this behaviour.
See the wiki: https://github.com/kimdre/doco-cd/wiki/Deploy-Settings
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.52.0...v0.53.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 -->
MAX_DEPLOYMENT_LOOP_COUNT (default: 2) to specify, when the detection should trigger a forced redeployment on consecutive deployments. Set the option to 0, to disable the detection logic.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.51.1...v0.52.0
<!-- Release notes generated using configuration in .github/release.yml at feat/824-add-gogs-as-supported-git-provider-for-webhooks -->
<!-- Release notes generated using configuration in .github/release.yml at feat/824-add-gogs-as-supported-git-provider-for-webhooks -->
Add Gogs as supported Git provider
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.51.1...v0.52.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 -->
You can now specify the namespace to get secrets or certs from OpenBao by specifying it as the first element of the reference syntax.
By default, the root namespace is used (root), but you can specify a different namespace by adding it as the first part of the reference.
A valid key-value secret reference should use the syntax: kv:<namespace(optional)>:<secretEngine>:<secretName>:<key>
A valid PKI certificate reference should use the syntax: pki:<namespace(optional)>:<secretEngine>:<commonName>
Example:
kv:prod-secrets:db-prod:username → Fetches the username key from the db-prod key-value secret in the prod-secrets secret engine in the root namespace.
kv:root:prod-secrets:db-prod:username → Same as above, explicitly specifying the root namespace.
See also the wiki: https://github.com/kimdre/doco-cd/wiki/External-Secrets#openbao
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.51.0...v0.51.1
<!-- 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 app setting/env var valled DEPLOY_CONFIG_BASE_DIR, which lets you set the relative path to the directory that contains the doco-cd deploy configs (globally for all repositories). By default this is still the root directory (/) of the repository.
[!NOTE] This does not affect/alter the
working_dirpath in the deploy configs. It must still be relative to the repository root.
See the wiki: https://github.com/kimdre/doco-cd/wiki/App-Settings
Also doco-cd now follows symlinks during the SOPS decryption.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.50.0...v0.51.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 two new features/improvements:
You can use the new auto-discovery feature to automatically deploy your stacks/projects from a directory structure.
Enable it with auto_discover: true, you can specify the directory to be scanned with the working_dir setting.
Doco-CD will then scan the directory for sub-directories that contain docker-compose.y(a)ml or compose.y(a)ml files and use the name of the sub-directory as the stack name (similiar to the name deploy setting).
See the wiki for more information: https://github.com/kimdre/doco-cd/wiki/Deploy-Settings#auto-discover-settings
For example with a file structure like this
.doco-cd.yml
apps/
├── wordpress/
│ ├── docker-compose.yml
│ └── .env
├── nginx/
│ ├── docker-compose.yaml
│ └── configs/
│ └── nginx.conf
└── misc/
└── image.png
and a .doco-cd.yml with the following content:
working_dir: apps/
auto_discover: true
doco-cd would deploy 2 stacks to the docker host:
A new syntax has been added to the env_files deploy setting.
If repository_url is set to deploy from a different repo, you can use the remote:<filepath> syntax to specify, that the dotenv file is located in the remote repository and should be loaded from there. Entries/Keys, that appear in multiple files, get overwritten by the next occurrence and remote dotenv files have higher priority than local ones.
See the wiki for more information: https://github.com/kimdre/doco-cd/wiki/Deploy-Settings#from-remote-repository
For example:
# base.env
TEST=base
HELLO=world
# test.env in remote repository
TEST=changed
repository_url: <url to repo>
env_files:
- base.env
- remote:test.env
Would result in
TEST=changed
HELLO=world
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.49.0...v0.50.0
<!-- Release notes generated using configuration in .github/release.yml at feat/autodiscover -->
<!-- Release notes generated using configuration in .github/release.yml at feat/autodiscover -->
This adds a new auto_discover boolean option to the deploy config. If set to true, doco-cd will try to autodiscover projects/stacks to deploy by searching for docker-compose.y(a)ml or compose.y(a)ml files in subdirectories in the working directory (working_dir). Doco-cd will internally generate new deploy configs based on the directory name and inherits all other settings from the base deploy config inside the .doco-cd.yml file or inline deployment config in poll configs.
When a app is no longer available in the working_dir (e.g. deleted or moved to another directory outside the working dir), doco-cd will automatically remove the deployed project/stack from the docker host.
Available settings:
auto_discover: (bool) true # enables autodiscovery of services to deploy in the working directory by checking for subdirectories with docker-compose files
auto_discover_opts: # options for the autodiscovery feature
depth: (int) 0 # maximum depth of subdirectories to scan for docker-compose files, set to 0 for no limit
delete: (bool) true # auto-remove obsolete auto-discovered deployments that are no longer present in the repository
For example with a structure like this
.doco-cd.yml
apps/
wordpress/
docker-compose.yml
.env
nginx/
docker-compose.yaml
configs/
nginx.conf
misc/
image.png
and a .doco-cd.yml with the following content:
working_dir: apps/
auto_discover: true
doco-cd would deploy 2 stacks to the docker host:
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.50.0-rc.1...v0.50.0-rc.2
<!-- Release notes generated using configuration in .github/release.yml at feat/autodiscover -->
<!-- Release notes generated using configuration in .github/release.yml at feat/autodiscover -->
This adds a new auto_discover boolean option to the deploy config. If set to true, doco-cd will try to autodiscover projects/stacks to deploy by searching for docker-compose.y(a)ml or compose.y(a)ml files in subdirectories in the working directory (working_dir). Doco-cd will internally generate new deploy configs based on the directory name and inherits all other settings from the base deploy config inside the .doco-cd.yml file (or inline deployment config).
When a app is no longer available in the working_dir (e.g. deleted or moved to another directory outside the working dir), doco-cd will automatically remove the deployed project/stack from the docker host.
For example with a structure like this
.doco-cd.yml
apps/
wordpress/
docker-compose.yml
.env
nginx/
docker-compose.yaml
configs/
nginx.conf
misc/
image.png
and a .doco-cd.yml with the following content:
working_dir: apps/
auto_discover: true
doco-cd would deploy 2 stacks to the docker host:
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.49.0...v0.50.0-rc.1
Nothing published for this version
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 -->
Added OpenBao as a new external secret provider. See the wiki for more info: https://github.com/kimdre/doco-cd/wiki/External-Secrets#openbao
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.48.0...v0.49.0
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 -->
Polling configurations (POLL_CONFIG or POLL_CONFIG_FILE) now support defining deployments in-line without requiring a .doco-cd.yml file inside the target repository. Add a deployments list to each poll job to describe the stacks doco-CD should manage:
- url: https://github.com/example/app.git
reference: refs/heads/main
interval: 300
deployments:
- name: example-app
working_dir: services/app
compose_files:
- compose.yaml
env_files:
- .env.production
Inline deployments reuse the same fields as .doco-cd.yml files, including support for external secrets and destroy workflows. The poll job url is always used as the deployment source.
If the poll config has an inline deploy config and the target repository also contains a .doco-cd.yml file, the file will be ignored in favor of the inline deploy config.
See also the wiki about this feature: https://github.com/kimdre/doco-cd/wiki/Poll-Settings#inline-deploy-configs
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.47.0...v0.48.0
Nothing published for this version
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 -->
Adds a new env_files deploy setting to doco-cd that allows you to specify dotenv files for variable interpolation.
Subsequent .env files overwrite each other.
If env_files is unset, the default value env_files: [".env"] will be used; If the default .env file does not exist, it will be ignored. This reflects the defaults of the docker compose specification.
For example
# base.env
NAME=test
STAGE=dev
# prod.env
STAGE=prod
# .doco-cd.yml
name: test
env_files:
- base.env
- prod.env
# docker-compose.yml
services:
test:
labels:
- stage=$STAGE
- name=$NAME
Will result in
# docker-compose.yml
services:
test:
labels:
- stage="prod"
- name="test"
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.46.0...v0.47.0
<!-- Release notes generated using configuration in .github/release.yml at feat/735-specify-env-files-for-variable-interpolation -->
<!-- Release notes generated using configuration in .github/release.yml at feat/735-specify-env-files-for-variable-interpolation -->
Adds a new env_files deploy setting to doco-cd that allows you to specify specify dotenv files for variable interpolation.
Subsequent .env files overwrite each other.
If env_files is unset, the default value env_files: [".env"] will be used; If the default .env file does not exist, it will be ignored. This reflects the defaults of the docker compose specification.
For example
# base.env
NAME=test
STAGE=dev
# prod.env
STAGE=prod
# .doco-cd.yml
name: test
env_files:
- base.env
- prod.env
# docker-compose.yml
services:
test:
labels:
- stage=$STAGE
- name=$NAME
Will result in
# docker-compose.yml
services:
test:
labels:
- stage="prod"
- name="test"
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.46.0...v0.47.0-rc.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 features a new run_once setting for poll configs that allows you to run a poll job only once to initialize a deployment. See the wiki for more info: https://github.com/kimdre/doco-cd/wiki/Poll-Settings
Also doco-cd now supports bind mounts also in Docker Swarm mode!
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.45.0...v0.46.0
<!-- Release notes generated using configuration in .github/release.yml at fix/730-swarm-bind-mounts -->
<!-- Release notes generated using configuration in .github/release.yml at fix/730-swarm-bind-mounts -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.45.0...v0.46.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 new API endpoints to manage Swarm stacks.
See the wiki for the new endpoints: https://github.com/kimdre/doco-cd/wiki/Endpoints#swarm-stacks
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.44.0...v0.45.0
One column per month.