-
Notifications
You must be signed in to change notification settings - Fork 101
[BUG] Error: 😭 error: File does not exist (1). #76
[BUG] Error: 😭 error: File does not exist (1). #76
Comments
Got the same problem. |
Got the same issue.. Nothing has changed in my action script |
Same issue |
NuGet/Home#11601 |
Same problem here. I have fixed it by removing references to this project and just pushing manually. I previously had this in my workflow file:
And I have replaced it with this:
|
Missing |
Also checking if never version then check in else ignore? |
Also fixed it with doing it manual like @VAllens.. I used this (for .net): `name: Release Master NuGet on: jobs:
|
Good job. name: NuGet Publish
on:
pull_request:
types: [ closed ]
branches: [ main ]
jobs:
build:
runs-on: ubuntu-latest
if: github.event.pull_request.merged == true
steps:
- uses: actions/checkout@v2
- name: Setup .NET
uses: actions/setup-dotnet@v1
with:
dotnet-version: 6.0.x
- name: Restore Obfuscation.Tasks project dependencies
run: dotnet restore src/Obfuscation.Tasks/Obfuscation.Tasks.csproj
- name: Build Obfuscation.Tasks project
run: dotnet build src/Obfuscation.Tasks/Obfuscation.Tasks.csproj --no-restore --configuration Release
- name: Pack Obfuscation.Tasks project
run: dotnet pack src/Obfuscation.Tasks/Obfuscation.Tasks.csproj --no-build --configuration Release --include-symbols -p:SymbolPackageFormat=snupkg -o .
- name: Publish package to NuGet
run: dotnet nuget push *.nupkg --api-key ${{secrets.NUGET_API_KEY}} --source "https://api.nuget.org/v3/index.json" --skip-duplicate
- name: publish package to GitHub
run: dotnet nuget push *.nupkg --api-key ${{secrets.PUBLISH_TO_GITHUB_TOKEN}} --source "https://nuget.pkg.github.com/VAllens/index.json" --skip-duplicate |
Same issue here, however, the packaged was published successfully |
Same error message with the package being published successfully. I recently changed from .net 5 to 6:
to
Maybe that triggered the error message. |
For those having the same problem, It seems to be a dotnet 6 topic.
|
You can use version 3.0.3 of this fork https://github.com/alirezanet/publish-nuget which among others includes a fix for this issue |
There are a mountain of forks for this action. It would be really great if we identified and settled on one as the new "source of truth" for publishing to NuGet from GitHub Actions, since this repository seems to be abandoned. |
I still don't see why use a Github action to push to nuget while you can achieve that by writing some lines? I abandoned the usage of this action and I'm using a native dotnet commands to push to nuget |
I'm now also using dotnet command to push to nuget. |
The advantage is that it checks whether the version in |
update of action script to fix internal bug, see brandedoutcast/publish-nuget#76
This is still an issue. |
There is a good fork of it. Simply replace this part in your workflow with alirezanet/publish-nuget@v3.0.4 and your are done |
Yeah I'll either do that or just drop it and use dotnet nuget push. |
If other functions of this workflow like tagging are not needed, using |
Per the Thread here, I kept getting "error: File does not exist (1)." but this other Fork resolves it as noted by the 11 Stars on it (vs many other random forks). - brandedoutcast/publish-nuget#76 (comment)
Changed the action used for CD, see brandedoutcast/publish-nuget#76, which was generating false fails.
Problem solved for me. Your dotnet-version of the job is must be same to dotnet version of your project. dotnet version of my project is 5.0 but dotnet version in my job is 6.0.x. I changed version 6.0.x to 5.0.x in the job. |
error caused by brandedoutcast/publish-nuget#76
The push was successful, but I received an exception:
Error: 😭 error: File does not exist (1).
My
publish.yml
:console log:
here: https://github.com/VAllens/Obfuscation.Fody/runs/5226354030?check_suite_focus=true
The text was updated successfully, but these errors were encountered: