Skip to content

Import X509 in PackageSigning #6228

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

Merged
merged 1 commit into from
Mar 6, 2023
Merged

Import X509 in PackageSigning #6228

merged 1 commit into from
Mar 6, 2023

Conversation

neonichu
Copy link
Contributor

@neonichu neonichu commented Mar 3, 2023

This includes #6216 right now so that we can run CI with both.

This should work as a way to prove that everything is set up correctly for depending on `X509` in practice.
@neonichu neonichu changed the title WIP: Import X509 in PackageSigning Import X509 in PackageSigning Mar 4, 2023
@neonichu neonichu marked this pull request as ready for review March 4, 2023 05:14
@neonichu
Copy link
Contributor Author

neonichu commented Mar 4, 2023

@swift-ci please smoke test

@neonichu
Copy link
Contributor Author

neonichu commented Mar 4, 2023

Windows build will fail here since it needs swiftlang/swift#64087

@neonichu
Copy link
Contributor Author

neonichu commented Mar 4, 2023

@swift-ci please smoke test

@tomerd
Copy link
Contributor

tomerd commented Mar 6, 2023

seems to work 🎉

@neonichu neonichu merged commit a87d74e into main Mar 6, 2023
@neonichu neonichu deleted the use-cert-lib branch March 6, 2023 19:08
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.

3 participants