Skip to content

Run the copyright update once a year - #52

Merged
jwrosewell merged 1 commit into
rcfrom
ci/copyright-yearly
Nov 7, 2026
Merged

jwrosewell merged 1 commit into
rcfrom
ci/copyright-yearly

Conversation

@ben51degrees

Copy link
Copy Markdown
Contributor

The copyright update ran on the first of every month, but the copyright year only changes once a year. This moves the schedule in .github/workflows/monthly-copyright-update.yml from 0 0 1 * * to 0 0 1 1 *, which is 00:00 UTC on 1 January, using the same two lines as 51degrees-cxx. The comment above the old line, which said why the cron string is quoted, gives way to the one saying why it runs yearly. The manual start stays, and the file keeps its name, as in 51degrees-cxx.

GitHub reads the five cron fields as minute, hour, day of the month, month and day of the week, so 0 0 1 1 * runs once a year on 1 January. The schedule cannot be exercised before then, and no build covers this file.

Where it came from

The same change was opened as a draft in each of the six repositories this one replaces, as pipeline-java#169, device-detection-java#617, ip-intelligence-java#202, location-java#41, device-detection-java-examples#692 and ip-intelligence-java-examples#184. This repository has one copy of the workflow, so one change covers all six. The commit is the one from pipeline-java, applied to the workflow here, which also takes a dry run input that the old one did not.

The copyright year only changes once a year, so the schedule moves from
00:00 UTC on the first of every month to 00:00 UTC on 1 January, with the
same two lines as 51degrees-cxx. The manual start stays.
@jwrosewell
jwrosewell marked this pull request as ready for review November 7, 2026 16:24
@jwrosewell
jwrosewell merged commit 80233d4 into rc Nov 7, 2026
2 checks passed
@jwrosewell
jwrosewell deleted the ci/copyright-yearly branch November 7, 2026 16:24
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.

2 participants