Update flux.rb to always use latest version

[lumaxis]

Using a versioned cask for this imo is not an ideal solution. For one, it's not very relevant which exact version your using and for me, also the security of having a sha256 check weighs less than always getting latest version without any maintenance cost. Also, according to the Contribution guidelines, an unversioned link is the preferred method.

[vitorgalvao]

and for me, also the security of having a sha256 check weighs less than always getting latest version without any maintenance cost.

But it is important for most other users, and casks aren’t changed to meet individual preferences (you can, however, set a personal tap for this cask that will solve your problem).

If it says in the guidelines an unversioned link is preferred, it is because we forgot to change it. Please point us to where the error is.

[lumaxis]

This seems curios to me. Maybe I am using cask in a different way than most people but for most applications I'd rather have the most up-to-date version without any additional work on a caskfile than getting a very specific version of a small helper tool like in this case flux.
Just out of curiosity, has there been a discussion with the community about this topic anywhere? I'd be interested to better understand other people's reasons behind this. 😊

The preference for unversioned links is mentioned in several places in your CONTRIBUTING.md:

• Adding a Cask - Examples: "This combination of version :latest and sha256 :no_check is currently the preferred mechanism when an unversioned download URL is available"
• Cask Stanzas: "application version; give the value :latest if an unversioned download is available"

[vitorgalvao]

has there been a discussion with the community about this topic anywhere?

Yes.

[lumaxis]

Perfect, thank you!