Use new shared workflow to publish firmware to Cloudflare R2 #33
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
jesserockz
changed the title
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.
Moving to a new shared workflow that keeps all of the firmware building and uploading logic in a single place and keeps consistency across our firmware repositories.
The manifests and binaries will be stored in a Cloudflare R2 Bucket which will be referenced by the
firmware.esphome.iodomain once the other firmwares have all be set up as well.To release a new version of firmware to "production", a GitHub release needs to be made with the desired version. The workflow will rewrite the
project_versionvalue in YAML before compiling with this version.