-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cli: search for {input}.sigstore.json
by default
#820
Conversation
Signed-off-by: William Woodruff <william@trailofbits.com>
Signed-off-by: William Woodruff <william@trailofbits.com>
They can be the same if the user explicitly passes in `--bundle`. Signed-off-by: William Woodruff <william@trailofbits.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This combines two items:
- handling implicit vs explicit bundle and
- handling legacy implicit bundle vs sigstore.json implicit bundle.
There's at least one issue left from that: if an explicit bundle is used, but the file does not exist then we use legacy implicit bundle. This seems wrong.
Good catch, thanks -- that does seem wrong. I'll fix that. |
Updates the requirements on [ruff](https://github.com/astral-sh/ruff) to permit the latest version. - [Release notes](https://github.com/astral-sh/ruff/releases) - [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md) - [Commits](astral-sh/ruff@v0.0.18...v0.1.7) --- updated-dependencies: - dependency-name: ruff dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: William Woodruff <william@trailofbits.com>
This prevents us from accidentally falling back on the legacy implicit bundle when the user's explicitly specified `--bundle` is specified but does not exist. Signed-off-by: William Woodruff <william@trailofbits.com>
…to ww/sigstore-json
This tweaks the default input collection in
sigstore verify
, allowing{input}.sigstore.json
to take priority when attempting to discover "implicit" inputs.{input}.sigstore
is also still discovered, preserving compatibility with existing outputs. However, discovering it now produces a logged warning telling the user that a future release will deprecate.sigstore
in favor of.sigstore.json
.We also produce a hard error when both
{input}.sigstore
and{input}.sigstore.json
are present -- this should really only happen in cases of user confusion, so we just prevent it outright.See #814.