Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Teams API drift advisory: 2.0.16 to 2.1.0

Abierto
  • ¿Algo no está bien?
#605 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
api, backend

Línea de trabajo

Start by reviewing the pinned microsoft-teams-api dependency and the ApiClient construction sites in microsoft_agents/hosting/msteams/_teams_api_client.py, teams_agent_extension.py, and teams_turn_context.py. Compare the constructor contract with version 2.1.0 and confirm the required scope with a maintainer before changing anything. Done means the approved compatibility decision is implemented and the relevant build and contract checks pass.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

teams.api Impact Report

Summary

This is an advisory report; it does not make or authorize implementation decisions. Comparing microsoft-teams-api 2.0.16 to 2.1.0 for microsoft-agents-hosting-msteams surfaced 1 blocking finding, 0 required findings, and 8 review findings (2 feature-review, 3 internal-opportunity, 3 general maintainer-decision). All supplied build/test checks succeeded, and 119 additional changes were classified as requiring no action.

Compatibility breaks

  • TSAPI-0069 — Advisory: The microsoft_teams.api.clients.api_client.ApiClient.__init__ constructor has changed and is classified as blocking. This consumed contract is instantiated in microsoft_agents/hosting/msteams/_teams_api_client.py, microsoft_agents/hosting/msteams/teams_agent_extension.py, and microsoft_agents/hosting/msteams/teams_turn_context.py, and must be adapted before adopting the candidate version.

Required adaptations

  • No findings in this category.

Feature-review candidates

  • TSAPI-0126, TSAPI-0127 — Advisory: New file-download-info symbols (FILE_DOWNLOAD_INFO_CONTENT_TYPE and FileDownloadInfo) were added upstream under the file-consents capability area. No directly affected source file was identified; evidence does not establish an existing consumption point or migration path, so maintainer review is needed to decide whether to adopt these into the file-consent handling surface.

Internal implementation opportunities

  • TSAPI-0066, TSAPI-0067, TSAPI-0068 — Advisory: New agentic-identity symbols (AGENTIC_IDENTITY_CLEAR, AgenticIdentityClear, AgenticIdentityScope) were added under microsoft_teams.api.clients, within the teams-api-client capability area. No directly affected source file was identified; adoption would require a maintainer decision on whether these support an internal implementation opportunity.

Maintainer decisions

  • TSAPI-0070, TSAPI-0071, TSAPI-0072 — Advisory: New methods were added to microsoft_teams.api.clients.api_client.ApiClient (clone, for_agentic_identity, from_service_url), affecting microsoft_agents/hosting/msteams/_teams_api_client.py, microsoft_agents/hosting/msteams/teams_agent_extension.py, and microsoft_agents/hosting/msteams/teams_turn_context.py where ApiClient is instantiated. These are additive and non-blocking per supplied evidence, but a maintainer decision is needed on whether to expose or leverage them.

No action

  • 119 additional changes require no action.

Suggested implementation issues

  • TSAPI-0069 — Advisory: Consider opening an issue to update the ApiClient construction sites in _teams_api_client.py, teams_agent_extension.py, and teams_turn_context.py to match the changed constructor signature ahead of any adoption of 2.1.0. This is a proposal only and does not constitute authorization to implement.
  • TSAPI-0070, TSAPI-0071, TSAPI-0072 — Advisory: Consider opening an issue to evaluate whether clone, for_agentic_identity, or from_service_url should be surfaced through the teams-api-client capability's owner files. This is a proposal only; supplied evidence does not establish a required migration path.

Validation checklist

  • Supplied checks reported success for apiComparison, apiExtraction, boundaryTests, build, contractTests, and usageCollection; these outcomes are deterministic evidence only and do not by themselves confirm runtime compatibility of the blocking ApiClient.__init__ change.
  • The candidate version differs from the extension's pinned dependency (==2.0.16); confirm dependency pinning strategy before any adoption, since tests were run in a disposable environment against the candidate rather than the pinned version.
  • No boundary or contract test failures were reported in the supplied evidence, but no test results specific to the changed ApiClient constructor or the new methods were provided — behavior of these should be verified explicitly rather than assumed from the aggregate "success" status.

Workflow artifacts

Lenguaje dominante
Python
Estrellas
212
Forks
91
Merge medio
1 d 19 h
PR fusionados (30 d)
22

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/Agents-for-python

Todos los issues de microsoft/Agents-for-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.