github flohoss/gocron v0.9.12
Release v0.9.12

3 hours ago

Breaking Changes

The --config flag now expects a path to the actual YAML config file, not a config folder. For example, use /path/to/config.yaml instead of /path/to/config or ./config.
Existing setups that relied on the old config-folder flag behavior must update their startup arguments before upgrading.

The SQLite configuration is now defined under a dedicated db section. Database directory is configured with db.location, and database file name is configured with db.name.

Job detail routes now use generated URL-safe slugs instead of raw job names. Slugs are derived automatically from the configured job name and must be unique.

Migration

Update your startup command to point --config directly to the config file.
Move any SQLite path customization into the db section.
To keep the previous default behavior, set db.location to . (the same folder as the config file) and leave db.name as db.sqlite.
Ensure job names produce unique slugs if you use the web UI, since duplicate slugs are now rejected during config loading.

Changes in This Release

Full Changelog: v0.9.11...v0.9.12


Docker Image

docker pull ghcr.io/flohoss/gocron:v0.9.12
docker pull ghcr.io/flohoss/gocron:latest

Binary Downloads

Download one of the attached binaries extracted from the release image:

  • gocron_<version>_linux_amd64
  • gocron_<version>_linux_arm64

Verify with ./gocron_<version>_linux_<arch> --version.

Image digest:

ghcr.io/flohoss/gocron:v0.9.12@sha256:914f81c74d05623f94d70c021f6c8a8aac94d6f91f3cb3005289c3ff920d61f3

Build Information

  • Version: v0.9.12
  • Build Time: 2026-05-11T04:39:31Z
  • Repository: https://github.com/flohoss/gocron
  • Platform: linux/amd64,linux/arm64
  • Attestations: SLSA Provenance, SBOM

Don't miss a new gocron release

NewReleases is sending notifications on new releases.