Skip to content

release: 0.37.0#110

Open
stainless-app[bot] wants to merge 18 commits intomainfrom
release-please--branches--main--changes--next
Open

release: 0.37.0#110
stainless-app[bot] wants to merge 18 commits intomainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app bot commented Mar 20, 2026

Automated Release PR

0.37.0 (2026-03-31)

Full Changelog: v0.36.0...v0.37.0

Features

  • api: api update (13e0682)
  • api: api update (a0f4720)
  • api: api update (d3e77c3)
  • api: api update (6180902)
  • internal: implement indices array format for query and form serialization (0e1fd91)

Bug Fixes

  • sanitize endpoint path params (b2b3ca2)

Chores

  • ci: skip lint on metadata-only changes (b5a6b2d)
  • internal: update gitignore (8f27c46)
  • tests: bump steady to v0.19.4 (a855b0a)
  • tests: bump steady to v0.19.5 (7ea97c0)
  • tests: bump steady to v0.19.6 (1ecd0bf)
  • tests: bump steady to v0.19.7 (466a814)

Refactors

  • tests: switch from prism to steady (441e854)

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
Copy link
Copy Markdown
Contributor Author

stainless-app bot commented Mar 20, 2026

🧪 Testing

To try out this version of the SDK:

pip install 'https://pkg.stainless.com/s/hyperspell-python/13e068243400026b7c8e11b11fdca6ba89a2460e/hyperspell-0.36.0-py3-none-any.whl'

Expires at: Tue, 28 Apr 2026 09:30:57 GMT
Updated at: Sun, 29 Mar 2026 09:30:57 GMT

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 0a683c7 to c11de29 Compare March 20, 2026 03:53
@canaries-inc
Copy link
Copy Markdown

canaries-inc bot commented Mar 20, 2026

Canary encountered an internal error while analyzing this PR.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from c11de29 to e79b8eb Compare March 21, 2026 05:08
@entelligence-ai-pr-reviews
Copy link
Copy Markdown



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.
  • 12 out of 16 changed files were reviewed with no issues found, providing good coverage confidence.
  • No existing unresolved comments that could indicate lingering concerns.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e79b8eb to 0a0e812 Compare March 21, 2026 05:14
@entelligence-ai-pr-reviews
Copy link
Copy Markdown



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.
  • 12 out of 16 changed files were reviewed with zero issues found, providing good coverage confidence.
  • No existing unresolved comments to consider, so there are no outstanding concerns blocking the merge.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 0a0e812 to df02664 Compare March 21, 2026 21:30
@stainless-app stainless-app bot changed the title release: 0.36.1 release: 0.37.0 Mar 21, 2026
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from df02664 to eed16a8 Compare March 21, 2026 21:30
@entelligence-ai-pr-reviews
Copy link
Copy Markdown



Confidence Score: 5/5 - Safe to Merge

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

@entelligence-ai-pr-reviews
Copy link
Copy Markdown



Confidence Score: 5/5 - Safe to Merge

  • No new review comments were generated, indicating a clean PR with no identified issues
  • No existing unresolved comments to consider
  • High coverage with 26/30 changed files reviewed, providing good confidence in the assessment
  • Heuristic analysis shows zero critical, significant, or medium issues detected

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from eed16a8 to 5e6ff5c Compare March 23, 2026 22:30
@entelligence-ai-pr-reviews
Copy link
Copy Markdown



Confidence Score: 5/5 - Safe to Merge

  • No new review comments were generated, indicating the PR is clean with no identified issues.
  • Zero critical, significant, or medium issues were flagged by the heuristic analysis.
  • High coverage of 26/30 changed files were reviewed, providing good confidence in the assessment.
  • No existing unresolved comments that could indicate lingering concerns.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 5e6ff5c to 4dd9085 Compare March 24, 2026 05:10
@entelligence-ai-pr-reviews
Copy link
Copy Markdown



Confidence Score: 5/5 - Safe to Merge

  • No critical or significant issues found
  • 26/31 changed files reviewed (84% coverage)

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 4dd9085 to 8496f01 Compare March 24, 2026 05:17
@entelligence-ai-pr-reviews
Copy link
Copy Markdown



