-
Notifications
You must be signed in to change notification settings - Fork 17
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
v0.6.15 coveralls-checksums.txt has incorrect path prefix (release/
)
#165
Comments
@adityasaky Thanks for the report. We are working on it now. Will update you here. |
+1 this is also affecting our team today.
|
Workarounds for nowFor users of coverage-reporter directly:Instead of this install step:
Download and install the latest working version (
Suggestion for users of the Coveralls GitHub Action:set fail-on-error input option to
Suggestion for users of the Coveralls Orb for CircleCI:set fail_on_error input option to
|
@adityasaky We believe we've patched this for now by updating the Can you please try |
Awesome. Thank you! ❤️ We're now fixing the issue for subsequent releases. |
Root cause analysis (by request) here. |
What was wrong?
We noticed coverage runs via the github action failing because the path specified in the latest release's checksums file doesn't match the location of the binary in question. It looks like the latest release includes a
release/
prefix which isn't present in at the very least the last release.Logs
Our CI run is at https://github.com/gittuf/gittuf/actions/runs/11147824919/job/30983463583?pr=578#step:5:33
The text was updated successfully, but these errors were encountered: