You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using v1 tag results in a successful upload, Wondering if there's a difference in how either the newer versions upload, or if it's a new nodejs version issue?
Got the same error on a windows runner. File size is 1156 MB which is within the GitHub limit of max. 2GB.
Tried setting the parameters in a step before calling the github action but with no luck:
$env:NODE_OPTIONS = "--max-old-space-size=4096"
$env:NODE_OPTIONS >> $PROFILE.AllUsersCurrentHost
I've been using this action for quite a while to make releases, as part of the releases we upload a series of files to the release.
This creates the release and uploads four of the five files, it failed on the much larger file however.
👩🏭 Creating new GitHub release for tag 20240820121111.7.10.08.20...
⬆️ Uploading 1.zip...
⬆️ Uploading 2.zip...
⬆️ Uploading 3.zip...
⬆️ Uploading 4.zip...
⬆️ Uploading 5.zip...
Error: write ENOBUFS
I don't know the exact file size of the file however it will be about 1.5GB or 1573321116 bytes.
I've tried the v2 release and the latest release v2.0.
I'm using the following in the YML
EDIT: The v1 version is because I'm testing multiple versions at the moment.
The text was updated successfully, but these errors were encountered: