Repository navigation
Automatically package Linux AppImage after next stable release - #305
Merged
masarray merged 3 commits intoOct 24, 2026
Merged
Conversation
…d with firmware prerequisite
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Automate the already-tested Linux AppImage workflow. On a new published stable GitHub release, verify the release contains a firmware manifest and board image, then dispatch
arstack-studio-linux-appimage.ymlwith that exact immutable tag. The AppImage workflow builds that tag and attaches package + checksum only after smoke tests.Existing M3.H release is not modified retroactively. No firmware or C++ source changes. Manual workflow_dispatch with a release_tag remains available as a fallback. GitHub Actions release events originated by GitHub's own token may not trigger a second workflow; the manual dispatch is retained for that case.