v1.4.1-build.6

Rebuild with go1.26.1

v1.5.0-beta.1

New:
- Add cron format `-at` flag

  Mutually exclusive with `-every`, the `-at` flag receives a cron 5-field
  date time expression to periodically execute the command at date time
  periods.

  Supported expressions:
    - Simple 5-field: * * * * *
    - Lists: 00 02,08,14,20 * * *
    - Ranges: 00 09-17 * * *
    - Steps: */5 1-10/2 * * *
    - Day of Week (Sunday=0 or 7): 15 10 * * 7

  Not yet supported:
    - Randomization with `~`

v1.4.1-build.5

Rebuild with go1.25.6

v1.4.1-build.4

Rebuild with go1.25.5

v1.4.1-build.2

Rebuild with go1.25.4

v1.4.1-build.2

Rebuild with go1.25.1

v1.4.1

Fixes a reintroduced bug that causes pings with empty bodies to be sent
with chunked encoding. While this is not an issue for healthchecks.io
hosted instance, self hosted instances directly exposing the Django's
HTTP server would fail with 411 Length Required response.

Reported and fix co-authored by @inode64

v1.4.0

New:
- Add `file:` prefix support for flag and env var indirection

  Passing secrets via environment variables isn't always safe. This change
  add support for reading values from a file, preferably one residing on a
  non-swappable memory, like systemd-credentials or Docker Compose
  Secrets, that get mounted from hopefully a safer location from the host.

  Example:
    # From the environment variable.
    export PING_KEY=file:/run/secrets/hc_prod_pingkey
    runitor -slug nightly-backup restic backup --files-from manifest

    # From the command line flag.
    # Using systemd-creds(1).
    [Service]
    Type=oneshot
    SetCredentialEncrypted=hc-uuid-upgrades: \
      Whxqht+[........................................................]nvz/E= \
    ExecStart=/usr/bin/runitor \
      -uuid file:%d/hc-uuid-upgrades \
      /usr/local/sbin/unattended-upgrades

    [Unit]
    Description=Unattended Upgrades

- Add PING_KEY environment as preferred alternative to HC_PING_KEY

- Go 1.24

Bug fixes:
- For pings with body (captured by default) retries failed to
  send the body again on the, causing 400 Bad Request errors due
  to mismatched Content-Length header and body size.

  Runitor retries if the remote server returns a status code of 408,
  429, or 50[0234].

  Reported by @yteraoka in #181

v1.4.0-beta.3

- Fixes a bug where ping body was when retrying the request if the prior
  request timed out or had a 5XX response.

v1.4.0-beta

- Fixes a bug where ping body was when retrying the request if the prior
  request timed out or had a 5XX response.