-
Notifications
You must be signed in to change notification settings - Fork 669
Create release for 3.3.11 #3868
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
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| --- | ||
| layout: news_post | ||
| title: "Ruby 3.3.11 Released" | ||
| author: hsbt | ||
| translator: | ||
| date: 2026-03-26 00:00:00 +0000 | ||
| lang: en | ||
| --- | ||
|
|
||
| Ruby 3.3.11 has been released. This release includes [an update to the zlib gem addressing CVE-2026-27820](https://www.ruby-lang.org/en/news/2026/03/05/buffer-overflow-zlib-cve-2026-27820/), along with some bug fixes. | ||
|
|
||
| Please see the [GitHub releases](https://github.com/ruby/ruby/releases/tag/v3_3_11) for further details. | ||
|
|
||
| This is the last release of normal maintenance for the Ruby 3.3 series. After this release, Ruby 3.3 enters a security maintenance phase. During this phase, we will only backport security fixes and fixes for critical build issues, without any regular bug fixes. | ||
|
|
||
| The security maintenance phase is scheduled to last for one year, until the end of March 2027. At that point, official support for Ruby 3.3 will end. We recommend that you begin planning your migration to Ruby 3.4 or 4.0. | ||
|
|
||
| ## Download | ||
|
|
||
| {% assign release = site.data.releases | where: "version", "3.3.11" | first %} | ||
|
|
||
| * <{{ release.url.gz }}> | ||
|
|
||
| SIZE: {{ release.size.gz }} | ||
| SHA1: {{ release.sha1.gz }} | ||
| SHA256: {{ release.sha256.gz }} | ||
| SHA512: {{ release.sha512.gz }} | ||
|
|
||
| * <{{ release.url.xz }}> | ||
|
|
||
| SIZE: {{ release.size.xz }} | ||
| SHA1: {{ release.sha1.xz }} | ||
| SHA256: {{ release.sha256.xz }} | ||
| SHA512: {{ release.sha512.xz }} | ||
|
|
||
| * <{{ release.url.zip }}> | ||
|
|
||
| SIZE: {{ release.size.zip }} | ||
| SHA1: {{ release.sha1.zip }} | ||
| SHA256: {{ release.sha256.zip }} | ||
| SHA512: {{ release.sha512.zip }} | ||
|
|
||
| ## Release Comment | ||
|
|
||
| Many committers, developers, and users who provided bug reports helped us make this release. | ||
| Thanks for their contributions. | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Frontmatter
datetime is00:00:00 +0000, but Ruby 3.3 patch release posts typically use11:00:00 +0000(e.g., en/news/_posts/2025-10-23-ruby-3-3-10-released.md and 2025-07-24-ruby-3-3-9-released.md). Consider aligning the timestamp to keep ordering/feeds consistent for same-day posts.