Include spec_version in role metadata #197
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This looks good, you may want to look at an in progress TAP about TUF version management. It is trying to allow for updates to the specification version to allow for breaking changes. This is still ongoing, but any feedback would be appreciated. |
erickt
force-pushed
the
spec_version
branch
2 times, most recently
from
7f6bd64 to
e145f88
Compare
In the [spec] in section 4, each metadata role includes a "spec_version" field that corresponds to the TUF metadata format. [spec]: https://github.com/theupdateframework/specification/blob/master/tuf-spec.md Change-Id: Ia91d44af91d2da37065f2f811b1fa2decdae6b25
Collaborator
Author
|
Rebased on top of master @mnm678 and thanks! I'll check out that spec. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In the spec in section 4, each metadata role includes a "spec_version"
field that corresponds to the TUF metadata format.