HelixDB

[wadkhlemshem]

Checklist

• I have searched the issue tracker for relevant or duplicate issues.

I want to suggest a new step

• Which tool is this about? Where is its repository?
  https://github.com/HelixDB/helix-db
• Which operating systems are supported by this tool?
  Linux, Windows, & Mac
• What should Topgrade do to figure out if the tool needs to be invoked?
  Run helix disambiguation, see Helix editor conflicts with HelixDB #1774
• Which exact commands should Topgrade run?
  helix update
• Does it have a --dry-run option? i.e., print what should be done and exit
  helix --version gives a message about new versions available:

[UPDATE] New version available: v2.2.7 -> v2.2.8
         Run 'helix update' to upgrade

Helix CLI 2.2.7

• Does it need the user to confirm the execution? And does it provide a --yes
  option to skip this?
  Yes, it requires user confirmation without a --yes option. It uses https://github.com/jaemk/self_update without the .no_confirm option

More information

• I am able and willing to implement this step myself

[GideonBear]

Feel free to implement after fixing the helix editor conflict, in a separate PR please. The --version dry run is not necessary. Just make sure to add if ctx.config().yes() { cmd.arg("--yes") }.

[wadkhlemshem]

I should clarify. They don't have a --yes cmd line arg. And it's only until the v2.3.0 release that they added a .no_confirm(true) to the self_update options (https://github.com/HelixDB/helix-db/pull/870/changes#diff-b04f70c3eb9708ae210c0d08fd785cf5867f172b9e7f7fdbee6351cefce84d8bR26). To make matters worse, an indicatif based progress bar was added in v2.2.6 (HelixDB/helix-db@e4c6dc5) which obscured the confirmation prompt, ending up in a confusing ux where the user wouldn't know that the cli was waiting for confirmation:

[UPDATE] New version available: v2.2.8 -> v2.3.0
         Run 'helix update' to upgrade

Updating 'CLI'
  ✓ Checked for updates (v2.2.8 -> v2.3.0)
  ⠸ Downloading and installing                                                                                                                                                                                     
helix release status:
  * Current exe: "/Users/$USER/.local/bin/helix"
  * New exe release: "helix-aarch64-apple-darwin"
  * New exe download url: "https://api.github.com/repos/HelixDB/helix-db/releases/assets/358730893"

The new release will be downloaded/extracted and the existing binary will be replaced.
  ⠇ Downloading and installing                                                                                                                                                                                 

It should have displayed the confirmation prompt here. Typing Y + <enter> works but there's no way to know that just by looking at this output. This happens in versions v2.2.6 - v2.2.9. It doesn't happen in v2.3.0 because they added the .no_confirm(true)

How should I proceed? Should I just skip if ctx.config().yes() is true? And perhaps add a note to type Y + <enter>?

[GideonBear]

Don't do anything special to support older versions. If the latest version works fine, you can just run helix update without anything special.
The idea is good, but I don't think it's worth it to add in special machinery for older versions (one notable exception being if older versions of the software are packaged elsewhere).