Failed to download step after recent 1.3.1 release

[mrister]

Has the release been done fully ?

[adamivancza]

yeah I can see the same issue on our builds

[adamivancza]

As a workaround, you can manually downgrade your NVM step to 1.3.0 to get this working again.

[ZioCain]

Same here. Applied the workaround to manually set the version 1.3.0 (through bitrise.yml) and it worked.

On a side note, version 1.2.2 will also break

[Almouro]

Damn, seems like there are some issues on nvm https://github.com/nvm-sh/nvm/issues/1985 about exiting with code 3

I couldn't reproduce quickly and find a fix so I'll revert so that the folks on auto update don't have their CI suddenly crashing for no reason

[Almouro]

Here's the PR on the Bitrise step lib https://github.com/bitrise-io/bitrise-steplib/pull/3553

Sorry everyone, didn't imagine that a simple set -e would break this much. If I do re-release the set -e, I'll make it a breaking change in the versioning to be safe

[mrister]

Thanks @Almouro

[jesse0824]

As a workaround, you can manually downgrade your NVM step to 1.3.0 to get this working again.

How would you manually downgrade NVM step to 1.3.0? I'm asking for a friend. :-)

[adamivancza]

As a workaround, you can manually downgrade your NVM step to 1.3.0 to get this working again.

How would you manually downgrade NVM step to 1.3.0? I'm asking for a friend. :-)

Just edit the bitrise.yml file and change the nvm step to be: - nvm@1.3.0:

[ghost]

version downgrade works for me

[jesse0824]

@adamivancza thanks for the info! That worked for me. My builds are working again.

[ronenempathy]

any update on this ?

[Almouro]

Hi @ronenempathy, version 1.3.2 of the nvm step should revert the breaking change and work Let me know if it doesn't!