Repository navigation
Provide permanent one-tap link to latest AppHarbor development APK - #3
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: 4b29e159b6
ℹ️ 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".
| git push origin "refs/tags/$TAG" --force | ||
| gh release edit "$TAG" --title "AppHarbor v${VERSION} — Development Preview" --notes-file release-notes.md --prerelease | ||
| gh release upload "$TAG" "$APK" "$APK.sha256" --clobber | ||
| gh release upload "$TAG" "$APK" "$APK.sha256" AppHarbor-latest-dev.apk AppHarbor-latest-dev.apk.sha256 --clobber |
There was a problem hiding this comment.
On every update to the existing rolling release, this clobbers the asset targeted by the README’s permanent download URL. The CLI documents that with --clobber, “existing assets are deleted before new assets are uploaded” and a failed upload loses the originals (gh release upload); therefore, a transient API or network failure after deletion leaves the prominent AppHarbor-latest-dev.apk link returning 404 until another successful run, while even successful updates have a deletion window. Stage the replacement under another name and swap it safely, or restore/retry the stable asset on failure.
Useful? React with 👍 / 👎.
1 participant
Why
The current rolling
appharbor-devrelease publishes onlyAppHarbor-vX.Y.Z-dev.apk, so direct links require version-specific filenames and go stale after releases.Change
AppHarbor-latest-dev.apkwith its own SHA-256 checksum on every successful development release (including updates to the rolling prerelease).Validation
Reviewed both release creation and update code paths; the new alias is copied from the verified build artifact before publication. This is a workflow/docs change only. GitHub Actions must validate on merge; no successful build or artifact publication is claimed by this PR.