Confidence Score: 5/5 - Safe to Merge

  • No critical or significant issues found
  • 26/31 changed files reviewed (84% coverage)

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 8496f01 to efbb978 Compare March 24, 2026 17:30
@entelligence-ai-pr-reviews
Copy link
Copy Markdown



Confidence Score: 5/5 - Safe to Merge

  • No critical or significant issues found
  • 26/31 changed files reviewed (84% coverage)

stainless-app bot added 2 commits March 25, 2026 03:28
Note that we still want to run tests, as these depend on the metadata.
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from efbb978 to 51bc4bd Compare March 25, 2026 03:29
@entelligence-ai-pr-reviews
Copy link
Copy Markdown



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.
  • 26 out of 32 changed files were reviewed with zero issues flagged, providing good coverage confidence.
  • No existing unresolved comments that could indicate lingering concerns from previous reviews.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 51bc4bd to 8081965 Compare March 26, 2026 17:30
@entelligence-ai-pr-reviews
Copy link
Copy Markdown


Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR cleanly introduces Gmail Actions integration, the RFC 3986-compliant path_template utility in src/hyperspell/_utils/_path.py, a memory search effort parameter, and migrates mock server testing from Prism to Steady, all without raising any flagged issues during review. The changes are well-scoped across actions.py, memories.py, connections.py, and the associated type model files, with consistent literal type additions and no logic or security concerns identified. No pre-existing unresolved comments were carried forward into this release PR.

Key Findings:

  • The path_template utility in src/hyperspell/_utils/_path.py was introduced with RFC 3986 compliance in scope, and no encoding or injection concerns were flagged during review of that new file.
  • The gmail_actions literal type addition was propagated consistently across all relevant resource methods and 12+ type model files, reducing the risk of type mismatches or runtime errors from incomplete rollout.
  • The Prism-to-Steady mock server migration is an infrastructure-level test tooling change with no runtime impact on library consumers, and no regressions were identified in coverage.
  • Zero review comments were generated across 27 of 33 changed files, with no critical, significant, or medium-severity issues surfaced by automated or manual analysis.
Files requiring special attention
  • src/hyperspell/_utils/_path.py
  • src/hyperspell/resources/actions.py
  • src/hyperspell/resources/memories.py

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 8081965 to c5ab112 Compare March 27, 2026 06:41
@entelligence-ai-pr-reviews
Copy link
Copy Markdown


Confidence Score: 5/5 - Safe to Merge

Safe to merge — this release PR (v0.37.0) introduces well-scoped additions including the gmail_actions literal type across resource methods in actions.py, memories.py, and connections.py, a new _path.py utility for safe path parameter encoding via path_template, the indices array serialization format, a effort parameter for memory search, and a mock server migration from Prism to Steady. No review comments were generated across the 28 reviewed files, and the heuristic analysis surfaced zero critical, significant, or medium issues. The changes appear to be additive and consistent in pattern, following established conventions in the codebase.

Key Findings:

  • The new src/hyperspell/_utils/_path.py module introducing path_template for safe path parameter encoding is a correctness improvement that reduces the risk of URL injection or malformed paths in API calls.
  • The gmail_actions literal additions across 11+ type files and resource methods (actions.py, memories.py, connections.py) are consistently applied, suggesting a complete and non-partial feature rollout.
  • The migration from Prism to Steady for mock server tooling is a tooling change with no runtime impact on production code paths.
  • Zero review comments were generated and all heuristic checks passed cleanly, with 28 of 34 changed files reviewed — the unreviewed files are unlikely to contain surprises given the additive nature of the changes.
Files requiring special attention
  • src/hyperspell/_utils/_path.py
  • src/hyperspell/resources/actions.py
  • src/hyperspell/resources/memories.py
  • src/hyperspell/resources/connections.py

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from c5ab112 to 58cf481 Compare March 29, 2026 09:30
@entelligence-ai-pr-reviews
Copy link
Copy Markdown


Confidence Score: 5/5 - Safe to Merge

Safe to merge — this release PR for v0.37.0 of the Hyperspell Python SDK introduces gmail_actions as a supported integration/provider type across a broad set of models including ActionAddReactionParams, ActionSendMessageParams, Memory, MemorySearchParams, and WebCrawlerIndexResponse, which is a consistent, well-scoped additive change. No review comments were generated and heuristic analysis found zero critical, significant, or medium issues across the 30 reviewed files. The changes appear to be a straightforward enum/literal expansion propagated uniformly through the SDK's type system, which is the expected pattern for adding new integration support.

