Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update cron to v3.0 + CronSchedule Timezone support #2215

Merged
merged 3 commits into from
Dec 21, 2021
Merged

Update cron to v3.0 + CronSchedule Timezone support #2215

merged 3 commits into from
Dec 21, 2021

Conversation

elb3k
Copy link
Contributor

@elb3k elb3k commented Nov 22, 2021

What changed?
Upgraded robfig/cron from v1.2.0 to v3.0.0

Why?
New robfig/cron has a support for timezone, which is requested by this

How did you test it?
Using develop/buildkite scripts for standard predefined tests
And added cron tests with CRON_TZ specified, with and without daylight saving.

Potential risks
Not to my knowledge, cron library is used only in one place, and cron is backwards compatible.

Is hotfix candidate?
Yes, since PR will add only minor feature

@CLAassistant
Copy link

CLAassistant commented Nov 22, 2021

CLA assistant check
All committers have signed the CLA.

@yiminc yiminc requested a review from dnr November 22, 2021 18:28
@elb3k elb3k marked this pull request as ready for review November 25, 2021 07:41
@elb3k elb3k requested a review from a team November 25, 2021 07:41
@elb3k elb3k changed the title Update cron to v3.0 Update cron to v3.0 + CronSchedule Timezone support Nov 25, 2021
Copy link
Member

@dnr dnr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,
Thanks for the contribution! This looks good, and we can target it for 1.15. To help ensure that the required tzdata is available in the official docker images, I made PR #2277 also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants