release: 0.39.0

[stainless-app]

Automated Release PR

0.39.0 (2026-06-13)

Full Changelog: v0.38.0...v0.39.0

Features

• api: api update (c36a0af)
• api: api update (f4552e6)
• api: api update (ac06265)
• api: api update (aece11c)
• api: api update (16484dc)
• api: api update (eb85299)
• api: api update (7465b15)
• api: api update (898829a)
• api: api update (c31c296)
• api: api update (8958b49)
• api: api update (10386a3)
• api: api update (e1f12f8)
• api: api update (700d0af)
• api: api update (d4b2496)
• api: manual updates (93a95b4)
• api: manual updates (dc0c039)
• support setting headers via env (0e3b514)

Bug Fixes

• typescript: upgrade tsc-multi so that it works with Node 26 (bb51450)

Chores

• avoid formatting file that gets changed during releases (cf52108)
• format: run eslint and prettier separately (43ec88d)
• internal: codegen related update (f6cdc59)
• internal: more robust bootstrap script (dd48b06)
• internal: update docs ordering (9ac7b35)
• redact api-key headers in debug logs (9ccb5ff)
• restructure docs search code (8a752b4)
• tests: remove redundant File import (1f3a018)
• update SDK settings (5f5049a)

Documentation

• update http mcp docs (6f8f5a6)

---

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

[stainless-app]

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/hyperspell-typescript/ac062652e4c9a7e3f11b7920668f2e1d20f66f24/dist.tar.gz'

Expires at: Sat, 11 Jul 2026 17:32:40 GMT
Updated at: Thu, 11 Jun 2026 17:32:40 GMT

[canaries-inc]

🐤 Canary Summary

This is an automated release PR with no UI/UX changes:

• Version bumped from 0.38.0 to 0.38.1 across all package files
• Updated npm publishing workflow authentication from OIDC to token-based
• Modified release scripts to use NPM_TOKEN environment variable
• Updated changelog and configuration metadata
• No user-facing UI components, styling, or application logic affected

---

---

View PR tests on Canary

[canaries-inc]

🐤 Canary Proposed Tests

No testable user journeys found for this PR.

[entelligence-ai-pr-reviews]

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this appears to be a standard release bump to version 0.38.1 with no identified logic, security, or correctness issues surfaced during review. The automated analysis found zero critical, significant, or medium-severity issues across the reviewed files. While only 4 of 13 changed files received coverage, the absence of any flagged concerns and the nature of a patch release (typically containing minor fixes or version metadata updates) supports a clean merge.

Key Findings:

• No new review comments were generated, indicating no obvious logic bugs, security vulnerabilities, or correctness issues were detected in the analyzed code.
• The PR is a patch release (0.38.1), which typically involves version string updates, changelog entries, and minor bug fixes rather than high-risk architectural changes.
• Zero unresolved pre-existing comments were carried into this review, meaning there is no backlog of known issues being deferred.
• 4 of 13 changed files were reviewed by the heuristic analysis — the unreviewed files represent a minor blind spot, but for a release PR this risk is generally low.

[entelligence-ai-pr-reviews]

EntelligenceAI PR Summary

Releases v0.39.0 with a major Hyperdoc type system overhaul and new API capabilities across memories and evaluate resources.

• src/resources/shared.ts: Replaced Notification, Resource, ResourcesCursorPage with a 12-type discriminated Document union and 25+ Hyperdoc block node types; expanded QueryResult with provenance, query, documents fields
• src/resources/memories.ts: Replaced Memory with MemoryListResponse/MemoryGetResponse/MemoryListResponsesCursorPage; changed effort from numeric to 'minimal'|'low'|'medium'|'high'|'very_high' enum; added provenance and recency_half_life_days to search options; added 8 new source providers (granola, fathom, fireflies, linear, hubspot, salesforce, coda, lightfield)
• src/client.ts: Added HYPERSPELL_CUSTOM_HEADERS env-var support (newline-delimited key: value pairs merged into defaultHeaders); updated type re-exports to match new model
• api.md / packages/mcp-server/src/local-docs-search.ts: Updated documentation and local search index to reflect new types, response schemas, and the new evaluate.listQueries paginated endpoint
• .stats.yml: Bumped configured_endpoints to 31 with updated spec hashes

---

Confidence Score: 2/5 - Changes Needed

Not safe to merge — while this PR delivers a substantial and coherent API overhaul (Hyperdoc type system, discriminated unions, expanded QueryResult), three unresolved pre-existing issues in supporting scripts pose real reliability and correctness risks. Specifically, bin/publish-npm fails to catch an empty-string NPM_TOKEN, scripts/fast-format guards on the file-path variable $FILE_LIST rather than the file's contents causing prettier to hang on empty input, and scripts/utils/postprocess-files.cjs has a ts-ignore replacement that alters character counts and breaks declaration maps. These are not introduced by this PR but remain unresolved and could cause broken releases or corrupted build artifacts when this version ships.

Key Findings:

• In bin/publish-npm, the NPM_TOKEN empty-string case is not caught by the existing guard, meaning a misconfigured CI environment could silently attempt an unauthenticated publish rather than failing fast — a reliability risk for a release PR.
• In scripts/fast-format, the conditional at L31-L37 tests $FILE_LIST (a file path string, always non-empty) instead of whether the file contains any paths, so prettier will be invoked with no files and hang or behave unexpectedly on clean branches.
• In scripts/utils/postprocess-files.cjs L23-L41, replacing ts-ignore comments changes the byte offset of subsequent characters, which invalidates source map / declaration map positions — this is a correctness bug that could produce misleading type errors for consumers of the published package.
• The core type-system changes in src/resources/shared.ts and src/resources/memories.ts appear well-structured (discriminated unions, cursor page renames), but the broken release tooling means the package as published may be malformed or unpublishable.
• 1 previous unresolved comment(s) likely resolved in latest diff (score-only signal; thread status unchanged)

Files requiring special attention

• bin/publish-npm
• scripts/fast-format
• scripts/utils/postprocess-files.cjs

[entelligence-ai-pr-reviews]

File: tests/api-resources/memories.test.ts

Test exercises provenance=true with effort='minimal', contradicting documented constraint

src/resources/memories.ts:598-604 documents provenance as 'effort=very_high only', but tests/api-resources/memories.test.ts:163+200 sends provenance=true alongside effort='minimal'. The test validates a combination the API docs say is unsupported, giving callers a false model of the API contract.

Prompt to fix with AI

Copy this prompt into your AI coding assistant to fix this issue.

In tests/api-resources/memories.test.ts, the search test at line 159 sets effort: 'minimal' but also passes provenance: true at line 200. The src/resources/memories.ts JSDoc for the provenance field states it is 'effort=\'very_high\' only'. Either change the test to use effort: 'very_high' to match the documented constraint, or remove the constraint note from the JSDoc if the API actually accepts provenance at any effort level.