Repository navigation
Automate per-branch releases and add demo APK release - #6
Merged
Merged
Conversation
Automate per-branch releases (dev prereleases, main stable)
Stable pushes to main now open a draft GitHub Release with the matching CHANGELOG section, and a new demo-app-release job builds example_app, uploads haptify-demo-<tag>.apk, and publishes the release. Gated on a new_stable_tag job output so dev prereleases and no-op main pushes skip it, and a failed build leaves only a draft.
The demo app depends on the package by path, so changes under lib/ can break its Android build, which analyze and test never exercise. Build it on every CI run and attach the APK as a workflow artifact so a demo-app change can be tried on a device without cutting a release. Enables the Flutter SDK cache to offset the added build time.
Building the APK on every feat/* pull request added minutes of Gradle time to each review cycle. Gate the build and upload steps to push events on dev and main; PRs keep analyze and test, and the artifact appears once the branch merges.
publish.yaml gates on dart pub publish --dry-run, which exits 65 when CHANGELOG.md does not mention the exact version being published. Dev prereleases never had a -dev.N section, so every one of them failed at that step; v0.4.0-dev.1 and v0.5.0-dev.1 never reached pub.dev. Prepend the section in the synthesized release commit, alongside the pubspec edit. Only the tag is pushed, so dev and main keep a changelog free of prerelease entries.
haptify-demo-v<version> instead of a 40-character commit hash, matching how the release asset is named. The APK inside the artifact gets the same name rather than the generic app-release.apk.
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
1 participant
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.
No description provided.