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

chore: bump opa to 0.42.2 #237

Merged
merged 2 commits into from
Jul 19, 2022
Merged

Conversation

sozercan
Copy link
Member

Signed-off-by: Sertac Ozercan sozercan@gmail.com

@sozercan sozercan requested a review from maxsmythe July 12, 2022 23:00
@sozercan sozercan changed the title chore: bump opa to 0.42.0 chore: bump opa to 0.42.1 Jul 12, 2022
@codecov-commenter
Copy link

codecov-commenter commented Jul 12, 2022

Codecov Report

Merging #237 (d5098c8) into master (c8f2fff) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #237   +/-   ##
=======================================
  Coverage   50.22%   50.22%           
=======================================
  Files          64       64           
  Lines        4255     4255           
=======================================
  Hits         2137     2137           
  Misses       1879     1879           
  Partials      239      239           
Flag Coverage Δ
unittests 50.22% <ø> (ø)

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


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c8f2fff...d5098c8. Read the comment docs.

@sozercan sozercan requested a review from a team July 19, 2022 20:10
@sozercan sozercan changed the title chore: bump opa to 0.42.1 chore: bump opa to 0.42.2 Jul 19, 2022
Signed-off-by: Sertac Ozercan <sozercan@gmail.com>
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

3 participants