Skip to content

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Dec 26, 2025

Automated Release PR

6.6.0 (2025-01-15)

Full Changelog: v6.5.0...v6.6.0

Breaking Changes

  • browser_rendering: refactor request body parameters to use proper union types

    The models were updated to be accurate to what the API expects, so there are parameter changes
    across most of the sub-resources under the browser_rendering umbrella.

Features

  • ai_search: add hybrid search and public endpoint support
  • ai_gateway: add is_default field to gateway configurations
  • cloudforce_one: add UUID support, STIX2 format, and async indicator processing
  • custom_pages: add waf_challenge identifier support
  • email_security: add async polling support with Location header and success field
  • magic_cloud_networking: expand type definitions for catalog sync, cloud integration, and onramp
  • realtime_kit: add comprehensive meeting, preset, recording, session, and webhook endpoints
  • rulesets: add request and response body buffering configuration options
  • stream: add properly typed download responses with status tracking
  • workers: add targeted placement support with host, hostname, and region options
  • workers_for_platforms: enhance dispatch namespace script settings types
  • workflows: add properly typed instance_retention parameter with error and success retention
  • zones: refactor subscription responses to use dedicated types

Chores

  • addressing: add auto_generated field to LOA document responses
  • custom_hostnames: make SSL parameter optional in create requests
  • email_security: deprecate item_count field in move responses
  • hyperdrive: improve documentation for caching and port configuration
  • pages: refactor project and deployment type definitions
  • shared: add union type implementations and documentation updates
  • zero_trust: simplify DLP shared entry types by removing entry_type unions

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 stainless-app bot force-pushed the release-please--branches--main--changes--next branch 5 times, most recently from 278b59b to 230ef5f Compare January 4, 2026 22:08
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 3 times, most recently from d35f7f8 to 8ac0d77 Compare January 6, 2026 19:29
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 8ac0d77 to fa9bdf0 Compare January 7, 2026 17:40
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from fa9bdf0 to 594e525 Compare January 8, 2026 17:20
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 594e525 to a1c580a Compare January 8, 2026 21:27
* fix: unsupported auth scheme
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from a1c580a to 3ee45a2 Compare January 8, 2026 23:32
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 3ee45a2 to 06d43bc Compare January 9, 2026 10:49
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 06d43bc to e18500d Compare January 9, 2026 11:56
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e28473c to 7097dda Compare January 13, 2026 19:26
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 7097dda to d6a7eaa Compare January 13, 2026 23:22
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from d6a7eaa to aafe105 Compare January 14, 2026 10:25
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from aafe105 to 61b655e Compare January 14, 2026 12:23
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 61b655e to 3d27fe2 Compare January 14, 2026 16:20
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 3d27fe2 to 8a216d6 Compare January 14, 2026 16:38
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 3 times, most recently from 66dd1f0 to 2d82358 Compare January 15, 2026 23:05
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 2d82358 to a9bb393 Compare January 15, 2026 23:32
@vaishakdinesh vaishakdinesh requested a review from a team January 15, 2026 23:59
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from a9bb393 to 281c2c2 Compare January 16, 2026 01:33
@musa-cf musa-cf merged commit 3cb4662 into main Jan 16, 2026
2 of 5 checks passed
@musa-cf musa-cf deleted the release-please--branches--main--changes--next branch January 16, 2026 01:38
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Jan 16, 2026

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.

3 participants