GitHub workflow release.yaml #42
Conversation
Create a workflow that automatically create releases inside GitHub. The source code should be zipped and uploaded with the last commit message as a release.
|
is this still active? |
|
Currently, no one is on the PR. Our main problem here is that the GitHub release version would not match the Play- / AppStore version. To address this issue we need to either get the version number from the stores or change our CI/CD pipeline. Check out dicussion #51 |
|
i think the wrong version number would be less of an issue than not having any releases at all. Is this merge still going to happen? |
|
The version numbers should be constant for all releases to avoid confusion. Otherwise, the app can simply be built from the source code. I do not see any benifit from releasing the app with mismatching version numbers. |
|
The benefit is that i do not have to compile the app myself when i want to run it on my phone without using the google play store but instead can use the release tab. If it is available in F-Droid i can just use the F-Droid Appstore. I do not care about the Version number at all (besides a possible one displayed within the app). When i install it from the github release page or the F-Droid Appstore i will not care about the google play store version. I do not see any benifit from releasing the app with matching version numbers on different appstores and plattforms as long as the internally displayed number stays the same. It enables much broader access to the app. Else it should be added to the next update to tackle this issue, its been open since about a year now and theres currently still dependency on google for all users that are privacy aware enough to avoid the appstore but lack the knowledge or time to compile the full app. Honestly Setting up flutter and adnroid studio is quite a ... |
Create a workflow that automatically create releases inside GitHub. The source code should be zipped and uploaded with the last commit message as a release.