# What changed in expo-server-sdk

> 10 changes in expo-server-sdk 4 to 8 from its official release notes, upgrade guides and advisories: 6 breaking, 1 deprecations, 3 new APIs and options. Each one cited. Sources checked 2026-11-03. HTML: https://unstale.sh/npm/expo-server-sdk/

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

## expo-server-sdk 8

### Breaking changes

- The SDK now uses the global fetch instead of undici's. (8.0.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v8.0.0)

## expo-server-sdk 7

### Breaking changes

- Node v20.x, v21.x, and v22.x below v22.12.0 are no longer supported. (7.0.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v7.0.0)

### Deprecations

- Deprecates _contentAvailable in favor of contentAvailable. (7.1.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v7.1.0)

### New APIs and options

- Adds support for new APNs fields. (7.2.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v7.2.0)
- Adds the threadId parameter. (7.1.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v7.1.0)

## expo-server-sdk 6

### Breaking changes

- The package is built as an ECMAScript module, changing its module format for developers using it. (6.0.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v6.0.0)

### New APIs and options

- Adds new options for collapsing push notifications. (6.1.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v6.1.0)

## expo-server-sdk 5

### Breaking changes

- Replaces node-fetch with undici as the HTTP client. (5.0.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v5.0.0)
- The useFcmV1 option was removed, so developers can no longer use it. (5.0.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v5.0.0)

## expo-server-sdk 4

### Breaking changes

- Support for Node v18.x was dropped, so applications using this SDK must run on a supported Node.js version. (4.0.0) — [release notes](https://github.com/expo/expo-server-sdk-node/releases/tag/v4.0.0)