Flyctl update notification but the update is not published

Hey there Fly team,

A friendly note, the cli is notifying that there’s an update available:

a@xxx ~> fly version
Update available 0.0.216 -> 0.0.217
Update with flyctl version update

flyctl v0.0.216 linux/amd64 Commit: 539d4cf BuildDate: 2021-05-06T21:26:41Z

But I see from your latest release that you explicitly disabled upload to AUR / Homebrew etc due to this being a pre-release?

Anyways, it might be a good idea to update the part of flyctl that checks for version updates to exclude pre-relases.

Whoops, we’ll fix that! Thanks for letting us know.

1 Like

@asyrique 0.0.217 is published, that commit message for our CI scripts is confusing. Here’s a better summary of what’s changed: Comparing v0.0.216...v0.0.217 · superfly/flyctl · GitHub. You won’t get a message from flyctl about prereleases unless you opt into them. I’m working on prereleases and update notifications now, so this should be cleaner soon.

Hi @michael , so, I’m not sure if this was intentional, but it seems like the commit you made to disable publishing to AUR for pre-release versions might have had the unintended consequence of not publishing to AUR entirely.

Looking at the latest Actions run from flyctl “Build & publish to AUR” is skipped.

Also, AUR shows the latest published version as 0.0.216-1