Skip to content

release: 0.11.3#31

Merged
stainless-app[bot] merged 2 commits intomainfrom
release-please--branches--main--changes--next
Sep 24, 2025
Merged

release: 0.11.3#31
stainless-app[bot] merged 2 commits intomainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Sep 24, 2025

Automated Release PR

0.11.3 (2025-09-24)

Full Changelog: v0.11.2...v0.11.3

Features


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 is an automated PR to release version 0.11.3, which introduces a new feature for accessing per-invocation logs.

Why we made these changes

To improve debugging and traceability for developers by allowing them to retrieve logs associated with each specific API invocation made through the SDK.

What changed?

  • Feature: Added support for per-invocation logs, with corresponding logic changes in invocation.go.
  • Documentation: Updated CHANGELOG.md, README.md, and api.md to reflect the new version and document the feature.
  • Versioning: Bumped the version number in internal/version.go and other release-related files like .release-please-manifest.json.

Description generated by Mesa. Update settings

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 22ff04a...e0ed760

Analysis

  1. The API signature change to FollowStreaming adds a new InvocationFollowParams parameter, which constitutes a breaking change that should be carefully considered by consumers of this API.

  2. As this appears to be generated code (likely from OpenAPI specifications), there may be consistency issues if manual modifications are made without updating the source specifications.

  3. While the PR adds time-based filtering capabilities, it's unclear if there are any performance implications for large log volumes or high-frequency invocations.

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

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

@hiroTamada hiroTamada changed the title release: 0.12.0 release: 0.11.3 Sep 24, 2025
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 24, 2025

Release version edited manually

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

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

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e0ed760 to 72ce9a5 Compare September 24, 2025 20:54
@stainless-app stainless-app bot merged commit 99eb978 into main Sep 24, 2025
4 checks passed
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 24, 2025

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.

1 participant