Skip to content

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 release introduces the ability to filter invocation logs by time.

Why we made these changes

To allow users to retrieve logs from a specific point in time, making it easier to monitor or debug long-running invocations without fetching the entire log history.

What changed?

  • The invocations.follow method now accepts an optional query parameter with a since property to filter logs by a timestamp.
  • The new InvocationFollowParams type is now exported for use in client applications.
  • A new (skipped) test was added to verify the correct passing of parameters to the invocations.follow method.
  • Version bumped to 0.11.3 across package.json, CHANGELOG.md, and other release-related files.

Description generated by Mesa. Update settings

@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 24, 2025

🧪 Testing

To try out this version of the SDK, run:

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

Expires: Fri, 24 Oct 2025 20:30:29 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 c1350d3...17a9531

Analysis

  1. The method signature uses InvocationFollowParams | undefined = {} which creates type confusion - it suggests undefined is allowed but defaults to an empty object instead.

  2. While the API changes maintain backward compatibility, the documentation should clearly indicate the behavior of the optional query parameter to ensure proper implementation by clients.

  3. The type safety implementation may need review to ensure that the since property filtering works as expected across all possible input scenarios.

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

10 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--components--sdk branch from 17a9531 to 39c8164 Compare September 24, 2025 20:54
@stainless-app stainless-app bot merged commit 4e1d5ce into main Sep 24, 2025
7 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.

2 participants