ci: Manually upgrade pex version to avoid platform-flapping issue #498
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When generating lockfiles in different architectures (x86-64/arm64), an extra platform tag (which is not used actually) becomes alternating. To avoid this issue, we could upgrade pex to 2.1.93. Also upgrade Pants from 2.12.0rc2 to 2.12.0rc3.
You don't have to do anything special. For source-based pants users, you need to manually checkout the new release tag, but there is no "release_2.12.0rc3" tag yet. As there is no significant functional differences between rc2 and rc3, you may just stay as-is.
refs pex-tool/pex#1685
refs https://github.com/pantsbuild/pants/blob/2.12.x/src/python/pants/notes/2.12.x.md