[PROF-11035] Bump to version 3.3.7#9
Merged
Conversation
anmarchenko
approved these changes
Dec 13, 2024
Base automatically changed from
ivoanjo/prof-11035-ruby-3.4.0-rc1-headers
to
master
December 13, 2024 14:18
Member
Author
|
We should only merge this and release once #11 is merged as well. |
AlexJF
approved these changes
Dec 16, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR bumps the gem to version 3.3.7 in preparation for the next release.
Motivation:
Release a new version with the Ruby 3.4.0-rc1 headers from #8.
Additional Notes:
I've also removed the
CHANGELOG.mdandCONTRIBUTING.mdfiles as they were leftovers from our forkingdebase-ruby_core_sourceand aren't particularly relevant anymore -- we have our own separate changelog file, and the instructions inCONTRIBUTING.mdare also in theREADME.md.This PR is on top of #8 to make it easier to test the new release (and because it implicitly depends on #8 anyway); once #8 gets merged to master, this one will automatically will get changed to master as well.
How to test the change?
Here's what I did to validate this locally:
bundle exec rake buildto package the gem