Skip to content

Conversation

stainless-app[bot]
Copy link
Contributor

@stainless-app stainless-app bot commented Oct 7, 2025

Automated Release PR

0.15.0 (2025-10-07)

Full Changelog: v0.14.0...v0.15.0

Features

  • Hide and deprecate mobile proxy type (54dae63)

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


TL;DR

This release deprecates and hides the mobile proxy type.

Why we made these changes

The mobile proxy type is a legacy feature that is no longer supported. This change removes it to simplify the API for users.

What changed?

  • The mobile option has been removed from the ProxyType enum.
  • The type is now marked as @deprecated in documentation to guide users away from using it.

Validation

All existing unit and integration tests for the related services continue to pass.

Description generated by Mesa. Update settings

Copy link
Contributor Author

stainless-app bot commented Oct 7, 2025

🧪 Testing

To try out this version of the SDK, run:

npm install 'https://pkg.stainless.com/s/kernel-typescript/54dae631f02ce14c75222677ffa171895f4cb0ca/dist.tar.gz'

Expires: Thu, 06 Nov 2025 15:02:46 GMT

Copy link

@mesa-dot-dev mesa-dot-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Performed full review of 927c14e...8bd6cbe

Analysis

  1. The API documentation cleanup removing "or EU" references may impact consumers who were relying on this non-standard country code format, potentially causing integration issues.

  2. The mobile proxy OS fields have been marked as deprecated without a clear migration path or timeline for removal, which could lead to future compatibility problems.

  3. Although version updates appear consistent, there's no explicit validation that all dependencies and internal references have been updated to support the new version.

  4. The OpenAPI spec update is reflected only in a stats file hash change without details on what API changes were made, making it difficult to assess potential impacts.

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

Slash Commands:

  • /review - Request a full code review
  • /review latest - Review only changes since the last review
  • /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
  • /help - Get help with Mesa commands and configuration options

6 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings

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