Skip to content

Commit

Permalink
Add CHANGELOG and remove version from individual files.
Browse files Browse the repository at this point in the history
Signed-off-by: Tom Hennen <tomhennen@google.com>
  • Loading branch information
TomHennen committed May 5, 2024
1 parent efef96f commit e8eb78a
Show file tree
Hide file tree
Showing 7 changed files with 12 additions and 32 deletions.
11 changes: 11 additions & 0 deletions spec/v1/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# Changelog

## v1.1

* Clarified that subjects are assumed to be immuatble and that it is
acceptable to use a non-cryptographic digest (though cryptographic
digests are still preferred).

## v1

Initial release.
2 changes: 1 addition & 1 deletion spec/v1/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Specification for in-toto attestation layers

Version: v1.0
Version: v1.1

Index:

Expand Down
2 changes: 0 additions & 2 deletions spec/v1/bundle.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,5 @@
# Bundle layer specification

Version: v1.0

An attestation Bundle is a collection of multiple attestations in a single
file. This allows attestations from multiple different points in the software
supply chain (e.g. Provenance, Code Review, Test Result, vuln scan, ...) to
Expand Down
13 changes: 0 additions & 13 deletions spec/v1/digest_set.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,5 @@
# DigestSet field type specification

Version: v1.1

Set of one or more cryptographic digests, or other immutable references,
for a single software artifact or metadata object.

Expand Down Expand Up @@ -188,17 +186,6 @@ flexibility for the user's various use cases.
- `{"sha256": "abcd"}` does not match `{"sha256": "fedb", "sha512": "abcd"}`
- `{"somecoolhash": "abcd"}` uses a non-predefined algorithm

## Change History

### v1.1

Clarified that it is acceptable to use a non-cryptographic digest (though
cryptographic digests are still preferred).

### v1.0

Initial

<!-- Add a horizontal rule to separate footnotes -->

---
Expand Down
2 changes: 0 additions & 2 deletions spec/v1/predicate.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,5 @@
# Predicate layer specification

Version: v1.0

The Predicate is the innermost layer of the attestation, containing arbitrary
metadata about the [Statement]'s `subject`.

Expand Down
2 changes: 0 additions & 2 deletions spec/v1/resource_descriptor.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,5 @@
# ResourceDescriptor field type specification

Version: v1.0

A size-efficient description of any software artifact or resource (mutable
or immutable).

Expand Down
12 changes: 0 additions & 12 deletions spec/v1/statement.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,5 @@
# Statement layer specification

Version: v1.1

The Statement is the middle layer of the attestation, binding it to a
particular subject and unambiguously identifying the types of the
[Predicate].
Expand Down Expand Up @@ -67,16 +65,6 @@ Additional [parsing rules] apply.
> set-but-empty. MAY be omitted if `predicateType` fully describes the
> predicate.
## Change History

### v1.1

Clarified that subjects are assumed to be immutable.

### v1.0

Initial

[ResourceDescriptor]: resource_descriptor.md
[JSON]: https://www.json.org/json-en.html
[Predicate]: predicate.md
Expand Down

0 comments on commit e8eb78a

Please sign in to comment.