-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add empty global.json to dependabot #6498
Conversation
/backport to release/8.0 |
/backport to release.7.x |
Started backporting to release/8.0: https://github.com/dotnet/dotnet-monitor/actions/runs/8806170764 |
/backport to release/6.x |
Started backporting to release.7.x: https://github.com/dotnet/dotnet-monitor/actions/runs/8806171847 |
Started backporting to release/6.x: https://github.com/dotnet/dotnet-monitor/actions/runs/8806172862 |
@jander-msft an error occurred while backporting to release.7.x, please check the run log for details! Error: The specified backport target branch release.7.x wasn't found in the repo. |
/backport to release/7.x |
Started backporting to release/7.x: https://github.com/dotnet/dotnet-monitor/actions/runs/8806176882 |
Summary
Some dependabot updates are failing because it is scanning for the global.json file associated with each of the dependabot projects and finding the one at the root of the repository which contains
msbuild-sdk
entries; the dependabot updater views these SDKs as updatable dependencies but fails to update them because they really don't exist in the dependabot project. To avoid this, add an empty global.json file in theeng/dependabot
folder so that extra dependencies are not discovered.Release Notes Entry