Skip to content

release: 0.11.5#33

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

release: 0.11.5#33
stainless-app[bot] merged 4 commits intomainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Contributor

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

Automated Release PR

0.11.5 (2025-09-29)

Full Changelog: v0.11.4...v0.11.5

Features

  • Add App Version to Invocation and add filtering on App Version (81f87e2)
  • Fix my incorrect grammer (f04186f)

Bug Fixes

  • bugfix for setting JSON keys with special characters (32304ba)

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


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 1f705b9...ea67179

Analysis

  1. The PR centralizes escaping of special characters for JSON keys through a new EscapeSJSONKey function, but it may not be immediately obvious to developers that this function should be used for all JSON key operations to maintain consistency.

  2. While the PR improves character coverage by handling additional special characters (\\, |, #, @, ?), it's unclear if a comprehensive analysis was done to ensure all possible problematic characters are now properly escaped.

  3. The fix is applied to three specific areas (encoder, union, parameter marshaling), but there could be other places in the codebase that manipulate JSON keys that weren't identified and may still contain the bug.

  4. The PR doesn't appear to include additional tests specifically targeting edge cases with the newly handled special characters, which could lead to regressions in the future.

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

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from ea67179 to a98acc3 Compare September 26, 2025 20:24
@stainless-app stainless-app bot changed the title release: 0.11.5 release: 0.12.0 Sep 26, 2025
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from a98acc3 to cf12325 Compare September 26, 2025 20:24
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from cf12325 to 04cd6ea Compare September 29, 2025 18:12
@hiroTamada hiroTamada changed the title release: 0.12.0 release: 0.11.5 Sep 29, 2025
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 29, 2025

Release version edited manually

The Pull Request version has been manually set to 0.11.5 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 04cd6ea to 5caef65 Compare September 29, 2025 18:19
@stainless-app stainless-app bot merged commit d0fc658 into main Sep 29, 2025
4 checks passed
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 29, 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