Re: "rolling" release artifacts on GitHub

On 7/12/2023 20:21, Dirk Hohndel via subsurface wrote: There is an oddity about the way this works. GitHub only does releases for tags. So there are basically two options: (a) do a "latest" tag and post all the binaries under that (which is what I've done so far) (b) create a tag for every merg

Re: "rolling" release artifacts on GitHub

Hi Dirk. On 10/12/23 16:17, Dirk Hohndel wrote: It also seems to be possible to create release with an indicative name without having to add it as a tag in the repository - at least when using GitHub actions to create the release: https://github.com/betaflight/betaflight-configurator/blob/0

Re: "rolling" release artifacts on GitHub

> On Dec 9, 2023, at 18:08, Michael wrote: > > > I have used (b) in the past, and gone for a concatenation of a datestring > with a counter - this results in release numbers that make it obvious how > recent they are, which is an advantage when trying to help people reporting a > problem. Y

Re: "rolling" release artifacts on GitHub

Hi Dirk. On 8/12/23 08:21, Dirk Hohndel via subsurface wrote: As Michael and I try to improve the way we post binaries for people to test and use, following up on the Ubuntu and Fedora binaries I mentioned earlier, we now have binaries posted on GitHub as "daily" or "latest" releases: https

Re: "rolling" release artifacts on GitHub

I should have mentioned that this only can work if you uninstall the store app. That's a Google "feature" that actually mostly makes sense. The app looking hung could be the initial connection / initial download from the cloud. There isn't enough visual feedback for that. But I'm not planning t

Re: "rolling" release artifacts on GitHub

I downloaded 261 (and 262) and both of them presented the invalid package error. But after uninstalling the Google Play store version the APK installed successfully. I'm running 262 at the moment. The first time running, after entering my credentials I was presented with an empty dive list

Re: "rolling" release artifacts on GitHub

> On Dec 8, 2023, at 07:56, I wrote: > > > I still can't adb to actually work here on the mac that I'm traveling with - > so I remotely installed the apk on a device connected at home for that > purpose. adb seemed to think it installed correctly - but maybe it failed and > I just can't see

Re: "rolling" release artifacts on GitHub

well, two reports clearly state a trend. back to the drawing board. I still can't adb to actually work here on the mac that I'm traveling with - so I remotely installed the apk on a device connected at home for that purpose. adb seemed to think it installed correctly - but maybe it failed and I

Re: "rolling" release artifacts on GitHub

Same story here. Just tried to install Subsurface-mobile-5.0.10.260.apk on my Motorola Thinkphone (Android 13) with and "invalid package" error.

Re: "rolling" release artifacts on GitHub

I have tried installing the APK in my S20, but it fails as it appears to be an invalid package :( Not sure if that's an issue locally, or a general one (I've been fighting with the Blackberry "business restriction" nonsense since we started using it to control access to work systems). On 7 De

"rolling" release artifacts on GitHub

As Michael and I try to improve the way we post binaries for people to test and use, following up on the Ubuntu and Fedora binaries I mentioned earlier, we now have binaries posted on GitHub as "daily" or "latest" releases: https://github.com/subsurface/subsurface/releases/tag/latest There is