Skip to content

fix: Explicitly mark buffer variable as unfrozen #59

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 14, 2025

Conversation

keelerm84
Copy link
Member

In a future version of Ruby, literal strings will be frozen by default.
To avoid this causing an issue (and raising deprecation warnings now),
we are explicitly marking this literal string as unfrozen.

In a future version of Ruby, literal strings will be frozen by default.
To avoid this causing an issue (and raising deprecation warnings now),
we are explicitly marking this literal string as unfrozen.
@keelerm84 keelerm84 requested a review from a team as a code owner July 14, 2025 17:00
@keelerm84 keelerm84 merged commit ccf79af into main Jul 14, 2025
10 of 11 checks passed
@keelerm84 keelerm84 deleted the mk/sdk-1382/fix-warning branch July 14, 2025 17:08
keelerm84 pushed a commit that referenced this pull request Jul 14, 2025
🤖 I have created a release *beep* *boop*
---


##
[2.2.5](2.2.4...2.2.5)
(2025-07-14)


### Bug Fixes

* Bump minimum to ruby 3.1
([#57](#57))
([93a9947](93a9947))
* Explicitly mark buffer variable as unfrozen
([#59](#59))
([ccf79af](ccf79af))

---
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