Skip to content
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

Receiving message "update_note_possible" on certain dependencies which breaks the pipeline while running dependabot in ADO #1491

Closed
1 task
mouaxiong1980 opened this issue Nov 25, 2024 · 1 comment

Comments

@mouaxiong1980
Copy link

Describe the bug
When running dependabot against our repo in ADO, dependabot is able to create PRs. However, on certain packages, it is coming back with the error message:

##[Error]Update job error: update_not_possible {"dependencies":["Microsoft.Extensions.Logging"]}

I've attached a screenshot.

Categorization

Repository
URL: e.g. https://dev.azure.com/tingle/dependabot/_git/repro-684
[<!-- If credentials are required, send them to [email protected] --https://dev.azure.com/EnvisionTechnologyPartners/WebIZ/_git/WebIZ.Common

To Reproduce
Steps to reproduce the behavior:

  1. Simply running the pipeline causes the error when dependabot is running

Expected behavior
PRs are created for each group specified and as necessary.

Logs and screenshots
If applicable, include relevant logs or screenshots to help explain your problem.
[See extension troubleshooting for more on how to collect additional diagnostic logs.]

https://app.screencast.com/TlNIh6DMI6tzT

Extension (please complete the following information):

  • Host: Azure DevOps
  • Version

Server (please complete the following information):

  • Region: Not sure
  • Version

Additional context

@rhyskoedijk
Copy link
Contributor

rhyskoedijk commented Nov 26, 2024

@mouaxiong1980 this is a known issue in dependabot-core for the NuGet ecosystem. Unfortunately, there is nothing that can be done in the scope of this project to fix it. There is a detailed explanation of why this happens in dependabot/dependabot-core#10834 (comment).

Feel free to upvote and comment on the above issue to give it more attention and visibility with the dependabot-core team. Until this is fixed in dependabot-core, the only workaround is to disable your group configuration in dependabot.yml.

@mburumaxwell mburumaxwell closed this as not planned Won't fix, can't repro, duplicate, stale Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants