release: 0.35.1

[stainless-app]

Automated Release PR

0.35.1 (2026-03-28)

Full Changelog: v0.35.0...v0.35.1

Features

• api: api update (c4f9849)
• api: api update (a768bf6)
• api: api update (c684933)

Chores

• ci: escape input path in publish-npm workflow (49625b4)
• ci: skip lint on metadata-only changes (07b1ee8)
• internal: fix MCP server TS errors that occur with required client options (028a8ad)
• internal: support custom-instructions-path flag in MCP servers (08f7fe0)
• internal: support local docs search in MCP servers (c1ca54f)
• internal: update gitignore (4949619)
• internal: update multipart form array serialization (3c2ea93)
• tests: bump steady to v0.19.4 (60d723b)
• tests: bump steady to v0.19.5 (be42038)
• tests: bump steady to v0.19.6 (7241e1e)
• tests: bump steady to v0.19.7 (9d6b23b)

Refactors

• tests: switch from prism to steady (489061f)

---

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/49625b4802fcfb0d0fd3445ffceb49b057f30229/dist.tar.gz'

Expires at: Mon, 27 Apr 2026 07:38:34 GMT
Updated at: Sat, 28 Mar 2026 07:38:34 GMT

[canaries-inc]

Canary encountered an internal error while analyzing this PR.

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No new review comments were generated, indicating the PR appears clean to the automated review.
• No critical, significant, or high-risk issues were identified in the heuristic analysis.
• 8 out of 11 changed files were reviewed with zero issues flagged across all severity levels.
• No existing unresolved comments remain, suggesting previous concerns have been addressed.

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No new review comments were generated, indicating the PR appears clean from an automated review perspective.
• No critical, significant, or high-risk issues were identified in the heuristic analysis.
• 8 out of 11 changed files were reviewed with no issues found, providing reasonable coverage confidence.
• No existing unresolved comments that could indicate lingering concerns.

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No new review comments were generated, indicating the PR appears clean from an automated review perspective.
• No critical, significant, or high-risk issues were identified in the heuristic analysis.
• 15 out of 18 changed files were reviewed, providing good coverage with no issues found.
• No existing unresolved comments that would block merging.

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No critical or significant issues found
• 15/18 changed files reviewed (83% coverage)

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No critical or significant issues found
• 15/18 changed files reviewed (83% coverage)

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No new review comments were generated, indicating the PR is clean from an automated review perspective.
• No critical, significant, or high-risk issues were identified in the heuristic analysis.
• 15 out of 18 changed files were reviewed with zero issues flagged, providing good coverage confidence.
• No existing unresolved comments carry over from previous reviews that would block merging.

[stainless-app]

Release version edited manually

The Pull Request version has been manually set to 0.35.1 and will be used for the release.

If you instead want to use the version number 0.36.0 generated from conventional commits, just remove the label autorelease: custom version from this Pull Request.

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No critical or significant issues found
• 15/19 changed files reviewed (79% coverage)

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No critical or significant issues found
• 16/20 changed files reviewed (80% coverage)

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No critical or significant issues found
• 16/20 changed files reviewed (80% coverage)

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No critical or significant issues found
• 16/20 changed files reviewed (80% coverage)

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No new review comments were generated, indicating the PR is clean with no identified issues.
• No existing unresolved comments to consider, meaning there are no lingering concerns from previous reviews.
• 16 out of 21 changed files were reviewed with no issues found, providing good coverage confidence.
• Heuristic analysis shows zero critical, significant, high-risk, or medium issues detected.

[entelligence-ai-pr-reviews]

---

---

Confidence Score: 5/5 - Safe to Merge

• No new review comments were generated, indicating the PR appears clean from an automated review perspective.
• No critical, significant, or high-risk issues were identified in the heuristic analysis.
• Coverage of 16/21 changed files is reasonable, and no unresolved existing comments are blocking the merge.
• The absence of any flagged issues across all severity levels supports a safe-to-merge assessment.

[entelligence-ai-pr-reviews]

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this patch release cleanly adds gmail_actions platform support across multiple type union definitions in actions.ts, auth.ts, connections.ts, integrations.ts, web-crawler.ts, memories.ts, and shared.ts, with no logic changes that could introduce regressions. The changes are additive and low-risk: new optional fields (actions_only in IntegrationListResponse, effort in MemorySearch) and a mock server migration from Prism to Steady. No review comments were generated and heuristic analysis found zero issues across all severity levels.

Key Findings:

• All platform union type additions of 'gmail_actions' are purely additive literal extensions — existing code paths consuming these unions remain unaffected as long as exhaustiveness checks are not present, and this is a typed SDK release where such additions are expected.
• The optional effort parameter (0 = verbatim, 1 = LLM-rewrite) on MemorySearch is non-breaking due to its optional nature, and the mock server migration from Prism to Steady is a dev/test infrastructure change with no production runtime impact.
• 17 of 22 changed files were reviewed with zero issues flagged at any severity level, providing strong coverage confidence for a patch release of this scope.

