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.
This changes a few things in how we deploy artifacts and metadata.
Artifacts for Releases
The Build All Targets action now listens to tag push events. Whenever we push a new tag (e.g., v1.15.1), this workflow will create a Github Release draft with the same title as the tag name and upload all artifacts as assets for download.
Artifacts for Special branches [stable, main, beta]
When pushing to any of the special branches, we grab the artifacts and metadata and upload them to S3
Manual Dispatch
You can now manually dispatch a new build by specifying a tag name. In cases where we want to try a rebuild of artifacts, it is only available for users with WRITE access to the repository.
Example Release:
Note: this is only a test, there was no tag bound to the release, this won't happen once we merge.
https://github.com/PX4/PX4-Autopilot/releases/tag/untagged-c09b4e98ea628e4e1fc2