dev-cmd/vendor-gems: run bundle clean

[Bo98]

Fixes install inconsistencies between standalone and all other bundle operations.

Should work as is but will test properly in a bit

[MikeMcQuaid]

Fixes install inconsistencies between standalone and all other bundle operations.

This resolves inconsistencies but in the wrong direction for base64 if we care about handling that.

Removing

brew/Library/Homebrew/.bundle/config

Line 3 in 49609ec

BUNDLE_CLEAN: "true"

(or making it false) and making bundle clean always require an explicit call feels like it might be nicer?

[Bo98]

I wouldn't necessarily say wrong. Standalone mode is the mode that's much less used than regular mode. So regular mode using the base64 that ships with Ruby (when the versions match) is fine as that's what happens to everyone else.

What breaks things is when it flip flops between the two, but this should fix that as it undos the unique standalone mode behaviour.

[Bo98]

#16893 is proof of this working

[MikeMcQuaid]

I don't understand why this works when I tried this approach before and it didn't seem to work before but: it's working and that's great, nice work @Bo98!

[Bo98]

I don't understand why this works when I tried this approach before and it didn't seem to work before but: it's working and that's great, nice work @Bo98!

If you were trying locally, it's possible the Bootsnap cache already got corrupt and would have required manually deleting. But in CI that's fine because we don't carry that cache over and for other end users it's also OK as we never shipped the bad state.

[MikeMcQuaid]

If you were trying locally, it's possible the Bootsnap cache already got corrupt and would have required manually deleting. But in CI that's fine because we don't carry that cache over and for other end users it's also OK as we never shipped the bad state.

Yeh, Bootsnap was definitely messing some stuff up here. Thanks for explaining @Bo98!