-
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
fs undefined reading createWriteStream #22
Comments
(Same here) |
Same here, As a temporary workaround, you can pin the FOSSA action version like this:
|
Please check the attached PR. It is working with the change suggested by @anibe. Hope to get it in soon! |
Thanks for reporting this! Just testing that PR now. |
Unless I've missed something, I'm still getting this when targeting v1.3.0 on the GitHub |
@tobysmith568 can you please share the pipeline run link? |
Actually you are right, I just checked. The tag v1.3.0 does not contain the commit The release v1.3.0 is behind main by 1 commit: @himynameisdave can you please recreate the release/tag with the right commit? |
Thanks guys - 1.3.1 has now resolved this issue for me 🚀 |
Hello,
We recently noticed our builds failing the FOSSA scan due to the error below:
It appears to have been introduced with v1.2.0.
Could you please consider offering backward compatibility for build agents that don't support the new Node.js syntax?
Details of our GitHub Action runner below:
Operating System:
Ubuntu
LTS
Virtual Environment:
Environment: ubuntu-20.04
Version: 20220410.2
The text was updated successfully, but these errors were encountered: