handle attests correctly with provenance and sbom inputs #1086
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.
We don't detect usage of
attests
input and therefore settingattests: type=provenance,mode=max
will result in a duplicated provenance as we already set it automatically and build will fail with:This will also set
builder-id
automatically ifprovenance
is used inattests
which was not the case before.To keep everything consistent across our flags such as
load
andpush
,provenance
andsbom
inputs take precedence over ones set inattests