You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that ssh2-python has returned, let's switch the primary ssh-backend
dependency to it. This primary dependency will be removed in Broker 0.7
along with the ssh2_python311 and ssh2_python312 optional dep
definitions.
Also, with the merge of SatelliteQE#346, we can fix how the license is attributed
in the project metadata. This moves us in compliance with the newer PEP
639 standard.
FixesSatelliteQE#347
Now that ssh2-python has returned, let's switch the primary ssh-backend
dependency to it. This primary dependency will be removed in Broker 0.7
along with the ssh2_python311 and ssh2_python312 optional dep
definitions.
Also, with the merge of SatelliteQE#346, we can fix how the license is attributed
in the project metadata. This moves us in compliance with the newer PEP
639 standard.
FixesSatelliteQE#347
Now that ssh2-python has returned, let's switch the primary ssh-backend
dependency to it. This primary dependency will be removed in Broker 0.7
along with the ssh2_python311 and ssh2_python312 optional dep
definitions.
Also, with the merge of SatelliteQE#346, we can fix how the license is attributed
in the project metadata. This moves us in compliance with the newer PEP
639 standard.
FixesSatelliteQE#347
For the primary ssh-backend dependency before Broker 0.7, let's move back to ssh2-python.
Read through the parent issue #342 for more information.
The text was updated successfully, but these errors were encountered: