dynamic / submit-nuget workflows being injected into my PRs as of 2025-07-01

[ReenigneArcher]

Select Topic Area

Bug

Body

GitHub is injecting some kind of nuget workflow into my repos/PRs.

From what I can find this is from the Automatic dependency submission setting under Advanced Security repository settings; however based on what I've read (https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-automatic-dependency-submission-for-your-repository) this should only occur if a pom.xml file is updated or something along those lines.

Pushing a commit which updates pom.xml will trigger a new run of the Dependency Tree Submission action and force a rebuild of that repository's dependency graph.

My repos have no such file, nor is one being added in these PRs.

• feat(docker)!: adjust artifact and release logic LizardByte/.github#475
• ci(workflows): refactor ci LizardByte/Sunshine#4025

Edit: To clarify I do not have any nuget projects and therefore would prefer not to have this failed check appearing for no reason. In the meantime I have disabled automatic dependency submission altogether which is probably not ideal; however it's better than annoying failures that don't apply.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[MartiUK]

This was enabled for NuGet packages yesterday (2025-07-01): https://github.blog/changelog/2025-07-01-dependency-auto-submission-now-supports-nuget/

Now this is all well and all as we'd like to publish our NuGet dependencies. Though we're having an issue with this where the workflow doesn't request permissions, and so, fails to restore the projects because it can't access NuGet packages hosted on GitHub.

A pretty obvious oversight, eh, GitHub?

[ReenigneArcher]

Yea, though I have no NuGet packages in any of my repos, and now I'm getting this failure in all PRs across all repos 😆

[isaacegglestone]

I mean the problem seems to be it does use the default GITHUB_TOKEN, but if your org has SSO enabled and required, then it breaks because GITHUB_TOKEN isn't SSO authorised.

See the top of the workflow log, you should see GITHUB_TOKEN mentioned there.
I can't find anyway to configure it except disabling it and running it manually as a workflow.

[KoushikKatrapally25]

Even I have the same issue where this has enabled yesterday just check the change log : https://github.blog/changelog/2025-07-01-dependency-auto-submission-now-supports-nuget/#:~:text=In%20order%20to%20use%20this,feature%20will%20incur%20actions%20usage.

If GitHub can give us solution to this it would be great

We have few repos where the manifest file is located not in root of the repo but its on the other folders

Just want to check if Automatic dependency submission works for the multimodule project like maven-dependency-submission-action ?

[Nikolajls]

Im facing an issue where the dotnet project being restored has a nuget.config file that tells what packages should be fetched from github.
The file also needs a token that allows it to access the nuget packages in our repository in the organization.
Something our own build steps normally adds and works all fine and dandy.

I cannot see anyway to configure this new added thingy which is rather annoying.

[MartiUK]

Yeah this is the exact issue we're having

[dkattan]

Us too

[Designer225]

It's nice to see automatic dependency submission support NuGet now.

However, when the action ran on my (private) project for the first time, I ran into an issue where it fails because it did not have certain .NET workloads installed:

It would be great for the action to support restoring workloads first, or alternatively allow configuring the action so that it can happen first.

[Christian-Schou]

Same thing happening to our projects now across PRs. dynamic / submit-nuget (dynamic) Failing. It can't restore projects where other NuGet packages going into the projects, are located in a private GitHub package registry. GitHub please fix this as soon as possible, our workflows are failing due to this release.

[ReenigneArcher]

Now I am getting this even though I have "Automatic dependency submission" disabled.

Again, this is not even a nuget project, nor does it have any nuget files in it that might confuse GitHub into thinking it's a nuget project.

[iriza841]

Hi,

I'm having this same issue because I have a submodule and I need to provide a token to access it

[isaacegglestone]

Github support finally came back on this and told us it wasn’t supported anymore on private repos. Finally i realised the action that was running was actually caused by github changing a default setting which kicked off this pipeline in many of our repos that didn’t even have it previously. My solution was to just disable it at the org level since the only repos using it had their own configuration for the checks and they were still working

…

On Tue, 30 Sep 2025 at 6:36 am, iriza841 ***@***.***> wrote: Hi, I'm having this same issue because I have a submodule and I need to provide a token to access it image.png (view on web) <https://github.com/user-attachments/assets/f1108160-4372-4ca8-a74c-ed07efc68053> image.png (view on web) <https://github.com/user-attachments/assets/d1cad027-e6d9-4d38-bd10-b9ccbbae11bd> — Reply to this email directly, view it on GitHub <#164747 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACLXT5V367WS4SLX4S5ARE33VGJ4HAVCNFSM6AAAAACASHAXXSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINJUGU4DAMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[iriza841]

thank you

[bentkris]

I would be nice to hear form GitHub support, if they plan to support this security feature private nuget repos. I guess this must be a blocker for many? In my experience it is hard to make any workaround, to let the submit-nuget job have the private nuget source, because Advanced Security is running independent and in parallel on push to the repo.

[gazab]

Yes, feels like GitHub forgot about this when they added the "Private Registries" feature? It would be perfect to use that for automatic dependency submission as well.

Currently the GUI says:

Access to private registry configurations is limited to CodeQL default setup and Dependabot.