-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
{Packaging} Bump cryptography to 41.0.1 and pyOpenSSL to 23.2.0 on Linux and MacOS #26671
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
Discussion: Should we silence the warning raised by I did consider disabling the warning by calling import platform
if platform.system() == 'Windows' and platform.architecture()[0].startswith('32'):
import warnings
warnings.simplefilter("ignore", category=UserWarning)
import cryptography.hazmat.bindings.openssl.binding but I think it is good to keep that warning to encourage people to upgrade to 64-bit Azure CLI once #26640 has been released. Additional information |
@@ -1,5 +1,8 @@ | |||
pushd %~dp0..\.. | |||
|
|||
Rem Upgrade pip to the latest version | |||
python -m pip install --upgrade pip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgrading pip
makes VerifyWindowsRequirements
, VerifyLinuxRequirements
and VerifyDarwinRequirements
have the same logic as other package building jobs, such as BuildDebPackages
.
It can utilize the latest pip
's error message to better find dependency resolution failures.
We have decided to keep the warning, as it is printed to
please set Update: We finally decided to postpone the version bump on Windows until Windows 64-bit MSI has been released (#26640). |
482f3a4
Description
Rework of #26596
As explained in #26596 (comment), only bumping
cryptography
is not enough.pyOpenSSL
should be bumped at the same time.Close #25913