Files requiring special attention

• memories.ts
• integrations.ts
• shared.ts

[entelligence-ai-pr-reviews]

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this patch release cleanly achieves its stated goals of migrating the mock server harness from Prism to Steady and extending 'gmail_actions' literal support across the relevant union types in actions.ts, auth.ts, connections.ts, integrations.ts, web-crawler.ts, memories.ts, and shared.ts. No review comments were generated across the 17 reviewed files, the heuristic analysis found zero issues at any severity level, and the changes are well-scoped additive updates (new literal in unions, health-check polling swap) with no logic mutations or breaking surface area. The PR is consistent with a standard generated SDK patch release and poses minimal risk.

Key Findings:

• The 'gmail_actions' literal addition to union types across multiple resource files (actions.ts, auth.ts, connections.ts, etc.) is purely additive and backward-compatible, posing no risk of breaking existing consumers.
• The mock server health check migration from log-file grep to HTTP polling at /_x-steady/health is a more robust and idiomatic approach, reducing flakiness in CI without altering production code paths.
• Zero issues were flagged by automated review across 17 of 22 changed files, with no critical, significant, or medium-severity concerns identified in the heuristic analysis.
• The 5 unreviewed files out of 22 are unlikely to harbor hidden issues given the pattern of the PR (SDK type generation + tooling swap), but represents a minor coverage gap that is acceptable for a patch release of this nature.

Files requiring special attention

• scripts/mock
• scripts/test
• src/resources/actions.ts
• src/resources/shared.ts

[entelligence-ai-pr-reviews]

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this patch release cleanly extends existing union types with 'gmail_actions' across actions.ts, auth.ts, connections.ts, integrations.ts, web-crawler.ts, memories.ts, and shared.ts in a consistent, additive fashion with no breaking changes. The additions of actions_only to IntegrationListResponse and effort to MemorySearchParams are optional fields that preserve backward compatibility. No review comments were generated and the heuristic analysis found zero issues of any severity across the 21 reviewed files.

Key Findings:

• All union type extensions adding 'gmail_actions' are purely additive and consistent across the affected type definition files, posing no risk of breaking existing consumers.
• The new optional effort parameter in MemorySearchParams and actions_only in IntegrationListResponse follow the existing optional field pattern, ensuring zero regression risk for current callers.
• The PR scope is well-contained to type definitions and interface extensions typical of a patch release, with no logic, algorithm, or control-flow changes that could introduce runtime issues.

Files requiring special attention

• integrations.ts
• memories.ts
• shared.ts

[entelligence-ai-pr-reviews]

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this patch release cleanly adds gmail_actions literal support across the type union definitions in actions.ts, auth.ts, connections.ts, integrations.ts, web-crawler.ts, memories.ts, and shared.ts, and introduces the optional effort parameter to MemorySearchParams and the actions_only boolean flag to IntegrationListResponse. No review comments were generated, the heuristic analysis found zero issues at any severity tier, and the changes are consistent, additive, and non-breaking in nature — exactly what you'd expect from a well-scoped patch release.

Key Findings:

• All seven files receiving the gmail_actions literal addition follow an established union type pattern, making the change low-risk and mechanically consistent across the codebase.
• The new effort parameter on MemorySearchParams is optional, preserving backward compatibility with existing callers that omit it.
• The IntegrationListResponse.actions_only boolean flag is an additive, optional field that does not alter existing response parsing for consumers unaware of it.
• Zero review comments were raised across 23 of 29 reviewed changed files, and the heuristic analysis surfaced no critical, significant, or medium-severity issues.

Files requiring special attention

• memories.ts
• integrations.ts
• shared.ts

[entelligence-ai-pr-reviews]

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this patch release (v0.35.1) cleanly adds gmail_actions to the union literal types across actions.ts, auth.ts, connections.ts, integrations.ts, web-crawler.ts, memories.ts, and shared.ts, and introduces the LocalDocsSearch class using MiniSearch for local document indexing in the MCP server. The changes are additive and non-breaking: new optional fields (actions_only on IntegrationListResponse, effort on MemorySearchParams) preserve backward compatibility, and no review comments were generated during analysis. The PR is consistent with a well-scoped patch release targeting type extension and tooling improvements.

Key Findings:

• All gmail_actions additions are purely additive literal type extensions to existing union types, posing no runtime risk to existing consumers who don't use the new value.
• The new optional actions_only boolean and effort parameter fields are correctly optional, ensuring no breaking changes to existing call sites.
• The LocalDocsSearch class introduction in local-docs-search.ts is a net-new capability isolated to the MCP server, limiting blast radius of any latent issues.
• Zero review comments were generated across 23 of 30 reviewed files, with no critical, significant, or medium-severity issues identified by heuristic analysis.

Files requiring special attention

• local-docs-search.ts
• shared.ts
• integrations.ts