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/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
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 -->
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
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
On 18.06.2024, over 2 years ago, I started this project. In that time, it has gained more popularity than I could have ever imagined. Thank you so much for using my tool, for all the support, and of course for the donations! :heart: :partying_face:
This release brings support for specifying Docker contexts in deployment configurations using the new context option. This allows you to use a single doco-cd instance to simultaneously manage and deploy to different or multiple Docker hosts. See the wiki: https://doco.cd/latest/Advanced/Docker-Contexts/
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.99.1...v0.100.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.99.0...v0.99.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
ignore_tlog option to the OCI Trust Policy config to skip Rekor transparency log verification.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.98.0...v0.99.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 -->
cd.doco.deployment.config.target to prevent multiple doco-cd instances to interfere with each other when auto-deployment is used.doco-cd/deploy: <error message>doco-cd/<stack>: <message>doco-cd/<target>/<stack>: <message>Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.97.0...v0.98.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 -->
SCHEDULER_ENABLED option to disable the built-in job scheduler. Useful if you run multiple doco-cd instances, e.g. for self-updating doco-cd.wait=false canceled the job as soon as the response was sent.poll/run endpoint when wait=false by @kimdre in https://github.com/kimdre/doco-cd/pull/1522Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.96.0...v0.97.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 -->
SCHEDULER_ENABLED option to disable the built-in job scheduler. Useful if you run multiple doco-cd instances, e.g. for self-updating doco-cd.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.96.0...v0.97.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 -->
Bind mounts on containers deployed from OCI artifacts should no longer lose their destination inode at OCI artifact sync.
Doco-CD can now post a commit status back to the source Git/SCM provider after each deployment, making the result visible directly on the commit or pull request in their web UI. See the wiki for information on how to enable Commit Status Reporting.
<img width="315" height="162" alt="image" src="https://github.com/user-attachments/assets/0a912caa-9a48-4b7b-ba07-c1ece9c8746d" />
<img width="689" height="150" alt="image" src="https://github.com/user-attachments/assets/eb64d870-e84e-405d-b8b5-358dd19a994e" />
<img width="689" height="150" alt="image" src="https://github.com/user-attachments/assets/c7ea2a59-d545-4b78-948b-e505d2ac51e7" />
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.95.0...v0.96.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.96.0-rc.1...v0.96.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 -->
Bind mounts on containers deployed from OCI artifacts should no longer lose their destination inode at OCI artifact sync.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.95.0...v0.96.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 -->
Back from vacation. This release exposes the default http and metrics ports in the container image and fixes issues with some dependencies:
fails to decrypt dotenv+age files: "Error getting data key: 0 successful groups required, got 0pre_start lifecycle hookFull Changelog: https://github.com/kimdre/doco-cd/compare/v0.94.0...v0.95.0
<!-- 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 custom targets to deploy from OCI artifacts.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.93.1...v0.94.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.93.0...v0.93.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Added the DATA_MOUNT_PATH environment variable to set the container path of the writable deployment data mount (set this if the the data volume is not mounted at /data), see also https://github.com/kimdre/doco-cd/issues/1441.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.92.1...v0.93.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Some improvements for the volume recreation introduced in v0.92.0.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.92.0...v0.92.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
tmpfs, nfs and cifs volumes to be recreated when their config changes.For example the config change below will trigger doco-cd to
services:
app:
image: nginx
volumes:
- tmp:/tmp
volumes:
tmp:
driver: local
driver_opts:
type: tmpfs
device: tmpfs
- o: size=50m
+ o: size=100m
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.91.0...v0.92.0
<!-- Release notes generated using configuration in .github/release.yml at feat/recreate-volume -->
<!-- Release notes generated using configuration in .github/release.yml at feat/recreate-volume -->
Added support for tmpfs, nfs and cifs volumes to be recreated when their config changes.
For example the config change below will trigger doco-cd to
services:
app:
image: nginx
volumes:
- tmp:/tmp
volumes:
tmp:
driver: local
driver_opts:
type: tmpfs
device: tmpfs
- o: size=50m
+ o: size=100m
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.91.0...v0.92.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 adds support for submodules with relative remote urls.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.90.1...v0.91.0
<!-- Release notes generated using configuration in .github/release.yml at fix/1412-relative-submodules -->
<!-- Release notes generated using configuration in .github/release.yml at fix/1412-relative-submodules -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.90.1...v0.91.0
This release fixes the vulnerability by enforcing a strict trust boundary and no-downgrade behavior:
<!-- Release notes generated using configuration in .github/release.yml at main -->
When global OCI signature verification was enabled via OCI_TRUST_POLICY (enabled: true), an attacker with write access to the configured OCI tag could publish an unsigned or improperly signed artifact containing .doco-cd.yml with oci.verify: false. This could cause signature verification to be bypassed and untrusted deployment content to be applied.
This primarily impacts users deploying from OCI artifacts where deployment config is read from artifact contents (for example, poll/webhook flows without trusted inline deployment overrides).
This release fixes the vulnerability by enforcing a strict trust boundary and no-downgrade behavior:
.doco-cd.yml is treated as untrusted for OCI trust-policy override decisions.OCI_TRUST_POLICY.enabled is true, per-deployment oci.verify: false cannot disable verification.Thanks to @strayer for finding and reporting the vulnerability! :heart:
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.90.0...v0.90.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
The API endpoint /v1/api/jobs now includes a status field that reports the Docker container state.
For example:
running job is currently runningexited (0) job ran successfuly and exited with status code 0exited (1) job failed and exited with status code 1Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.89.2...v0.90.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
Fixed an issue where in some cases the deployment concurrency was not working.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.89.1...v0.89.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 -->
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.89.0...v0.89.1
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
60), numeric strings ("60") and Go duration strings ("60s" or "1m").
Intervals are now always shown in the logs as Go durations..doco-cd.yml) are now always required.wait_running_jobs deployment configuration option and label to let doco-cd wait for running jobs before running a deployment to prevent long-running jobs from being interrupted.[!NOTE] The auto-discovery config is stored as a container label. This is neccesarry so that doco-cd is able to know how to clean up obsolete/removed stacks. When upgrading your doco-cd instance, all containers will be recreated once to hold the correct auto-discovered stack configuration.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.88.0...v0.89.0
<!-- Release notes generated using configuration in .github/release.yml at main -->
<!-- Release notes generated using configuration in .github/release.yml at main -->
wait_running_jobs deployment configuration option and label to let doco-cd wait for running jobs before running a deployment to prevent long-running jobs from being interrupted.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.89.0-rc.2...v0.89.0-rc.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 -->
.doco-cd.yml) are now always required.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.89.0-rc.1...v0.89.0-rc.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 -->
60), numeric strings ("60") and Go duration strings ("60s" or "1m").
Intervals are now always shown in the logs as Go durations.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.88.0...v0.89.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 -->
one_shotThe job scheduler execution mode one_shot has been renamed from to one_off for consistency.
The old value is still accepted for backward compatibility but will log a warning and be removed in a future release.
Github Apps are now properly supported, more info in the documentation.
one_shot to one_off for consistency by @kimdre in https://github.com/kimdre/doco-cd/pull/1336Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.87.0...v0.88.0
<!-- 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 jobs to always be scheduled with UTC timezone instead of the local/set timezone.
This release also adds two new API endpoints to list and trigger scheduled jobs (introduced in v0.86.0), see also the REST API documentation.
| Endpoint | Method | Description | Query Parameters |
|---|---|---|---|
/v1/api/jobs |
GET | List all discovered scheduled jobs. | - stack (string, optional): Return scheduled jobs only for one stack/project. |
/v1/api/job/{jobName}/run |
POST | Trigger a configured scheduled job immediately. | - stack (string, optional): Limit matching to a specific stack/project.<br/>- wait (boolean, default: true): Wait for the triggered run to finish before responding. |
What is the jobName for a scheduled job?
jobName is the runtime name of the scheduled target:
my-stack-backup-1)my-stack_backup)How do I find the jobName for a scheduled job?
You can get the jobName from the scheduler logs ("job":"...") or from GET /v1/api/jobs.
jobName, provide stack to disambiguate for the run endpoint.Common run endpoint outcomes
200 OK: run triggered and completed (wait=true).202 Accepted: run accepted and running in background (wait=false).404 Not Found: no scheduled job matched jobName (and optional stack).409 Conflict: matched job is disabled or the selection is ambiguous.curl --request POST \
--url 'https://cd.example.com/v1/api/job/my-stack-backup-1/run?wait=true' \
--header 'x-api-key: your-api-key'
curl --request POST \
--url 'https://cd.example.com/v1/api/job/backup/run?stack=my-stack&wait=true' \
--header 'x-api-key: your-api-key'
curl --request GET \
--url 'https://cd.example.com/v1/api/jobs?stack=my-stack' \
--header 'x-api-key: your-api-key'
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.86.0...v0.87.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 adds a job scheduler that allows you to run containers/services defined in your docker compose files as scheduled jobs based on cron-like schedules or predefined intervals. This is useful for running periodic tasks such as backups, maintenance scripts, or any recurring workloads without needing an external scheduler.
More details in the documentation.
You can now specify domain-scoped Git auth credentials to allow Git operations (clone/fetch) for multiple SCMs/domains. If no domains match or domain-scoped authentication is not configured, the GIT_ACCESS_TOKEN / SSH_PRIVATE_KEY values are used.
The domain-scoped authentication configuration is a YAML list where each entry defines credentials for one or more domains. Each entry in the list has the following structure:
- domains: # (Required) List of domain names or patterns
- domain1.com
- domain2.com
- '*.example.com'
git_access_token: xxx # (Optional) HTTP token for git access
ssh_private_key: | # (Optional) SSH private key content
-----BEGIN OPENSSH PRIVATE KEY-----
...
-----END OPENSSH PRIVATE KEY-----
ssh_private_key_passphrase: xxx # (Optional) Passphrase for encrypted SSH key
More details in the documentation.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.85.1...v0.86.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 pre-release adds a feature that allows you to run containers/services defined in your docker compose files as scheduled jobs based on cron-like schedules or predefined intervals. This is useful for running periodic tasks such as backups, maintenance scripts, or any recurring workloads without needing an external scheduler.
More details in the next version docs: https://doco.cd/next/Advanced/Scheduled-Jobs/
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.85.1...v0.86.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.85.0...v0.85.1
By renaming the auto_discovery deploy setting, I also changed their Container labels. The old labels are deprecated but still supported to prevent unn…
<!-- Release notes generated using configuration in .github/release.yml at main -->
You can now add additional, nested deployment configurations when use the auto-discovery feature to override the base-deployment configuration for a specifc project/stack. For more info see the documentation for Nested config overrides.
This Release introduces a configuration schema cleanup in the deployment settings for consistency with other settings, adds flexible shorthand syntax, and updates auto-discovery label handling in Docker Container.
[!IMPORTANT] You need to change the following values:
- Replace the following in your
.doco-cd.ymlfiles:
auto_discoverandauto_discover_opts->auto_discovery(merged together to one object)destroyanddestroy_opts->destroy(merged together to one object)build_opts->build(Renamed)- Consider recreating containers that use the legacy
cd.doco.deployment.auto_discoverDocker label to migrate tocd.doco.deployment.auto_discoveryin the next convenient moment.
auto_discover and auto_discover_opts are replaced by a single auto_discovery object:
auto_discovery.enabledauto_discovery.depthauto_discovery.deletedestroy (boolean) and destroy_opts are replaced by a single destroy object:
destroy.enableddestroy.remove_volumesdestroy.remove_imagesdestroy.remove_dirbuild_opts has been renamed to build:
build:
force_image_pull: true
no_cache: true
args:
MY_ARG: value
auto_discovery, destroy, and reconciliation now accept either a boolean or a full object, enabling a concise shorthand:
# Shorthand (uses default options)
auto_discovery: true
destroy: true
reconciliation: false
# Full object (for customization)
auto_discovery:
enabled: true
depth: 2
delete: false
By renaming the auto_discovery deploy setting, I also changed their Container labels. The old labels are deprecated but still supported to prevent unnecessary redeployments/container recreations:
cd.doco.deployment.auto_discovery and cd.doco.deployment.auto_discovery.deleteauto_discover labels are still read as a fallback for existing containers, and a deprecation warning is logged, prompting migration.Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.84.0...v0.85.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 was a lot of work. Thank you to everyone who provided contributions and tested the changes! :)
The reconciliation logic has been completely rewritten and now triggers on events from the Docker daemon (like a removed service or unhealthy container) to start the reconciliation process instead of checking on an interval if reconciliation is needed. Configuration options and further information can be found in the documentation.
Doco-CD now fetches image digests from container registries using HEAD requests to avoid rate limits with a fallback to the previous GET request logic.
This is useful for registries like DockerHub, where all GET requests against the registry count as an image pull, even if they don't download any image layers.
This release adds support for using a 1Password Connect Server as a external secrets provider.
A 1Password Connect server is a self-hosted proxy that caches vault data locally and serves secrets over a simple HTTP API. This is useful when you are deploying frequently or have multiple instances that would otherwise hit 1Password API rate limits.
See the docs for setup and usage: https://doco.cd/latest/External-Secrets/1Password-Connect/
[!TIP] For 1Password Users For improved performance and to avoid API rate limits in high-volume deployments, consider using 1Password Connect instead of service account authentication (The 1Password provider).
The 1Password provider now supports client-side caching to reduce API calls to the 1Password cloud.
Enable and configure caching with the following environment variables:
| Key | Value | Default |
|---|---|---|
SECRET_PROVIDER_CACHE_ENABLED |
Enables in-memory caching for resolved secrets | false |
SECRET_PROVIDER_CACHE_TTL |
Cache TTL for resolved secrets as a Go duration string (for example: 30s, 5m, 1h) |
5m |
SECRET_PROVIDER_CACHE_MAX_SIZE |
Maximum number of secrets stored in cache before least-recently-used entries are evicted | 100 |
[!WARNING] If the cache TTL is too long, secrets may become outdated.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.83.0...v0.84.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 two new major improvements:
The reconciliation logic has been completely rewritten and now triggers on events from the Docker daemon (like a removed service or unhealthy container) to start the reconciliation process instead of checking on an interval if reconciliation is needed. Configuration options and further information can be found in the documentation.
Doco-CD now fetches image digests from container registries using HEAD requests to avoid rate limits with a fallback to the previous GET request logic.
This is useful for registries like DockerHub, where all GET requests against the registry count as an image pull, even if they don't download any image layers.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.84.0-rc.2...v0.84.0-rc.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 -->
This Pre-release adds support for using a 1Password Connect Server as a external secrets provider.
A 1Password Connect server is a self-hosted proxy that caches vault data locally and serves secrets over a simple HTTP API. This is useful when you are deploying frequently or have multiple instances that would otherwise hit 1Password API rate limits.
See the next version docs for setup and usage: https://doco.cd/next/External-Secrets/1Password-Connect/
[!TIP] For 1Password Users For improved performance and to avoid API rate limits in high-volume deployments, consider using 1Password Connect Server instead of service account authentication (The previous 1Password provider).
The optional Client-Side Caching has a new configuration option SECRET_PROVIDER_CACHE_MAX_SIZE to set the maximum number of secrets stored in cache before least-recently-used entries are evicted (default: 100)
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.84.0-rc.1...v0.84.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 optional client-side caching to reduce 1Password API calls. See also in the docs.
Enable and configure caching with the following environment variables:
| Key | Value | Default |
|---|---|---|
SECRET_PROVIDER_CACHE_ENABLED |
Enables in-memory caching for resolved secrets | false |
SECRET_PROVIDER_CACHE_TTL |
Cache TTL for resolved secrets as a Go duration string (for example: 30s, 5m, 1h) |
5m |
[!WARNING] If the cache TTL is too long, secrets may become outdated.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.83.0...v0.84.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.82.2...v0.83.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.82.2...v0.83.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 -->
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.
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.
Full Changelog: https://github.com/kimdre/doco-cd/compare/v0.82.1...v0.82.2
Nothing published for this version
One column per month.