Skip to content

Releases: go-co-op/gocron

v1.14.0

14 Jun 11:09
f8144d2
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.13.0...v1.14.0

v1.13.0

22 Feb 21:29
b35e4e8
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.12.0...v1.13.0

v1.12.0

08 Feb 15:57
5131f4a
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.11.0...v1.12.0

v1.11.0

07 Dec 03:45
c3be44d
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.10.0...v1.11.0

v1.10.0

29 Nov 15:43
5dd4543
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.9.0...v1.10.0

v1.9.0

13 Sep 21:05
47b19f0
Compare
Choose a tag to compare

Changed

  • stopping the scheduler waits for all jobs to finish before returning (#238) @Streppel

v1.8.0

13 Sep 16:18
971b91f
Compare
Choose a tag to compare

Added

Changed

Fixed

  • Handle slice bounds check causing panic when getting the current job is called before a job exists (#234) ty @denizzengin

Chores

v1.7.1

27 Aug 18:37
10e5db6
Compare
Choose a tag to compare

Fixed

  • Replace tag map with thread safe sync.map (#212) ty @djenriquez
  • Catch time.AfterFunc firing early per wall clock time (#214) @JohnRoesler
    • This is an exciting fix related to occurrences of jobs firing twice unexpectedly. TL;DR, the monotonic and wall clock times can be slightly out of sync causing functions like time.AfterFunc to fire "early" per the wall clock time, when it was accurate per monotonic time. Look into the PR + linked issues for more details.

v1.7.0

17 Aug 20:45
3b7fc6f
Compare
Choose a tag to compare

Changed

  • always wait for the cron interval instead of starting immediately to mimmic actual cron behavior (#207) @JohnRoesler - ty to @andschneider for reporting!

Fixed

v1.6.2

10 Jun 14:47
8f63acc
Compare
Choose a tag to compare

Fixed