-
Notifications
You must be signed in to change notification settings - Fork 463
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
Update OpenSSH downstream branch to OQS-v9 #1898
Conversation
Signed-off-by: Spencer Wilson <[email protected]>
@geedo0 You'll need to set the workflow in OpenSSH to be triggered on |
Ack, added the trigger to the PR here. |
Apparently the GitHub trigger won't do anything unless the downstream workflow is on the default branch: see open-quantum-safe/openssh#168 (comment) for discussion. |
Signed-off-by: Spencer Wilson <[email protected]>
Signed-off-by: Spencer Wilson <[email protected]>
Signed-off-by: Spencer Wilson <[email protected]>
This reverts commit ba4a551. Signed-off-by: Spencer Wilson <[email protected]>
Trigger tested on commit caea971: see the upstream and and downstream runs. For testing, I disabled the other downstream triggers and set the workflow to be triggered on pushes to this branch; the most recent commit reverts these changes. |
As per open-quantum-safe/openssh#166.
* [ ] Does this PR change the input/output behaviour of a cryptographic algorithm (i.e., does it change known answer test values)? (If so, a version bump will be required from x.y.z to x.(y+1).0.)* [ ] Does this PR change the list of algorithms available -- either adding, removing, or renaming? Does this PR otherwise change an API? (If so, PRs in fully supported downstream projects dependent on these, i.e., oqs-provider will also need to be ready for review and merge by the time this is merged.)