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
Include signing entity in version metadata #6363
Conversation
@swift-ci please smoke test |
4d2f75d
to
e262bd0
Compare
@swift-ci please smoke test |
@swift-ci smoke test |
e262bd0
to
2f14408
Compare
@swift-ci smoke test |
return nil | ||
} | ||
let configuration = self.configuration.signing(for: package, registry: registry) | ||
return try? tsc_await { SignatureValidation.extractSigningEntity( |
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.
I think the method itself is async, so we wont need to use tsc_await here?
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.
As far as I can see, nothing in RegistryClient
is async.
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.
what I mean is that this method takes a completion handler. so we dont need to use tsc_await, we can chain the handlers
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.
Oh, now I get what you mean. We could do that but I think that'll make this code much more complicated tbh. We can have zero and also more than one resource with signing info, so there'll be a bunch of logic for aggregating the results. IMO seems better to just do this for now and eventually replace with real await instead.
2f14408
to
9f465a4
Compare
@swift-ci smoke test |
Clients who are asking for metadata prior to download an archive from the registry may still want to display information from the signature which is non-trivial to extract. This includes it if possible.
9f465a4
to
ff1de60
Compare
@swift-ci smoke test |
@swift-ci smoke test linux |
@swift-ci smoke test windows |
|
@swift-ci smoke test windows |
@swift-ci smoke test macOS |
@swift-ci smoke test windows |
Clients who are asking for metadata prior to download an archive from the registry may still want to display information from the signature which is non-trivial to extract. This includes it if possible.