Skip to content

install.sh leads to different versions, depending on available install method (brew, npm, git) #260

@RobertKosten

Description

@RobertKosten

Platform

  • debian 12.11
  • bash 5.2.15(1)-release
  • curl -#fLo- 'https://raw.githubusercontent.com/hyperupcall/autoenv/main/scripts/install.sh' | sh, as recommended in README.md
  • v0.4.0, v0.3.0, HEAD

Describe the bug

  • brew seems to go for the correct v0.4.0 (I don't have MacOS and I won't bother installing it on Linux)
  • npm is still on version v0.3.0
  • git pulls in HEAD (b030c1922448cfc658b32b5b05cc69278347eb64) and this repo does not follow git-flow, so that is different from the tagged v0.4.0 (11ab75f38b14cb3b7b443399e83947347c7445cc)

Expected behavior

All three installation paths, brew, npm, git used by install.sh install the same, the latest, version; Currently v0.4.0.

Additional context

Frankly I see no point in even having the brew and npm calls (But then I'm neither a MacOS nor a JS aficionado ;-) ), the pure git one seems eminently portable on its own, at least if it went for the tagged version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions