Skip to content

Conversation

@jku
Copy link
Member

@jku jku commented Oct 17, 2025

  • Argument is optional, valid values [1,2]
  • Default is 1, except on staging where it's already 2
  • Plan is to change default to 2 (in a major release) as soon as Rekor v2 is available in production
  • There is a test (test does not verify which rekor was actually used but the output shows the entry type)

Fixes #227

It's worth noting that this means we always set --rekor-version now. The annoying part of that is that setting rekor-version:2 right now fails in production (because it's not defined in signingconfig yet)... but I don't want to make that an invalid input since it will start succeeding at some point, and I'm also hesitant to add more complexity like rekor-version: auto or something. I think I'm fine with this: after all, most users should never have to touch this argument.

* Argument is optional, valid values [1,2]
* Default is 1, except on staging where it's 2
* Plan is to change default to 2 in a major release as soon as Rekor
  v2 is available in production

Signed-off-by: Jussi Kukkonen <[email protected]>
@jku jku force-pushed the rekor-version-argument branch from aa0c498 to c394ac5 Compare October 17, 2025 08:42
@jku jku mentioned this pull request Oct 17, 2025
@woodruffw woodruffw merged commit 35fff1e into main Oct 20, 2025
34 checks passed
@woodruffw woodruffw deleted the rekor-version-argument branch October 20, 2025 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

expose --rekor-version in action API

2 participants