Skip to content

Releases: bdd/runitor

v1.3.0-build.2

31 Aug 06:16
@bdd bdd
8959f10
Compare
Choose a tag to compare

v1.3.0-build.2

Rebuild with go1.23.0

v1.3.0

11 May 05:35
@bdd bdd
v1.3.0
addc2b3
Compare
Choose a tag to compare

v1.3.0

New Features:

v1.2.0-build.2

03 Jan 22:34
@bdd bdd
6ee7f2f
Compare
Choose a tag to compare

v1.2.0-build.2

Rebuild with latest Go to address CVEs found in Go versions prior to 1.19.8.

v1.3.0-beta.2

09 Jul 00:44
@bdd bdd
v1.3.0-beta.2
02fcc95
Compare
Choose a tag to compare
v1.3.0-beta.2 Pre-release
Pre-release

v1.3.0-beta.2

New Features:

v1.3.0-beta.1

26 Jun 22:22
@bdd bdd
5cdce6f
Compare
Choose a tag to compare
v1.3.0-beta.1 Pre-release
Pre-release

v1.3.0-beta.1

New Features:

v1.2.0

03 Dec 18:53
@bdd bdd
v1.2.0
f312186
Compare
Choose a tag to compare

v1.2.0

New Features:

  • Support HTTP 307 and 308 redirects, allowing the POST body to be
    preserved and sent to redirected URL.

    Use case of this is the ability to have a custom and more permanent
    API URL which can be trivially directed to either hc-ping.com or a
    private instance of Healthchecks as described in #79.

v1.2.0-beta.1

02 Dec 01:33
@bdd bdd
v1.2.0-beta.1
f312186
Compare
Choose a tag to compare
v1.2.0-beta.1 Pre-release
Pre-release

v1.2.0-beta.1

New Features:

  • Support HTTP 307 and 308 redirects, allowing the POST body to be
    preserved and sent to redirected URL.

    Use case of this is the ability to have a custom and more permanent
    API URL which can be trivially directed to either hc-ping.com or a
    private instance of Healthchecks as described in #79.

v1.1.1

23 Nov 20:42
@bdd bdd
Compare
Choose a tag to compare

v1.1.1

Bugfix:

  • Fixes #75
  • Retracts Go mod v1.1.0

v1.1.1-rc.1

23 Nov 07:21
@bdd bdd
Compare
Choose a tag to compare
v1.1.1-rc.1 Pre-release
Pre-release

v1.1.1-rc.1

Bugfix:

v1.1.0

21 Nov 22:25
@bdd bdd
v1.1.0
bac4814
Compare
Choose a tag to compare

v1.1.0

New Features:

  • Add Run Id support
    https://blog.healthchecks.io/2022/11/using-run-ids-to-track-run-times-of-overlapping-jobs/
    A UUID-4 (random) run id is generated for every run and sent with
    related pings, unless instructed otherwise with -no-run-id flag.
    .
    For use cases where runitor is in charge of periodically running a
    command (specified with -every <duration>), each run gets its own
    random UUID as expected.
    .
    There is no way for the user to supply the run ids, and I don't intend
    to add such functionality. Furthermore I may consider removing
    -no-run-id flag altogether.

Misc:

  • Require Go 1.19