From 1456de121d1b6e5b5d31153531c51698cd7b9a98 Mon Sep 17 00:00:00 2001 From: Brian DeHamer Date: Wed, 20 Nov 2024 16:24:49 -0800 Subject: [PATCH] bump actions/attest to v2.0.0 Signed-off-by: Brian DeHamer --- README.md | 19 +++++++------------ action.yml | 6 +++--- 2 files changed, 10 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index 0faac02c..ae45f014 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ See [action.yml](action.yml) with: # Path to the artifact serving as the subject of the attestation. Must # specify exactly one of "subject-path" or "subject-digest". May contain a - # glob pattern or list of paths (total subject count cannot exceed 2500). + # glob pattern or list of paths (total subject count cannot exceed 1024). subject-path: # SHA256 digest of the subject for the attestation. Must be in the form @@ -95,24 +95,20 @@ See [action.yml](action.yml) | Name | Description | Example | | ------------- | -------------------------------------------------------------- | ------------------------ | -| `bundle-path` | Absolute path to the file containing the generated attestation | `/tmp/attestation.jsonl` | +| `bundle-path` | Absolute path to the file containing the generated attestation | `/tmp/attestation.json` | Attestations are saved in the JSON-serialized [Sigstore bundle][6] format. -If multiple subjects are being attested at the same time, each attestation will -be written to the output file on a separate line (using the [JSON Lines][7] -format). +If multiple subjects are being attested at the same time, a single attestation +will be created with references to each of the supplied subjects. ## Attestation Limits ### Subject Limits -No more than 2500 subjects can be attested at the same time. Subjects will be -processed in batches 50. After the initial group of 50, each subsequent batch -will incur an exponentially increasing amount of delay (capped at 1 minute of -delay per batch) to avoid overwhelming the attestation API. +No more than 1024 subjects can be attested at the same time. ## Examples @@ -148,8 +144,8 @@ jobs: ### Identify Multiple Subjects -If you are generating multiple artifacts, you can generate a provenance -attestation for each by using a wildcard in the `subject-path` input. +If you are generating multiple artifacts, you can attest all of them at the +same time by using a wildcard in the `subject-path` input. ```yaml - uses: actions/attest-build-provenance@v1 @@ -245,7 +241,6 @@ jobs: [5]: https://cli.github.com/manual/gh_attestation_verify [6]: https://github.com/sigstore/protobuf-specs/blob/main/protos/sigstore_bundle.proto -[7]: https://jsonlines.org/ [8]: https://github.com/actions/toolkit/tree/main/packages/glob#patterns [9]: https://docs.github.com/en/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds diff --git a/action.yml b/action.yml index 0fc77c1c..a4ca096f 100644 --- a/action.yml +++ b/action.yml @@ -10,7 +10,7 @@ inputs: description: > Path to the artifact serving as the subject of the attestation. Must specify exactly one of "subject-path" or "subject-digest". May contain a - glob pattern or list of paths (total subject count cannot exceed 2500). + glob pattern or list of paths (total subject count cannot exceed 1024). required: false subject-digest: description: > @@ -44,7 +44,7 @@ inputs: outputs: bundle-path: - description: 'The path to the file containing the attestation bundle(s).' + description: 'The path to the file containing the attestation bundle.' value: ${{ steps.attest.outputs.bundle-path }} runs: @@ -52,7 +52,7 @@ runs: steps: - uses: actions/attest-build-provenance/predicate@36fa7d009e22618ca7cd599486979b8150596c74 # predicate@1.1.4 id: generate-build-provenance-predicate - - uses: actions/attest@67422f5511b7ff725f4dbd6fb9bd2cd925c65a8d # v1.4.1 + - uses: actions/attest@v2.0.0 id: attest with: subject-path: ${{ inputs.subject-path }}