Skip to content
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

helm: add fuzzer for provenance unmarshalling #1243

Merged
merged 1 commit into from Jan 3, 2023

Conversation

AdamKorcz
Copy link
Contributor

@AdamKorcz AdamKorcz commented Dec 14, 2022

Signed-off-by: AdamKorcz adam@adalogics.com

Summary

Adds a fuzzer for the helm type provenance unmarshalling. Adds it to the OSS-Fuzz build script.

Release Note

Documentation

@AdamKorcz AdamKorcz requested review from bobcallaway and a team as code owners December 14, 2022 14:36
bobcallaway
bobcallaway previously approved these changes Dec 14, 2022
@dlorenc
Copy link
Member

dlorenc commented Dec 26, 2022

CI looks stuck here, could you amend to try retriggering?

@AdamKorcz AdamKorcz closed this Dec 27, 2022
@AdamKorcz AdamKorcz reopened this Dec 27, 2022
@codecov-commenter
Copy link

codecov-commenter commented Dec 27, 2022

Codecov Report

Merging #1243 (fcb2229) into main (8a68186) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1243      +/-   ##
==========================================
+ Coverage   63.27%   63.29%   +0.02%     
==========================================
  Files          82       82              
  Lines        7670     7670              
==========================================
+ Hits         4853     4855       +2     
+ Misses       2205     2203       -2     
  Partials      612      612              
Flag Coverage Δ
e2etests 47.78% <ø> (ø)
unittests 42.11% <ø> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
pkg/types/rekord/v0.0.1/entry.go 68.42% <0.00%> (+0.65%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@bobcallaway
Copy link
Member

@AdamKorcz can you do git commit -s --amend and force push that here so the DCO check re-fires?

Signed-off-by: AdamKorcz <adam@adalogics.com>
@AdamKorcz
Copy link
Contributor Author

@AdamKorcz can you do git commit -s --amend and force push that here so the DCO check re-fires?

done

@bobcallaway bobcallaway merged commit 33a6feb into sigstore:main Jan 3, 2023
@github-actions github-actions bot added this to the v1.1.0 milestone Jan 3, 2023
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.

None yet

4 participants