Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Backport fixes for REST API version 6.0

Open
#512 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, python
Domain
api, release

Research direction

Review the v6.0.0b4 package and the referenced commit that fixed the setuptools warning, then compare fixes on the current dev branch with the supported REST API versions. Define which changes apply to Azure DevOps Server 2020 and other supported versions; done requires an agreed backport scope and corresponding versioned releases.

Written by the indexing model from the issue text.

Description

The current dev branch as well recent releases focus on version 7.0 & 7.1 of the Azure DevOps REST API ,as mentioned in the documentation of the latter.

However, it would be interesting to backport fixes on top of older versions of the library addressing other REST API versions, matching other versions of the Azure DevOps (Server) product.

For instance, the current v6.0.0b4, the latest to support the 6.0 REST API version matchin Azure DevOps Server 2020.1, does not include fixex to the python package generating warning at the setuptools level when the package is being used.
Cf. this commit.

All fixes being meta or interesting for multiple versions of the REST API would be interesting to get for all the supported product.
Azure DevOps Server 2020, for instance, is supported until 2025 (and potentially 2030).
It is incoherent support for this library moves away from otherwise supported products.

Dominant language
Python
Stars
684
Forks
218
Avg merge
8d 10h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/azure-devops-python-api

All issues in microsoft/azure-devops-python-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.