You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sigstore sign should probably produce {input}.sigstore.json by default, rather than {input}.sigstore
sigstore verify should accept either {input}.sigstore.jsonor{input}.sigstore, whichever is present (and probably fail if both are present)
(2) is pretty straightforward, and can be done in a backwards-compatible manner. (1) is a breaking change, so we'll either need to feature flag it or defer it until 3.0.
The text was updated successfully, but these errors were encountered:
Per the Sigstore Client Spec
Two parts:
sigstore sign
should probably produce{input}.sigstore.json
by default, rather than{input}.sigstore
sigstore verify
should accept either{input}.sigstore.json
or{input}.sigstore
, whichever is present (and probably fail if both are present)(2) is pretty straightforward, and can be done in a backwards-compatible manner. (1) is a breaking change, so we'll either need to feature flag it or defer it until 3.0.
The text was updated successfully, but these errors were encountered: