Conversation
✅
|
echoix
left a comment
There was a problem hiding this comment.
I think bugbot's suggestions are correct if they are right, otherwise I'm supporting you with this, it is way better than without it, as nothing would work
Cursor suggestions fixed |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
MegaLinter v9.3.0 and earlier crash on startup with Python 3.13 due to AzureCommentReporter importing azure.devops which requires pkg_resources (removed from stdlib). The fix is merged in oxsecurity/megalinter#7151 but not yet released. Using :beta (tracks main branch) as a temporary workaround until v9.4.0.
MegaLinter v9.3.0 and earlier crash on startup with Python 3.13 due to AzureCommentReporter importing azure.devops which requires pkg_resources (removed from stdlib). The fix is merged in oxsecurity/megalinter#7151 but not yet released. Using :beta (tracks main branch) as a temporary workaround until v9.4.0.
pkg_resources (part of setuptools) is not included in Python 3.13 by default but is unconditionally imported by the azure-devops SDK used in AzureCommentReporter.py. This causes MegaLinter to crash at startup. Add a post-build step that layers 'pip install setuptools' on top of the built image. This is simpler and more reliable than waiting for upstream MegaLinter to publish a new image with the fix from oxsecurity/megalinter#7151 (merged 2026-02-16). Will remove this patch once a new MegaLinter release ships the fix.
pkg_resources (part of setuptools) is not included in Python 3.13 by default but is unconditionally imported by the azure-devops SDK used in AzureCommentReporter.py. This causes MegaLinter to crash at startup. Add a post-build step that layers 'pip install setuptools' on top of the built image. This is simpler and more reliable than waiting for upstream MegaLinter to publish a new image with the fix from oxsecurity/megalinter#7151 (merged 2026-02-16). Will remove this patch step once a new MegaLinter release ships the fix.

Related #4894
The Python package has been practically abandoned: https://pypi.org/project/azure-devops/#history
So I removed that dependency and used the REST API directly: https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-7.2
We currently use 6 endpoints that have been very easy to refactor and maintain in the future.
At the moment, I am using the current stable version (7.2 it's preview): 7.1
Note
Medium Risk
Changes the integration path for posting Azure PR comments (auth, endpoint URLs, and response parsing), which could break reporting in Azure environments if any REST contract/permissions differ; dependency bumps are otherwise routine.
Overview
Switches
AzureCommentReporterfrom the unmaintainedazure-devopsPython SDK to direct Azure DevOps REST calls (API7.1) usingrequests, including manual Basic auth header construction and JSON response handling.Removes
azure-devops(and transitivemsrest/OAuth deps) from project/dev dependencies and lockfile, updates docs/examples accordingly, and bumps related tool/dependency versions (langchain-core,robotframework-robocop) plus adds a new Trivy ignore entry (CVE-2026-25639).Written by Cursor Bugbot for commit f8a960b. This will update automatically on new commits. Configure here.