On this page
Support
Project status#
TeamAPI is actively developed and pre-1.0. It is suitable for evaluation and version-pinned adoption, but minor releases may include announced breaking changes. See the compatibility policy before depending on a public API or machine-readable format.
| Version | Status |
|---|---|
| Latest npm release | Supported with compatible fixes and documentation updates |
main |
Development branch; may change before release |
| Earlier pre-1.0 releases | Best-effort guidance; fixes normally target the next release |
The supported Node.js versions are declared in each published package's engines field. Provider integrations also
depend on external APIs that can change independently; pin TeamAPI in automation and run teamapi doctor when a live
integration stops behaving as expected.
Getting help#
Before opening an issue:
- Reproduce the problem on the latest release when practical.
- Run the smallest relevant command with a minimal, redacted
teamapi.yml. - For provider failures, include the provider, operation, HTTP status and
teamapi doctorresult, but never a token. - Include the TeamAPI package version, Node.js version and operating system.
Use GitHub issues for reproducible bugs and feature requests. Support is provided on a best-effort basis; there is no guaranteed response time or private support channel.
Report vulnerabilities through the private process in SECURITY.md, not through a public support issue. Questions about contributing and releases belong in CONTRIBUTING.md.