Repository navigation
feat: expose ClientTrustConfig as a public class - #1496
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Exposing ClientTrustConfig. Since recent changes to SigningContext.staging/production being moved to ClientTrustConfig, it would be better for this class to be public as it is/will be used in Model-Transparency and such. The API has had massive changes as is, so I think it would be better doing this now for next release.
Resolves #1019
Release Note
Added to changelog.md
The ClientTrustConfig class has been moved from the private _internal package to a new public
module (sigstore.trust). This change formally adds the class to the project's public API,
making it available for use in other projects.