Automatically release a new version of flyctl daily #3626
Merged
Conversation
This file contains 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
|
Oh I realized, we should skip deploying on Fridays and weekends to not cause trouble when most of us are offline |
billyb2
force-pushed
the
auto_release_flyctl
branch
from
e201e37
to
9e44769
Compare
billyb2
force-pushed
the
auto_release_flyctl
branch
from
9e44769
to
fc810a9
Compare
Not Eastern time (daylight savings not included)
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.
Change Summary
What and Why:
By automatically releasing flyctl, as long as a PR gets approved and merged, it'll show up in a new flyctl release relatively soon. We can also release a new version if necessary.
How:
Added a new Github Action that runs every day at 3 PM eastern
Related to:
https://flyio.slack.com/archives/C06G424TJRF/p1718101085197859?thread_ts=1718047902.923779&cid=C06G424TJRF
Documentation