This release is same as v1.23.3 which I accidentally dropped.

Added

• CLI: Added --name flag to start, retry, and enqueue commands to override the DAG name specified in the YAML file (#1363)
• DAG: Support shell-like parameter expansion for env and parameters fields, including ${VAR:offset:length} slices and shell-style defaults (${VAR:-fallback}) (#1354)
• Distributed: Added comprehensive Kubernetes deployment manifests with ConfigMaps, PVCs, and separate server/worker deployments (#1360)
• Distributed: Added automatic cleanup of stale coordinator service registrations (#1360)
• Distributed: Added retry mechanism with exponential backoff for coordinator client connections (#1360)

Improved

• Distributed: Enhanced distributed execution with better worker coordination and status propagation (#1360)
• Distributed: Improved child DAG status propagation in distributed mode to correctly report final status to parent workflows (#1358)
• OIDC: Improved OIDC configuration validation with better error messages and logging (#1361)
• OIDC: Enhanced OIDC authentication flow with proper state management and error handling (#1361)
• API: Better error handling in API endpoints with more descriptive error messages (#1361)

Fixed

• Distributed: Fixed child DAG status not being properly propagated to parent in distributed execution (#1358)
• Distributed: Fixed parallel execution status tracking for sub-DAGs (#1358)
• Distributed: Fixed service registry cleanup and stale entry detection (#1360)

Contributors

Thanks to our contributors for this release:

Full Changelog: v1.23.2...v1.23.4

This is a hotfix for v1.23.0..

Changelog

• 98d795b fix: the server should set same environment variable to start a subprocess (#1351)

What's Changed

• fix: the server should set same environment variable to start a subprocess by @yottahmd in #1351

Full Changelog: v1.23.0...v1.23.2

This release introduces several enhancements, including a GitHub Actions executor (which allows you to run GitHub Actions in your DAG locally!), JSON Schema validation for parameters, secrets support, improved Windows compatibility, an upgraded Web UI, and many bug fixes.

Here's an example of cloning a repository using actions/checkout GitHub Actions:

workingDIr: /tmp/dagu-workdir

secrets:
  - name: GITHUB_TOKEN
    provider: env
    key: GITHUB_TOKEN

steps:
  - name: checkout
    command: actions/checkout@v4
    executor: gha
    params:
      repository: dagu-org/dagu
      ref: main
      token: "${GITHUB_TOKEN}"

We welcome feedback, issues, and contributions for this new version.

Changed

• Status: Adopted canonical lowercase tokens for DAG and node lifecycle states (not_started, queued, running, succeeded, partially_succeeded, failed, canceled), and updated API examples, docs, and telemetry labels to match.
• Status: Updated the Sub-DAG execution field to support call field alias.

Added

• CLI: Added --dagu-home global flag to override the application home directory on a per-command basis. Useful for testing, running multiple instances with isolated data, and CI/CD scenarios.
• CLI: Added dagu validate command to validate DAG specifications without executing them. Prints human‑readable errors and exits with code 1 on failure.
• API: Added POST /api/v2/dags/validate to validate DAG YAML. Returns { valid: boolean, errors: string[], dag?: DAGDetails }.
• API: POST /api/v2/dags now accepts optional spec to initialize a DAG. The spec is validated before creation and returns 400 on invalid input.
• API: Added POST /api/v2/dag-runs to create and start a DAG-run directly from an inline YAML spec without persisting a DAG file. Supports optional name, params, dagRunId, and singleton.
• API: Added nextRun sort option to GET /api/v2/dags to sort DAGs by their next scheduled run time. DAGs with earlier next runs appear first in ascending order, and DAGs without schedules appear last.
• Steps: Add support for shebang detection in script.
• Steps: Multi-line command strings now execute as inline scripts, including support for shebang.
• DAG: Introduced a secrets block that references external providers (built-in env and file) and resolves values at runtime with automatic log/output masking.
• Parameters: Added JSON Schema validation mode with schema.
• Runtime: Injects DAG_RUN_STATUS into handler environments so exit/success/failure/cancel scripts can branch on the final canonical status.
• Executors: Added an experimental GitHub Actions executor (type: gha) powered by nektos/act; action inputs come from the new step-level params map.
• UI: Added accordion-style expandable node rows to display step logs inline, similar to GitHub Actions, reducing the need to open popup windows (#1313).
• Security: Implemented security filtering for system environment variables passed to step processes and child DAGs.

Fixed

• DAG name validation is centralized and enforced consistently: names must be <= 40 chars and match [A-Za-z0-9_.-]+. Endpoints that accept name now return 400 bad_request for invalid names.
• Docker: Fixed container initialization bug with registryAuths field (#1330)
• Windows: Fixed process cancellation not terminating subprocesses by recursively killing all child processes (#1342)
• UI: Fixed duration display update bug in DAG run details
• Other small issues and improvements

Contributors

Thanks to our contributors for this release:

New Contributors

• @AdityaTel89 made their first contribution in #1308
• @lvoeg made their first contribution in #1342

Full Changelog: v1.22.4...v1.23.0

This release includes a new UI feature to clear the queue, an API enhancement that supports using latest as a Run ID, a UI fix improving grouped DAG visibility on mobile, and several bug fixes in the DAG execution engine. Many thanks to @kriyanshii for the contribution and to everyone who reported issues.

Added

• UI: add clear queue functionality #1298 (#1299) by @kriyanshii
• API: add support for latest in GET /api/v2/dag-runs/{name}/{dagRunId} (#1300)

Fixed

• UI: display grouped DAGs (#1295)
• DAG: treat single JSON object as a parallel item (#1297)
• DAG: initialize node before setting node status running (#1302)

Full Changelog: v1.22.9...v1.22.10

This minor release includes a Web UI enhancement enabling DAGs to be sorted based on the Next Run column, improving UX.

Changelog

• 4ced35c feat: Allow sorting DAGs by NextRun (#1292)

Full Changelog: v1.22.8...v1.22.9

This release addresses an issue in the DAG editor UI where the editing state was being reset on each polling.

Changelog

• d88e3f9 fix(ui): keep editing state while polling (#1290)

Full Changelog: v1.22.7...v1.22.8

This release is same as v1.22.6 except that we've applied a fix for a minor NPM package issue.

Changelog

• 360a988 fix: NPM module exit code handling (#1272)

Full Changelog: v1.22.6...v1.22.7

In this release, we’ve applied several bug fixes to the docker-executor. One important change is that the default maxCleanUpTimeSec has been reduced from 60 seconds to 5 seconds. This means your application has only 5 seconds to exit once it receives a termination signal; otherwise, it will be killed with SIGKILL. If needed, you can modify maxCleanUpTimeSec in the base DAG or on a per-DAG basis.

Changelog

• bb0b125 [#1237] fix: container name is not properly set & container does not stop when a DAG run is cancelled (#1271)

Full Changelog: v1.22.5...v1.22.6

This release includes a patch to fix a minor issue regarding to docker executor.

Changelog

• 4b23493 feat(container): Automatically start a container when container name is specified (#1266)

Full Changelog: v1.22.4...v1.22.5

This release updates the SSH field to support the use of parameters and environment variables in configuration. For more details see the documentation.

Changelog

• be57f3d test(integration): verify containerName-only executor config works (#1248)

What's Changed

• feat: Allow params & environment variables in SSH field by @yottahmd in #1247
• test(integration): verify containerName-only executor config works by @yottahmd in #1248

Full Changelog: v1.22.3...v1.22.4