Repository navigation
Improve AppImage compatibility and update support - #49
boggedbrush wants to merge 3 commits into
Conversation
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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ba08183e8b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| PYTHON_VERSION: "3.12" | ||
| APPIMAGE_PATH: dist/packages/PatchOpsIII.AppImage | ||
| ZSYNC_PATH: dist/packages/PatchOpsIII.AppImage.zsync | ||
| APPIMAGE_UPDATE_INFO: gh-releases-zsync|boggedbrush|PatchOpsIII|latest|PatchOpsIII.AppImage.zsync |
There was a problem hiding this comment.
When this reusable workflow is called by the beta pipeline (release-beta.yml:304-310), it embeds the stable asset name PatchOpsIII.AppImage.zsync, but the publishing job renames that file to PatchOpsIII-Beta.AppImage.zsync (release-beta.yml:462-466). Consequently, a published beta AppImage cannot discover its beta zsync asset using the embedded metadata; pass channel-specific update information or keep the published asset name consistent.
Useful? React with 👍 / 👎.
Summary
.zsyncasset in CI.Changes are limited to
.github/workflows/linux-build.yml.Validation
bash -n.