Update of fastlane fails gitlab ci pipeline about fastlane

[lacostej]

It looks like fastlane binary final location moved and/or the PATH wasn't reloaded.

Could you run fastlane env to see how fastlane is configured?

In the mean time I suggest to lock fastlane e.g. using Bundler and avoid using the update_fastlane action

[krypt-lx]

fastlane was installed using Homebrew. One moment, I trying to access build agent (and It is not going smoothly)

Also, on unrelated note, (probably I should create separate issue) fastlane does update by invoking brew upgrade (update all packages and not just the fastlane), causing undesirable side effects (Bazel version changed from 6.4.0 to 7.0.0 in my local machine some time ago)

[krypt-lx]

Could you run fastlane env to see how fastlane is configured?

Sorry, not at this current moment. There seems to be some issues with remote access.

[krypt-lx]

Added env to the issue

[lacostej]

Also, on unrelated note, (probably I should create separate issue) fastlane does update by invoking brew upgrade (update all packages and not just the fastlane), causing undesirable side effects (Bazel version changed from 6.4.0 to 7.0.0 in my local machine some time ago)

Oh you're right. Brew upgrade by default also updates all outdated packages. Bad design...

The code has been doing brew upgrade fastlane since 2020. https://github.com/fastlane/fastlane/blame/master/fastlane/lib/fastlane/actions/update_fastlane.rb#L58

[krypt-lx]

It happend somewhere around autumn 2023, and not in 2020 for sure.
That heppened, It wasn't even formulae update what happened: Bazel formulae is 6.4.0 even now. But I had installed Bazelisk one and somehow it took over Bazel instead.