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 14 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
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
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 -->
This release mainly contains code cleanup and refactoring.
Two small things have been added:
timeout deploy config setting in the wiki.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.114.0...v0.115.0-rc.1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
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 a stateless Model Context Protocol server to allow AI applications/LLMs to communicate directly with doco-cd using provided MCP tools.
Doco-CD exposes the MCP server at POST /mcp using streamable HTTP transport. The endpoint uses the HTTP_PORT and follows doco-cd's TLS configuration.
Enable the server with MCP_ENABLED: true and provide an API secret using API_SECRET or API_SECRET_FILE (see REST API Authentication):
services:
app:
environment:
MCP_ENABLED: "true"
API_SECRET: your-api-key
See the wiki about how to set the correct client configuration for authentication against the MCP server.
If you are using Docker Swarm, you can now configure each deployment, whether doco-cd should deploy as a Compose project or a Swarm stack. Use the new swarm.enabled deploment configuration setting for this.
true deploys a Docker Swarm stack. false deploys a Docker Compose project. When omitted, the Docker context determines the mode (like before). An explicit true fails if the context is not a Swarm manager or DOCKER_SWARM_FEATURES=false.
name: netbird
swarm:
enabled: false
When the value of enabled changes for a doco-cd-managed deployment, doco-cd migrates the project or stack automatically. Its volumes are retained during this migration.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.113.0...v0.114.0
Nothing published for this version
This release adds multi-context support and cleans up deprecated code/features.
<!-- Release notes generated using configuration in .github/release.yml at main -->
This release adds multi-context support and cleans up deprecated code/features.
The one_shot alias for one_off is no longer supported.
Use one_off instead; one_shot values are rejected.
one_shot to one_off in job definitions.Legacy label formats are retired:
cd.doco.deployment.auto_discovercd.doco.deployment.auto_discover.deletecd.doco.deployment.auto_discovery.deleteNew deployments use cd.doco.deployment.auto_discovery and the JSON configuration label cd.doco.deployment.auto_discovery.config.
Existing deployments using legacy auto-discovery labels are migrated automatically:
ENCRYPTED PRIVATE KEYSupport is removed because it relied on the deprecated Go x509.DecryptPEMBlock() API. Use modern OpenSSH or unencrypted PEM key formats.
Docker Compose services are started automatically after they are created or updated. To let an external tool control a service's lifecycle, set the cd.doco.deployment.autostart service label to false.
services:
on-demand:
image: example/on-demand:latest
labels:
cd.doco.deployment.autostart: "false"
The label defaults to true. When it is false:
More info in the wiki: https://doco.cd/latest/Deploy-Settings/#preserve-a-services-running-state
Added multi-context support for Docker contexts to all subsystems of doco-cd:
context label)Project, stack, and scheduled-job endpoints now accept one optional context query parameter. If it is omitted or set to default, the endpoint uses the default Docker context. Named contexts must exist in the Docker CLI context store available to doco-cd. More info in the wiki.
These endpoints return the selected external context name in the X-Doco-CD-Context response header. Their JSON response shapes do not change.
one_shot alias for jobs, deprecated labels, and PKCS#1 SSH support by @kimdre in https://github.com/kimdre/doco-cd/pull/1757Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.112.0...v0.113.0
This pre-release removes three deprecated features that have reached end-of-life.
<!-- Release notes generated using configuration in .github/release.yml at main -->
This pre-release removes three deprecated features that have reached end-of-life.
Job execution mode: the one_shot alias for one_off is no longer supported.
Use one_off instead; one_shot values are rejected.
Auto-discovery labels: legacy label formats are retired:
cd.doco.deployment.auto_discovercd.doco.deployment.auto_discover.deletecd.doco.deployment.auto_discovery.deleteNew deployments use cd.doco.deployment.auto_discovery and the JSON configuration label cd.doco.deployment.auto_discovery.config.
SSH private keys: PKCS#1 ENCRYPTED PRIVATE KEY support is removed because
it relied on the deprecated Go x509.DecryptPEMBlock() API. Use modern OpenSSH
or unencrypted PEM key formats.
Existing deployments using legacy auto-discovery labels are migrated automatically:
one_shot to one_off in job definitions.Docker Compose services are started automatically after they are created or updated. To let an external tool control a service's lifecycle, set the cd.doco.deployment.autostart service label to false.
services:
on-demand:
image: example/on-demand:latest
labels:
cd.doco.deployment.autostart: "false"
The label defaults to true. When it is false:
More info in the wiki: https://doco.cd/next/Deploy-Settings/#preserve-a-services-running-state
one_shot alias for jobs, deprecated labels, and PKCS#1 SSH support by @kimdre in https://github.com/kimdre/doco-cd/pull/1757Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.113.0-rc.1...v0.113.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 pre-release adds multi-context support for Docker contexts to all subsystems of doco-cd:
context label)Project, stack, and scheduled-job endpoints now accept one optional context query parameter. If it is omitted or set to default, the endpoint uses the default Docker context. Named contexts must exist in the Docker CLI context store available to doco-cd. More info in the wiki.
These endpoints return the selected external context name in the X-Doco-CD-Context response header. Their JSON response shapes do not change.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.112.0...v0.113.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 -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.111.0...v0.112.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Some stacks cannot be deployed without a running SCM available (e.g. a self-hosted Gitea/Forgejo instance that should be deployed via doco-cd (hence a chicken-and-egg problem), or a stack that is deployed from a local Git repository that is not hosted on any remote SCM). This release adds support for polling local Git repositories to solve this problem.
Mount the directory containing your local Git repo into the doco-cd container, then use a poll config with the url: value being the absolute path to the Git repo inside the container.
More info in the wiki at Polling Local Filesystem Repositories.
In addition to interval-based polling, doco-cd watches the local repository's git directory for changes and triggers a deployment check immediately when new commits land, without waiting for the next interval. This is enabled by default; set watch: false to disable it and rely on interval only. Set interval: 0 (with watch left enabled) to rely on the watcher exclusively, with no periodic fallback polling at all.
See the watch poll option in the wiki.
.env files (env_files) are now parsed with compose-go's dotenv engine (the same one Docker Compose uses) instead of godotenv. Variables set in one env_files entry are now correctly available for ${VAR} substitution in later entries.
Reference docs:
.env syntax (.env file section): https://docs.docker.com/compose/how-tos/environment-variables/variable-interpolation/#env-fileInterpolation syntax): https://docs.docker.com/reference/compose-file/interpolation/[!WARNING] No longer supported / behavior changes:
- Lowercase/mixed-case
${var}references are no longer left as literal text. Previously,godotenvonly expandedUPPERCASEvariable names and silently ignored${lowercase_var}/${MixedCase}, keeping the literal string in the value. These are now interpolated like any other variable — if unset, they resolve to an empty string instead of the original literal text.If any of your
.envfiles intentionally relied on lowercase${...}placeholders being left untouched, rename them to avoid the$/${}pattern (e.g. escape with\$) or ensure the referenced variable is actually defined.
[!NOTE] New/added support:
- Bash-style default and required-value operators now work inside
.envfiles:${VAR:-default},${VAR-default},${VAR:+alt},${VAR+alt},${VAR:?error},${VAR?error}.- Bare keys (e.g. a line with just
SOME_VAR) now inherit the value from the process environment or an earlierenv_filesentry.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.110.1...v0.111.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 -->
Fixed a bug that caused the job API to not return the last_run_at field anymore.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.110.0...v0.110.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Set the new environment variables HTTP_TLS_CERT_FILE and HTTP_TLS_KEY_FILE to enable HTTPS for the API and metrics server, and healthcheck.
Added automatic OpenBao certificate rotation, see the wiki for more info.
Set these env vars for doco-cd to enable and configure the cert rotation watcher:
CERT_ROTATION_ENABLED=true
CERT_ROTATION_THRESHOLD=72h
CERT_ROTATION_CHECK_INTERVAL=1h
Use pki-role:
external_secrets:
CERT: "pki-role:pki:my-role:app.example.com"
pki-role:certs:myapp-role:myapp.example.com -> Issues a new certificate for the common name myapp.example.com using the myapp-role PKI role in the certs secret engine in the root namespace.pki-role:my-namespace:certs:myapp-role:myapp.example.com -> Same as above but in the my-namespace namespace.pki-role: issues a fresh certificate and matching private key on deploy. When rotation is enabled, doco-cd will watch the deployed cert’s expiry and redeploy the affected service before it expires.
Use CERT for the certificate and CERT_KEY for the private key in your compose file.
See the OpenBao Provider documentation in the PR.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.109.2...v0.110.0
<!-- Release notes generated using configuration in .github/release.yml at feat/1657-secret-rotation -->
<!-- Release notes generated using configuration in .github/release.yml at feat/1657-secret-rotation -->
Added automatic OpenBao certificate rotation
To test the new feature, switch your OpenBao secret reference from pki: to pki-role: and enable the rotation watcher:
external_secrets:
CERT: "pki-role:pki:my-role:app.example.com"
Examples:
pki-role:certs:myapp-role:myapp.example.com -> Issues a new certificate for the common name myapp.example.com using the myapp-role PKI role in the certs secret engine in the root namespace.pki-role:my-namespace:certs:myapp-role:myapp.example.com -> Same as above but in the my-namespace namespace.Then set these env vars for doco-cd:
CERT_ROTATION_ENABLED=true
CERT_ROTATION_THRESHOLD=72h
CERT_ROTATION_CHECK_INTERVAL=1h
pki-role: issues a fresh certificate and matching private key on deploy. When rotation is enabled, doco-cd will watch the deployed cert’s expiry and redeploy the affected service before it expires.
Use CERT for the certificate and CERT_KEY for the private key in your compose file.
See the OpenBao Provider documentation in the PR.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.109.2...v0.110.0
<!-- Release notes generated using configuration in .github/release.yml at feat/1657-secret-rotation -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.109.2...v0.110.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 -->
Added TRUSTED_PROXY_NETWORKS and TRUSTED_PROXY_HEADER env vars to configure trusted proxies for real client ip logging in API logs.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.109.1...v0.109.2
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 -->
A change in release v0.107.0 broke variable interpolation with values in environment in the deployment configuration. This release fixes this.
One-off job containers now also have the default docker compose labels, for example:
com.docker.compose.projectcom.docker.compose.servicecom.docker.compose.project.working_dirFull Changelog: https://github.com/kimdre/doco-cd/compare/v0.109.0...v0.109.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
If a docker config is provided/mounted inside the container, doco-cd will now verify the configuration and throw errors if the config is invalid or requires a credential helper binary, that is not available in $PATH.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.108.0...v0.109.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 -->
This release adds support for including Git repos and OCI artifacts in Docker Compose's include top-level section as described in their documentation:
includeallows you to reference Compose files from remote sources, such as OCI artifacts or Git repositories. Here serviceB is defined in a Compose file stored on Docker Hub.include: - oci://docker.io/username/my-compose-app:latest # use a Compose file stored as an OCI artifact services: serviceA: build: . depends_on: - serviceB
Use the new OCI_INSECURE_REGISTRIES environment variable to set a comma-seperated allowlist of OCI registries to treat as insecure (HTTP or self-signed certs). Entries are deduplicated and normalized to lowercase. Each entry must be a hostname with optional port (no URL schemes allowed).
Example: registry.example:5000,localhost:5000
include: section to a Compose file:include:
- path: https://github.com/user/repo.git#main:docker-compose.yml # use a relative path if the compose file is in a subdirectory: docker/compose.yml
- path: oci://docker.io/namespace/config:latest
GIT_ACCESS_TOKEN or domain-scoped credentials are configured (see wiki).OCI_INSECURE_REGISTRIES.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.107.0...v0.108.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
DATA_HOST_PATH: Optional source path of the deployment data mount as seen by the target Docker daemon (See Remote Docker daemons). Automatically detected by default.[!IMPORTANT] The default value of the
auto_discovery.deleteoption changed tofalse. Users, that want to auto-remove obsolete projects/stacks, need to explicitly setauto_discovery.delete: truein their deployment config now.
[!NOTE]
- The first deployment after upgrading doco-cd will trigger a recreation of all tasks/containers in the stack to set the correct doco-cd metadata.
- The REST API response shape for the Stack endpoints changed
APPRISE_NOTIFY_LEVEL is set to info.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.106.0...v0.107.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 an option to rewrite source URLs for deployments.
SOURCE_URL_REWRITES (and SOURCE_URL_REWRITES_FILE) let you rewrite git source URLs before doco-cd clones them. Rules apply to both webhook- and poll-triggered deployments.
This is useful when your Git provider advertises a public URL (in webhook payloads or poll configs) but doco-cd should clone through an internal network path instead — for example when your Forgejo instance is behind a reverse proxy with a public domain, but is reachable directly over a Docker network.
More info in the wiki:
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.105.2...v0.106.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
This pre-release adds an option to rewrite source URLs in deployments.
SOURCE_URL_REWRITES (and SOURCE_URL_REWRITES_FILE) let you rewrite git source URLs before doco-cd clones them. Rules apply to both webhook- and poll-triggered deployments.
This is useful when your Git provider advertises a public URL (in webhook payloads or poll configs) but doco-cd should clone through an internal network path instead — for example when your Forgejo instance is behind a reverse proxy with a public domain, but is reachable directly over a Docker network.
More info in the wiki:
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.105.2...v0.106.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 -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.105.1...v0.105.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.105.0...v0.105.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 -->
Added new fields for the notification body:
{{ .Duration }} - Time the deployment (or destroy) took, from job start to the notification, e.g. 12.483s. Zero where no deployment ran (reconciliation restarts, scheduled jobs) — hide it with {{if .Duration}}...{{end}}{{ .ChangedServices }} - Sorted names of the services force-recreated by this deploy (changed mounted/referenced files or a changed auto-discovery label). Empty when the whole stack is (re)deployed for other reasons, e.g. a compose config change, an image update, state drift or force_recreate.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.104.0...v0.105.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
cd.doco.job.stop_services allowing jobs to specify a comma-separated list of services (within the same or other projects) to be stopped before the job runs and restarted after completion, see the wiki: Temporarily stop services during a job run..Target: Custom webhook/poll target that was used for the deployment (empty if default target or unused).Commits: Commits deployed since the last deploy (see Notifications/Commit changelog)
Example:environment:
APPRISE_NOTIFY_BODY_TEMPLATE: |
{{ .DefaultBody }}
{{ range .Commits }}- {{ .ShortHash }} {{ .Subject }} ({{ .Author }})
{{ end }}
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.103.0...v0.104.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 -->
.Target as a possible field for the custom notification body for the deployment target .cd.doco.job.stop_services allowing jobs to specify a comma-separated list of services (within the same or other projects) to be stopped before the job runs and restarted after completion, see also Temporarily stop services during a job run.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.103.0...v0.104.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 -->
GIT_ACCESS_TOKEN_USER if you use a global access token and git_access_token_user if you use domain-scoped authentication.APPRISE_NOTIFY_BODY_TEMPLATE and APPRISE_NOTIFY_BODY_TEMPLATE_FILE to allow users to customize the notification message body. See Custom notification body in the wiki.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.102.0...v0.103.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
GIT_SCM_API_URL environment variable to set the correct HTTP url of their SCM instance (see the docs)Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.101.1...v0.102.0
<!-- Release notes generated using configuration in .github/release.yml at fix/docker-context-ssh -->
<!-- Release notes generated using configuration in .github/release.yml at fix/docker-context-ssh -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.101.1...v0.102.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.101.0...v0.101.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
The "deployment in progress" log during deployments now contains a deploy.phase field that shows what doco-cd is doing in the background (e.g. pulling or building images, creating services or waiting for service startup)
{"time":"2026-07-23T11:14:06.550169542+02:00","level":"info","msg":"deployment in progress","deploy":{"job_id":"019f8e40-d48d-7bb9-8832-93a167a5b239","phase":"pulling images","reference":"main","repository":"github.com/kimdre/doco-cd_tests","stack":"test-deploy","stage":"deploy"}}
{"time":"2026-07-23T11:14:11.552029128+02:00","level":"info","msg":"deployment in progress","deploy":{"job_id":"019f8e40-d48d-7bb9-8832-93a167a5b239","phase":"pulling images","reference":"main","repository":"github.com/kimdre/doco-cd_tests","stack":"test-deploy","stage":"deploy"}}
{"time":"2026-07-23T11:14:16.554090422+02:00","level":"info","msg":"deployment in progress","deploy":{"job_id":"019f8e40-d48d-7bb9-8832-93a167a5b239","phase":"waiting for services to start","reference":"main","repository":"github.com/kimdre/doco-cd_tests","stack":"test-deploy","stage":"deploy"}}
Scheduled jobs are no longer executed when their stack is deployed or redeployed (on both Docker Compose and Swarm). They now run only on their configured schedule.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.100.0...v0.101.0
One column per month.