What makenotion/notion-sdk-js shipped
Written by FoxPlug from the repository's own releases; not affiliated with Notion. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/makenotion/notion-sdk-js; Notion did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- Typed endpoints now accept a betas option so a single call can opt into a Notion API beta. Pull request #838
- Version 5.31.0 lets views.create and views.update accept typed filters, sorts and quick filters in TypeScript. Release
- Version 5.31.1 cuts 1,712 bytes from the TypeScript declarations by sharing page property and list response types. Release
- Enhanced Markdown v1 is marked deprecated in the README and in page and comment descriptions, with guidance on when the default changes and how to test v2. Pull request #840
- The pagination helper comments now name
start_cursorinstead ofnext_cursoras the request argument. Pull request #837 - A new PUBLISHING.md documents the version bump, CI and PR approval, npm publishing and release note steps, linked from CONTRIBUTING.md. Pull request #831
- Publish runs now check the exact version on npm first and skip install, build and test when it is already published, and releases queue without cancelling each other. Pull request #829
- CI now cancels superseded runs on the same pull request while main-branch, scheduled and manual runs keep going. Pull request #833
- The link checker is replaced with Lychee, which checks tracked Markdown files together and catches broken heading anchors. Pull request #835
- The unused Biome configuration file is removed since the repo uses ESLint and Prettier. Pull request #832
Why it matters
This week gives TypeScript users working view filters and sorts plus per-request beta flags, and trims the shipped declarations. It also makes the project easier to maintain: publishing steps are written down, redundant publish builds are skipped, and superseded CI runs are cancelled so feedback arrives sooner.
Changelog entry
- Typed endpoints accept a betas option for per-request beta flags. Pull request #838
- V5.31.0: views.create and views.update accept typed filters, sorts and quick filters. Release
- V5.31.1: 1,712 fewer bytes of TypeScript declarations through shared page property and list response types. Release
- Page create and update share one generated property type; search and data source query share one list response type; imports and methods unchanged. Pull request #843
- Enhanced Markdown v1 marked deprecated in the README and generated page and comment descriptions. Pull request #840
- Pagination helper comments corrected to name
start_cursoras the request argument. Pull request #837 - View request types regenerated from the API schema so view creation and data source queries share filter and sort types. Pull request #841
- PUBLISHING.md added with version bump, CI, publishing and release note steps, linked from CONTRIBUTING.md. Pull request #831
- Publish runs skip install, build and test when the version is already on npm; releases queue without cancelling active runs. Pull request #829
- CI cancels superseded pull request runs; main-branch, scheduled and manual runs are unaffected. Pull request #833
- Link checker replaced with Lychee, now covering broken heading anchors. Pull request #835
- Unused Biome configuration file removed. Pull request #832
V5.31.0 types view filters and sorts in TypeScript. v5.31.1 trims 1,712 bytes of declarations. Typed endpoints take per-request betas. Enhanced Markdown v1 is now marked deprecated, with a guide to testing v2.
Two releases this week. v5.31.0 makes views.create and views.update accept typed filters, sorts and quick filters in TypeScript. v5.31.1 trims 1,712 bytes of declarations by sharing one type for page properties across create and update, and one list response type across search and data source queries, with no change to existing imports or client methods. Typed endpoints now accept a betas option so a single call can opt into a Notion API beta. Enhanced Markdown v1 is marked deprecated in the README and generated descriptions, with guidance on when the default changes and how to test v2. On the maintenance side, a new PUBLISHING.md documents the release process, publish runs skip work when the version is already on npm, and CI cancels superseded pull request runs.
Week of October 26, 2026
What shipped
- V5.30.0 released, requiring Node.js 22 or later and dropping support for all earlier Node.js versions. Release
- Common API types such as rich text, filter, icon, date, schema and client options are now exported from the package root, along with QueryDataSourceFilter and QueryDataSourceSort aliases. Pull request #822
- Comment responses and the comment.created, comment.updated and comment.deleted webhook payloads now carry an optional
property_idthat is present for comments on a database page property and omitted for ordinary comments. Pull request #820 - ExtractNotionId and extractDatabaseId now return the database ID from the path for database links that have no title slug, instead of the side-peek page ID from p=. Pull request #819
- Webhook signature checks now use the global Web Crypto API and crypto.subtle.verify, with the Node crypto fallback and cached provider removed and public APIs and the HMAC-SHA256 algorithm unchanged. Pull request #827
- Every CI, Semgrep, version-bump and publish workflow job is now capped at 10 minutes so stalled runs stop while normal runs keep headroom. Pull request #834
- Development now defaults to Node 24, CI tests Node 22, 24 and 26, and installs use npm ci. Pull request #823
- Dependency installs now skip packages published in the last 24 hours via a release-age cooldown, require npm 11.10 or later for source checkouts, pin npm 11.21.1 in install workflows, and update SHA-pinned CI actions. Pull request #826
- The SDK now uses TypeScript 6.0.3 with ESLint moved to flat configuration, and ESLint, Jest, typescript-eslint, ts-jest and lint-staged are updated. Pull request #825
- Development dependencies are updated and pinned, with Prettier at 3.9.10, cspell at 10.4.0 and Markdown link check at 3.15.0, plus compatible audit fixes. Pull request #824
Why it matters
The v5.30.0 release makes Node.js 22 the minimum, so anyone on an older runtime has to upgrade before taking this version. The same release cuts the need for deep imports by exporting common API types from the package root. A fix for database links without a title slug also changes which ID extraction helpers return for those links, so check any code that relied on the previous value.
Changelog entry
- V5.30.0: Node.js 22 or later is now required; support for earlier versions is dropped. Release
- Export rich text, filter, icon, date, schema and client options types from the package root, plus QueryDataSourceFilter and QueryDataSourceSort aliases. Pull request #822
- Add optional
property_idto comment responses and comment webhook payloads; ordinary comments omit it. Pull request #820 - ExtractNotionId and extractDatabaseId return the database ID from the path for links without a title slug. Pull request #819
- Use global Web Crypto and crypto.subtle.verify for webhook signature checks; no public API change. Pull request #827
- Cap all CI, Semgrep, version-bump and publish workflow jobs at 10 minutes. Pull request #834
- Require Node 22, default development to Node 24, and test Node 22, 24 and 26 in CI using npm ci. Pull request #823
- Skip npm packages published in the last 24 hours and pin npm 11.21.1 across install workflows; update SHA-pinned CI actions. Pull request #826
- Upgrade to TypeScript 6.0.3 with ESLint flat configuration and update ESLint, Jest, typescript-eslint, ts-jest and lint-staged. Pull request #825
- Update and pin development dependencies: Prettier 3.9.10, cspell 10.4.0, Markdown link check 3.15.0, plus audit fixes. Pull request #824
V5.30.0 is out. Node.js 22 or later is now required. Common API types are exported from the package root, so rich text, filter, icon, date, schema and client options types no longer need deep imports. Database links without a title slug now resolve to the database ID in extractNo
V5.30.0 of the Notion SDK for JavaScript is released. The breaking change is that Node.js 22 or later is now required, and support for all earlier versions has been dropped, so upgrade your runtime before updating. New capabilities in this release: common API types, including rich text, filter, icon, date, schema and client options, are now exported from the package root, along with QueryDataSourceFilter and QueryDataSourceSort aliases, so you no longer need deep imports to name these values. Comment responses and comment webhook payloads now include an optional property_id, set for comments on a database page property and omitted for ordinary comments. extractNotionId and extractDatabaseId now return the database ID for links that have no title slug, rather than the side-peek page ID. Web
More from makenotion/notion-sdk-js on GitHub
Merged pull requests
- Block Notion tokens in a browser unless dangerouslyAllowBrowser is set (#791, merged September 25, 2026 by ksinder) (source)
- [SDK] Add typed Skills and plugin directory methods (#804, merged September 16, 2026 by notion-software-lab) (source)
- [SDK] Check compatibility before refactors ship (#783, merged August 28, 2026 by ksinder) (source)
- [SDK] Generate endpoint methods without changing the public API (#781, merged August 28, 2026 by ksinder) (source)
- [SDK] Complete custom-agent client facade (#769, merged August 15, 2026 by hallie) (source)
- Fix
isFullDataSourceandisFullDatabaseaccepting partial responses (#764, merged August 13, 2026 by ksinder) (source)