Skip to content

fix: Update force_encoding to operate on unfrozen string #60

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

Merged
merged 1 commit into from
Jul 15, 2025

Conversation

keelerm84
Copy link
Member

Similar to the work done in ccf79af, we are updating this library to
handle the upcoming change where strings are frozen by default.

Similar to the work done in ccf79af, we are updating this library to
handle the upcoming change where strings are frozen by default.
@keelerm84 keelerm84 requested a review from a team as a code owner July 15, 2025 14:44
@keelerm84 keelerm84 merged commit 0e2e80d into main Jul 15, 2025
6 checks passed
@keelerm84 keelerm84 deleted the mk/sdk-1382/deprecation-warning branch July 15, 2025 15:19
keelerm84 pushed a commit that referenced this pull request Jul 15, 2025
🤖 I have created a release *beep* *boop*
---


##
[2.2.6](2.2.5...2.2.6)
(2025-07-15)


### Bug Fixes

* Add `logger` as explicit dependency
([#61](#61))
([50efb0d](50efb0d))
* Update `force_encoding` to operate on unfrozen string
([#60](#60))
([0e2e80d](0e2e80d))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants