# What changed in @azure/functions

> 6 changes in @azure/functions 4 from its official release notes, upgrade guides and advisories: 2 security, 2 new APIs and options. Each one cited. Sources checked 2026-10-19. HTML: https://unstale.sh/npm/@azure/functions/

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

## @azure/functions 4

### Security

- HTTP proxy header handling was hardened. (4.16.4) — [release notes](https://github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.16.4)
- Serialized library errors are sanitized. (4.16.4) — [release notes](https://github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.16.4)

### New APIs and options

- Support was added for CosmosDb ChangeFeed. (4.16.4) — [release notes](https://github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.16.4)
- An SDK binding option was added for Service Bus topic triggers. (4.16.4) — [release notes](https://github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.16.4)

### Fixes and other changes

- The name of AllVersionsAndDeletes changed; the notes do not specify the replacement name. (4.16.5) — [release notes](https://github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.16.5)
- GET and HEAD request bodies no longer fail before reaching the handler. (4.16.4) — [release notes](https://github.com/Azure/azure-functions-nodejs-library/releases/tag/v4.16.4)