Skip to content

fix gpg release workflow by removing vestigial fingerprint var#530

Open
grokspawn wants to merge 1 commit into
operator-framework:mainfrom
grokspawn:fix-gpg-release
Open

fix gpg release workflow by removing vestigial fingerprint var#530
grokspawn wants to merge 1 commit into
operator-framework:mainfrom
grokspawn:fix-gpg-release

Conversation

@grokspawn
Copy link
Copy Markdown
Contributor

Vestigial GPG_FINGERPRINT variable in the deployment workflow, which isn't set because there is no import_gpg workflow, so the field evaluation fails.

Signed-off-by: grokspawn <jordan@nimblewidget.com>
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.71%. Comparing base (08ab7fb) to head (8e9e355).
⚠️ Report is 150 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (08ab7fb) and HEAD (8e9e355). Click for more details.

HEAD has 1 upload less than BASE
Flag BASE (08ab7fb) HEAD (8e9e355)
2 1
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #530       +/-   ##
===========================================
- Coverage   85.06%   74.71%   -10.35%     
===========================================
  Files          19       31       +12     
  Lines        1346     2037      +691     
===========================================
+ Hits         1145     1522      +377     
- Misses        125      433      +308     
- Partials       76       82        +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@grokspawn
Copy link
Copy Markdown
Contributor Author

/hold
this might be valid, but the gpg signing key has expired, and this won't resolve it.

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/infra area/sdk do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants