-
Notifications
You must be signed in to change notification settings - Fork 72
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
Input coverage-reporter-version
isn't recognized.
#225
Comments
@jesusaurus Thanks for reporting. Looking into it. Will update you here. |
Hi @jesusaurus. It looks like that input option is present in the latest version of the github-action ( However per this conditional, that input option is not available on MacOS runners, so if your runner was MacOS you would see the error message:
But that's not what you're seeing, so I'm thinking you may be referencing an older version of the github-action? Are you referencing a version older than
The
|
@afinetooth thanks for the quick response, I'm currently using |
@jesusaurus OK, got it. Likewise, thanks for confirming your usage of In that case, it does seem like a bug. We'll have a deeper look and I'll get back to you asap. |
@jesusaurus, I made some changes to the logic handling TBH, I was not able to account for what caused that error in your CI run, since, at that point, When you get a chance to try the |
@afinetooth thanks for looking into this. Still no change when using (P.S. I changed my username) |
This should be fixed now. I think the real underlying issue was this: We had fallen out of our standard pattern for releases such that our floating tag Can you please try again and let me know if it's not working as expected for you? 🙏 I'll close this until I hear otherwise from you. Thanks. |
@afinetooth awesome! |
Perfect. Thanks for confirming! |
Setting
coverage-reporter-version
has no effect other than a warning that the input isn't recognized:The text was updated successfully, but these errors were encountered: