Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare the 2.1.64 release. #1590

Merged
merged 1 commit into from
Jan 25, 2022
Merged

Prepare the 2.1.64 release. #1590

merged 1 commit into from
Jan 25, 2022

Conversation

jsirois
Copy link
Member

@jsirois jsirois commented Jan 25, 2022

Closes #1573

Copy link
Contributor

@Eric-Arellano Eric-Arellano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

Would it make sense to include the universal lock change in this release? Iirc, you're not announcing those tho because it's experimental.

@jsirois
Copy link
Member Author

jsirois commented Jan 25, 2022

I don't think so. Primarily because #1587 is a pressing bug. That aside though, the universal lock is not usable right now since it can't be read. I've got that 1/2 done (extra metadata is now written down in the lock #1585) but the resolve side of using the lock remains (See: #1583). As such no one would benefit from including the ability to write down a fancy lock but not actually use it afaict.

@jsirois jsirois merged commit f4d4712 into pex-tool:main Jan 25, 2022
@jsirois jsirois deleted the issues/1573 branch January 25, 2022 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Release 2.1.64
2 participants