I've been running FFB-Bridge with the updates configured to check the Beta track for updates. I had the latest beta (1.4.1-rc3) installed. When I manually checked for an update, it reported that I was on the latest build. However, I just received the announcement email reporting that FFB-Bridge 1.4.2 was released.
Now perhaps Stable 1.4.2 is identical to Beta 1.4.1-rc3 and there was nothing to worry but shouldn't FFB-Bridge have grabbed the 1.4.2 update even when configured for the Beta channel?
It should have - I just installed 1.4.1-RC3 to check, and it does pop up the "Update Ready" option.
Most likely you have this set to the Beta channel - and 1.4.2 never hit that. It went straight to the release channel, I did a smaller closed beta with a few people for this one.
Yes. I should have been clearer in my original post. When I switched the channel back to "Stable" and checked, I did get the update to 1.4.2. My point, though, is that if you hadn't sent out an email notice (or I had unsubscribed from emails), I'd have never received the update or known that an update was available as long as I left my channel set to "Beta".
I'd have expected that even with the channel set to "Beta" that if there was a newer release in "Stable" it would be offered when checking for updates.
Hey this is sorted now. Older beta clients should see the full 1.4.4 release, and going forward beta channel clients will check both stable and beta, and take the most recent version. Stable channel only checks the stable channel.