Transition to azure-devops from vsts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 59
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
The legacy `vsts` library relies on `setuptools` < 81, and we've set our dependency requirements accordingly (see https://github.com/llnl/scraper/pull/85).
A [recently reported `setuptools` vulnerability](https://nvd.nist.gov/vuln/detail/CVE-2026-59890) calls for an update to 83.0.0, which would break `vsts`.
Our best bet is probably to make the move to [`azure-devops`](https://github.com/microsoft/azure-devops-python-api).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the legacy vsts library, setuptools requirements, and the azure-devops Python API, but no repository files or tests. Start by locating vsts imports and dependency declarations, then compare the required API usage with azure-devops. Done means the project no longer depends on vsts and remains compatible with setuptools 83.0.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100