Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Approaches to support multi-version trust policy #415

Closed
priteshbandi opened this issue Jun 11, 2024 · 2 comments
Closed

Approaches to support multi-version trust policy #415

priteshbandi opened this issue Jun 11, 2024 · 2 comments
Labels
Stale

Comments

@priteshbandi
Copy link
Contributor

Do we need to consider how to support a multi-version trust policy? If we have trust policy v2.0, and the struct fields differ from v1.0 because our verifier uses the v1.0 struct directly, how can we ensure that both v1.0 and v2.0 work without causing breaking changes?

Originally posted by @JeyJeyGao in #394 (comment)
@priteshbandi priteshbandi mentioned this issue Jun 11, 2024
Merged
@github-actions GitHub Actions
Copy link

This issue is stale because it has been opened for 60 days with no activity. Remove stale label or comment. Otherwise, it will be closed in 30 days.

@github-actions github-actions bot added the Stale label Aug 11, 2024
@github-actions GitHub Actions
Copy link

Issue closed due to no activity in the past 30 days.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Stale
Projects
Notary Project Planning Board
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@priteshbandi