Clean up build after update to 7.2.0

[fmeum]

No description provided.

[fmeum]

@keertk @iancha1992 FYI, I prepared this PR to verify compatibility with the new lockfile format. Happy to finalize it when 7.2.0 lands.

[iancha1992]

@keertk @iancha1992 FYI, I prepared this PR to verify compatibility with the new lockfile format. Happy to finalize it when 7.2.0 lands.

Just FYI, if you change the .bazelversion, I think you might need to update the lockfile on all four platforms.

[fmeum]

Thanks, I'm in the process of setting up a Windows VM for that. But I likely need to do it again after the actual release, so I'll wait for that.

[Wyverald]

Thanks, I'm in the process of setting up a Windows VM for that. But I likely need to do it again after the actual release, so I'll wait for that.

I'd suggest you not to worry about it, and let us (me?) do the work when 7.2.0 is actually released :) I've done this multiple times now and have all four machine types on hand.

[Wyverald]

or, actually, if we could get rules_python to declare certain module extensions of theirs to be reproducible, we might be able to just remove all traces of them from the lockfile.

[fmeum]

or, actually, if we could get rules_python to declare certain module extensions of theirs to be reproducible, we might be able to just remove all traces of them from the lockfile.

I looked into that today: Two of their extensions are trivially reproducible (bazelbuild/rules_python#1892), but the pip extension is both os/arch dependendent and not reproducible: it talks to https://pypi.org/simple/ (don't click on that link, it might freeze your browser) during extension evaluation.

[meteorcloudy]

Awesome!

[fmeum]

@bazel-io fork 7.3.0