Repository navigation
Turn the schedules on - #18
Merged
Merged
Conversation
This repository takes over from the separate Java repositories it replaces, whose scheduled and publishing workflows are now off, so the nightly pipeline, the cloud 51Did tests, the example assets update and the monthly copyright update run from here.
ben51degrees
marked this pull request as ready for review
November 2, 2026 20:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The separate Java repositories this one replaces have had their scheduled and publishing workflows disabled, so the same job can no longer run in both. This uncomments the schedules here: the nightly pipeline at 03:00, the cloud 51Did tests at 05:10, the example assets update on Mondays and the monthly copyright update on the first of the month, all as the separate repositories had them.
The Publish dry run from this repository is green end to end, and the packages it built match the last releases of the separate repositories.
What was checked
Every workflow file still loads as YAML with the schedule in place. Nothing runs until this merges.