@octokit/openapi-types
29.0.1 · 29 Aug 2026MIT97.2M / weekRepositoryHomepagenpmAtom feed
Upgrading @octokit/openapi-types From 12.2.0 to 12.11.0
12 releases in betweenevery note read
- 2
- changes to make
- 0
- advisories fixed
- 24
- new
- 9
- fixes
Before you upgrade
Tick each one off as you go- Breaking12.6.0
- Breaking12.5.0
Release by release
- New
New
GET /enterprises/{enterprise}/code-scanning/alertsendpoint and description updates for multiple other endpoints
- New
- New
Add example for
use_squash_pr_title_as_defaultproperty when repositories are returned in the API
- New
- New
Add new
GET /repos/{owner}/{repo}/codespaces/newAPI operation - New
Update operation parameter descriptions, operation descriptions and response examples
- New
- Fixed
Improve parameter descriptions for
GET /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers
- Fixed
- New
Improve operation descriptions when an API operation is not available in a particular context (e.g. GHAE or a GHES version)
- New
Improve parameter descriptions for
POST /authorizations,PUT /authorizations/clients/{client_id}andPUT /authorizations/clients/{client_id}/{fingerprint} - New
Add type annotations with
examples and annotations about strings'formats, where available
- New
- New
Add support for returning
dependency_snapshots-specific rate limits inGET /rate_limit - Fixed
Clarify description to make it clear that
POST /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deploymentsis only available to required reviewers
- New
- New
Add support for specifying a
namefor the forked repository when creating a fork withPOST /repos/{owner}/{repo}/forks
- New
- Fixed
Don't mark endpoints as unavailable in GHES 3.5 and GHAE which are in fact available
- Fixed
2 other lines we could not sort, mostly version bumps
- 12.7.0
When a SARIF response is explicitly requested from
GET /repos/{owner}/{repo}/code-scanning/analyses/{analysis_id}, handle it as JSON - 12.7.0
Mark
sortbynumberforGET /repos/{owner}/{repo}/code-scanning/alertsas deprecated
3 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.