v1.16.4

Changelog

• e1b639a ci: fix: goreleaser config

What's Changed

• docs: update quickstart to include messy output example by @Lewiscowles1986 in #851
• [#854] config: fix: BasePath config is not working by @yottahmd in #860
• docs: note block in execute the DAG of QuickStart by @Lewiscowles1986 in #862
• [#861] test: add: integration test for logDir configuration by @yottahmd in #864

New Contributors

• @Lewiscowles1986 made their first contribution in #851

Full Changelog: v1.16.3...v1.16.4

v1.16.3

Changelog

• ec38f7e [#840] config: fix: Add dagsDir config key (#850)

What's Changed

• doc(executor/docker): add doc about working with env by @vnghia in #836
• doc: Add Github sponser button by @arky in #839
• doc: Update code of conduct by @arky in #843
• doc: improve contribution guide, add commit standards by @arky in #844
• [#846] Fix: issue in calling sub-DAG by @yohamta in #848
• [#847] fix: digraph: overload multiple dotenv files by @yohamta in #849
• [#840] config: fix: Add dagsDir config key by @yohamta in #850

New Contributors

• @vnghia made their first contribution in #836

Full Changelog: v1.16.2...v1.16.3

v1.16.2

Changelog

• 2810502 [#830] executor/docker: support network configuration (#835)

What's Changed

• system version fix by @dayne in #829
• [#827] executor/docker: Fix: command arguments are not evaluated by @yohamta in #832
• [#831] cmd: fix: --config parameter handling by @yohamta in #834
• [#830] executor/docker: support network configuration by @yohamta in #835

New Contributors

• @dayne made their first contribution in #829
• @dependabot made their first contribution in #833

Full Changelog: v1.16.1...v1.16.2

v1.16.1

Changelog

• 6cd013e [#821] Support Snapcraft distribution (#824)

Summary

• Bugfixes (#796 #799 #810)
• Support /health endpoint
• Support headless mode
• Enhance YAML Editor with field completion and schema validation

What's Changed

• support for headless mode as mentioned in #800 by @kriyanshii in #805
• chore: Update docker examples (Fixes #638) by @arky in #818
• chore: Email attachment testcase (Fixes #812) by @arky in #814
• [#820] Add /health endpoint for health check by @yohamta in #823
• digraph: update node.go by @eltociear in #788

New Contributors

• @eltociear made their first contribution in #788
• @kennethpjdyer made their first contribution in #791
• @arky made their first contribution in #808
• @vhespanha made their first contribution in #659

Full Changelog: v1.16.0...v1.16.1

v1.16.0

Changelog

https://dagu.readthedocs.io/en/latest/changelog.html#v1-16-0-2025-01-09

Full Changelog: v1.15.1...v1.16.0

v1.15.1

Changelog

• 5af66f1 [#736] add TLS skip verification option for remote node (#739)

What's Changed

• [#736] add TLS skip verification option for remote node by @yohamta in #739

Full Changelog: v1.15.0...v1.15.1

v1.15.0

What's Changed

• [#709] feat: Add skipIfSuccessful by @yohamta in #712
• fix: incorrect paths in config docs by @jonnochoo in #713
• feat: Support configurable base path for server by @chrishoage in #714
• docs: added docs for CRON_TZ by @jonnochoo in #716
• Improve Dockerfile to reduce amount of config needed in docker-compose by @chrishoage in #723
• chore: add support for devcontainers by @jonnochoo in #728
• add support for default page by @jonnochoo in #729
• [#730] Add Remote-Node support by @yohamta in #731
• [#732] Upgrade to Go 1.23 and Golanci-lint 1.62 by @yohamta in #733

New Features

Remote Node support

Dagu now supports managing multiple Dagu servers from a single UI through its remote node feature. This allows you to:

• Monitor and manage DAGs across different environments (dev, staging, prod)
• Access multiple Dagu instances from a centralized UI
• Switch between nodes easily through the UI dropdown
• See Remote Node Configuration for more details.

Configuration:
Remote nodes can be configured by creating admin.yaml in $HOME/.config/dagu/:

# admin.yaml
remoteNodes:
    - name: "prod" # Name of the remote node
      apiBaseUrl: "https://prod.example.com/api/v1" # Base URL of the remote node API
    - name: "staging"
      apiBaseUrl: "https://staging.example.com/api/v1"

Timezone config in schedule

You can specify a cron expression to run within a specific timezone.

schedule: "CRON_TZ=Asia/Tokyo 5 9 * * *" # Run at 09:05 in Tokyo
steps:
  - name: scheduled job
    command: job.sh

skipIfSuccessful

skipIfSuccessful. When set to true, Dagu will automatically check the last successful run time against the defined schedule. If the DAG has already run successfully since the last scheduled time, the current run will be skipped.

schedule: "0 */4 * * *"   # Run every 4 hours
skipIfSuccessful: true    # Skip if already succeeded since last schedule (e.g., manually triggered)
steps:
  - name: resource-intensive-job
    command: process_data.sh

New Contributors

• @chrishoage made their first contribution in #714

Full Changelog: v1.14.8...v1.15.0

v1.14.8

What's Changed

• fixed bug when using the CRON_TZ= cron expression by @jonnochoo in #707

Full Changelog: v1.14.7...v1.14.8

v1.14.7

What's Changed

• chore: update the Dockerfile & docs by @yohamta in #699
• ui: Add Page Limit Input and Improve Case-Insensitive DAG Search by @yohamta in #702
• ui: Reimplement Timeline Chart and Adjust Server Timezone Handling by @yohamta in #704

Full Changelog: v1.14.6...v1.14.7

v1.14.6

What's Changed

• docs: Add docs for special envs by @yohamta in #689
• docs: Add command to run server in docker compose file by @KMe72 in #693
• fix: use the server timezone to parse the cron expression by @jonnochoo in #696
• docs: add documentation for the time zone configurations by @yohamta in #698
• add: new environment config key DAGU_TZ for server & scheduler's time zone setting

New Contributors

• @KMe72 made their first contribution in #693
• @jonnochoo made their first contribution in #696

Full Changelog: v1.14.5...v1.14.6