Update packages weekly instead of daily - #20
Merged
Conversation
Over the last 30 days virtually all of this repository's workflow activity was the daily package update itself plus the CI its push triggers. For a repository with this little day-to-day change, weekly freshness costs one seventh of the runs with no practical loss; manual dispatch remains for an urgent bump.
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
1 participant
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.
Continuation of the Actions load reduction: this repository's last 30 days of workflow runs were almost entirely the daily Update Packages cron and its push-triggered cascade. Weekly cadence (same staggered minute/hour, day 1) keeps dependencies fresh at 1/7th of the load;
workflow_dispatchremains for urgent bumps.