Key Findings:

  • The gmail_actions integration type addition is consistently applied across all relevant models (ActionAddReactionParams, ActionSendMessageParams, AuthMeResponse, ConnectionListResponse, IntegrationListResponse, Memory, MemoryDeleteResponse, MemoryListParams, MemorySearchParams, MemoryStatus, MemoryUpdateParams, Resource, WebCrawlerIndexResponse), indicating a thorough and non-partial rollout with no risk of type mismatch or missing enum values.
  • Zero heuristic issues were flagged at any severity level (critical, significant, high-risk, or medium), and no automated review comments were generated, suggesting the code follows existing SDK patterns without introducing novel logic or error-prone constructs.
  • This is a versioned release PR with additive-only changes to literal/enum type definitions, which carry minimal regression risk as they do not alter existing behavior for consumers not using the new gmail_actions value.
Files requiring special attention
  • src/hyperspell/types/memory.py
  • src/hyperspell/types/memory_search_params.py
  • src/hyperspell/types/integration_list_response.py

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 58cf481 to 94f6a6e Compare March 30, 2026 23:30
@entelligence-ai-pr-reviews
Copy link
Copy Markdown


Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR introduces the gmail_actions literal type across 13+ type definitions and resource methods, adds a new path_template utility module with RFC 3986-compliant URI interpolation, and migrates test infrastructure, all without any identified issues. The automated review generated zero comments across 30 of 36 changed files, and no critical, significant, or medium-severity concerns were flagged. The changes appear well-scoped as an API expansion and utility addition consistent with a library release version bump.

Key Findings:

  • The gmail_actions literal was consistently added across all relevant type definitions and resource methods (actions, memories, connections, integrations, shared types), suggesting a disciplined and complete integration with no partial or inconsistent typing.
  • The new src/hyperspell/_utils/_path.py module implementing RFC 3986-compliant URI interpolation with percent-encoding is a well-defined utility addition, and no issues with its logic or safety were identified by the automated review.
  • Zero review comments were generated across all reviewed files, and no pre-existing unresolved issues exist — the heuristic ceiling for this PR is 5/5 with no blocking, critical, or significant findings.
  • 30 out of 36 changed files were reviewed with no issues, and the 6 unreviewed files are likely minor (e.g., generated code or config updates) consistent with a versioned SDK release.
Files requiring special attention
  • src/hyperspell/_utils/_path.py
  • src/hyperspell/types/__init__.py
  • src/hyperspell/resources/actions/__init__.py

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 94f6a6e to c6b5480 Compare March 31, 2026 18:31
@entelligence-ai-pr-reviews
Copy link
Copy Markdown


Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR cleanly introduces path_template() in src/hyperspell/_utils/_path.py for RFC 3986-compliant URI construction and migrates the CI mock server from @stainless-api/prism-cli to @stdy/cli with updated health check endpoints at /_x-steady/health. No review comments were generated across the 30 reviewed files, and the changes are well-scoped with clear separation between the new utility module and the mechanical replacement of f-string URL interpolations. The CI scripting changes in scripts/mock and scripts/test are straightforward polling updates with no logic regressions introduced.

Key Findings:

  • The new src/hyperspell/_utils/_path.py module introduces a dedicated path_template() utility that centralizes URI construction, replacing ad-hoc f-string interpolation across resource files — this improves consistency and reduces the risk of malformed URLs.
  • The mock server migration from Prism to Steady (@stdy/cli v0.19.7) is a contained change limited to CI scripts, with the health check endpoint update to /_x-steady/health being the only behavioral delta, posing negligible runtime risk to production code.
  • Zero review comments were generated across 30 of 36 changed files, and the heuristic analysis found no critical, significant, or medium issues, supporting a clean merge signal.
  • The 6 uncovered files out of 36 changed represent a minor gap in automated review coverage, but given the mechanical nature of the f-string-to-path_template() substitutions, this is unlikely to hide defects.
Files requiring special attention
  • src/hyperspell/_utils/_path.py
  • scripts/mock
  • scripts/test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants