ci: change nightly to run in UTC time to fix nightly-status check#8629
Merged
Conversation
Contributor
WalkthroughThe scheduled time for the nightly build GitHub Actions workflow was changed from 6:30 UTC to 00:00 UTC. No other modifications were made to the workflow's logic, environment, or steps. Changes
📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (1)
🔇 Additional comments (1)
|
ogabrielluiz
approved these changes
Jun 20, 2025
ogabrielluiz
pushed a commit
to bkatya2001/langflow
that referenced
this pull request
Jun 24, 2025
…ngflow-ai#8629) Change nightly to run in UTC time
Khurdhula-Harshavardhan
pushed a commit
to JigsawStack/langflow
that referenced
this pull request
Jul 1, 2025
…ngflow-ai#8629) Change nightly to run in UTC time
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.
Nightly builds ran at 06:30 UTC.
check-nightly-statuschecked that the day the PR ran was the same day the latest nightly was published. Thus, there was a window where the latest published nightly was from the "day before" from the perspective of the PR, but that's just because the workflow hadn't run yet for the (UTC-based) day.This PR changes the nightly to run in UTC time. Seems more standard.
Summary by CodeRabbit