Unable to push the code to dev

[swathidhanaraj]

🏷️ Discussion Type

Question

Body

I’m unable to push the code to Dev due to an issue with nuget package

[kartik-012]

Hey, I had a look at your workflow.

From what I can see, the main problem is that the build-uipath-nuget-package step is failing. Because that step fails, GitHub automatically skips the publish-uipath-nuget-package-Dev step, so nothing gets deployed to the Dev environment.

The first thing I'd do is open the failed (❌) build job and check the error message. That will usually tell you exactly what's wrong.

If you're not sure what to look for, here are the most common reasons:

• Sometimes the GitHub runner doesn't have the NuGet feed configured, so the build can't restore the required packages.
• Another common issue is that the UiPath CLI isn't installed on the runner before the build starts.
• If you're using a private NuGet feed, you might get a 401 Unauthorized error. In that case, you'll need to configure your feed credentials using GitHub Secrets.
• It could also be a dependency issue in your project.json, especially if it's using preview or development package versions instead of stable releases.

So before changing anything, I'd recommend checking the error log from the failed build. Once you know the exact error, it'll be much easier to find the right fix.

If you can share that error log here, I'd be happy to help you figure out the exact issue.

[amrthesha213-netizen]

If the build step is failing because of a NuGet package issue, it's also worth checking whether the package source is configured correctly. A missing or incorrect NuGet feed can prevent dependencies from being restored, causing the build to fail before the publish step is reached.

Another thing to verify is that the package versions referenced in the project are available in the configured feed. If a package was removed or the version doesn't exist, the restore process will fail.

The publish job being skipped is expected behavior since it depends on the build job completing successfully. The build log should contain the specific NuGet error that points to the root cause.