Bluehill / Jonghyo Lee
Bluehill / Jonghyo Lee
The changes do not mention NuGet lock files. That workflow doesn't work out of the box because generating a NuGet lock file requires modifying the project file.
This happened during the "temporary project" build process, so doing that in my project doesn't fix it. The fundamental solution is to remove that RID from WinAppSdk.
I don't know why the test failed. It was successful when I tested it locally.
https://github.com/dependabot/dependabot-core/blob/ddb9722dd9ed00daf54b5115ccfe033c6bb910b7/nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/LockFileUpdater.cs#L21 Oh, I think I forgot the quotation marks.
#6031 is too old. I tried to fix it, but I don't know where or how to fix it.
But I provided correct api key. Nonetheless, I received a 401 error.
According to README.md: ```yml - uses: actions/setup-dotnet@v4 with: dotnet-version: 3.1.x - name: Publish the package to nuget.org run: dotnet nuget push */bin/Release/*.nupkg -k $NUGET_AUTH_TOKEN -s https://api.nuget.org/v3/index.json env: NUGET_AUTH_TOKEN: ${{ secrets.NUGET_TOKEN...
I ignored it using a dependabot ignore command. (#9916 and na1307/SimpleSixtarScorecard#5) I have a Dependabot Actions log, but I don't know which one to link to.
> I am faced with the same issue as @na1307. I maintain a relatively big set of Java-based projects that are updated weekly by dependabot in grouped pull requests. >...
This issue seems to be resolved now: na1307/SimpleSixtarScorecard#18