# What changed in @octokit/graphql

> 6 changes in @octokit/graphql 5 to 9 from its official release notes, upgrade guides and advisories: 6 breaking. Each one cited. Sources checked 2026-10-26. HTML: https://unstale.sh/npm/@octokit/graphql/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## @octokit/graphql 9

### Breaking changes

- Drops support for NodeJS v18 and sets the minimum Node version to v20. (9.0.0) — [release notes](https://github.com/octokit/graphql.js/releases/tag/v9.0.0)

## @octokit/graphql 8

### Breaking changes

- The package is now ESM, which changes how developers consume it. (8.0.0) — [release notes](https://github.com/octokit/graphql.js/releases/tag/v8.0.0)

## @octokit/graphql 7

### Breaking changes

- Custom request options can no longer be passed, except for method, headers, body, signal, and data. (7.0.0) — [release notes](https://github.com/octokit/graphql.js/releases/tag/v7.0.0)
- Support for Node.js http(s) Agents was replaced with documentation on using fetch dispatchers instead. (7.0.0) — [release notes](https://github.com/octokit/graphql.js/releases/tag/v7.0.0)

## @octokit/graphql 6

### Breaking changes

- Support for NodeJS v14 and v16 was dropped. (6.0.0) — [release notes](https://github.com/octokit/graphql.js/releases/tag/v6.0.0)

## @octokit/graphql 5

### Breaking changes

- Support for NodeJS v10 and v12 was dropped. (5.0.0) — [release notes](https://github.com/octokit/graphql.js/releases/tag/v5.0.0)