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
✖ [publisher-s3] Running the publish command [FAILED: ENOENT: no such file or directory, open 'C:\actions-runner_work\Wallets\Wallets\Wallets\MyProject{PROJECT}\out\make\squirrel.windows\x64{PROJECT}-14.0.0-delta.nupkg']
✖ Publishing distributables [FAILED: ENOENT: no such file or directory, open 'C:\actions-runner_work\Wallets\Wallets\Wallets\MyProject{PROJECT}\out\make\squirrel.windows\x64{PROJECT}-14.0.0-delta.nupkg']
only a {PROJECT}-14.0.0-full-nupkg is created.
the RELEASES file is empty in the aws.
The text was updated successfully, but these errors were encountered:
I just ran into this as well and the following worked for me.
For the first release:
Create an empty file called RELEASES at the same path that the s3 publisher publishes the objects to. Note that @electron-forge/publisher-s3 uploads objects to this path by default.
Point the Squirrel.Windows remoteReleases option to the same directory you created RELEASES in.
Set the Squirrel.Windows option noDelta to true.
For subsequent releases:
Set the Squirrel.Windows option noDelta to false.
The delta file will then be generated for all releases after the first.
delta update for nuget is not created:
✖ [publisher-s3] Running the publish command [FAILED: ENOENT: no such file or directory, open 'C:\actions-runner_work\Wallets\Wallets\Wallets\MyProject{PROJECT}\out\make\squirrel.windows\x64{PROJECT}-14.0.0-delta.nupkg']
✖ Publishing distributables [FAILED: ENOENT: no such file or directory, open 'C:\actions-runner_work\Wallets\Wallets\Wallets\MyProject{PROJECT}\out\make\squirrel.windows\x64{PROJECT}-14.0.0-delta.nupkg']
only a {PROJECT}-14.0.0-full-nupkg is created.
the RELEASES file is empty in the aws.
The text was updated successfully, but these errors were encountered: