Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release: 0.9.0 #75

Merged
merged 7 commits into from
Jan 3, 2025
Merged

Conversation

stainless-app[bot]
Copy link
Contributor

@stainless-app stainless-app bot commented Jan 2, 2025

Automated Release PR

0.9.0 (2025-01-03)

Full Changelog: v0.8.1...v0.9.0

⚠ BREAKING CHANGES

  • client: switch query params objects to use QueryParams (#64)

Features

  • client: add beta endpoints (#79) (8584a20)
  • client: put body field in params, add more convenience methods, and add missing docs (#77) (0c74350)

Chores

Documentation

Refactors

  • client: switch query params objects to use QueryParams (#64) (4e9c3eb)
  • internal: use constructor to deserialize json (#66) (27389cd)

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

)

feat(client): add methods for removing additional properties
chore(internal): remove unnecessary validation methods
chore(internal): swap params body getters to use optionals
chore(internal): remove unnecessary nullable annotations
style(internal): minor changes to code ordering and syntax
# Migration
If you were accessing `_additionalProperties()` on a query params object, then previously it returned `Map<String, List<String>>`. Now it returns a dedicated `QueryParams` object. The `QueryParams` class is better suited for mapping a key to multiple values and has similar methods to `Map`.
@stainless-app stainless-app bot requested a review from a team as a code owner January 2, 2025 18:11
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch 3 times, most recently from f1f06b8 to 769175d Compare January 3, 2025 05:02
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e2f4c69 to 0c74350 Compare January 3, 2025 18:09
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 55e3003 to d153ef9 Compare January 3, 2025 19:12
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from d689ca8 to 8584a20 Compare January 3, 2025 22:57
@stainless-app stainless-app bot merged commit 2b735f9 into main Jan 3, 2025
2 checks passed
Copy link
Contributor Author

stainless-app bot commented Jan 3, 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