Release Rails 7.2.0

Author: rafaelfranca

Gemfile.lock

@@ -1,7 +1,7 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.1.3.2)
+    activesupport (7.1.3.4)
       base64
       bigdecimal
       concurrent-ruby (~> 1.0, >= 1.0.2)
@@ -11,19 +11,19 @@ GEM
       minitest (>= 5.1)
       mutex_m
       tzinfo (~> 2.0)
-    addressable (2.8.6)
-      public_suffix (>= 2.0.2, < 6.0)
+    addressable (2.8.7)
+      public_suffix (>= 2.0.2, < 7.0)
     base64 (0.2.0)
-    bigdecimal (3.1.7)
+    bigdecimal (3.1.8)
     coffee-script (2.4.1)
       coffee-script-source
       execjs
     coffee-script-source (1.12.2)
     colorator (1.1.0)
     commonmarker (0.23.10)
-    concurrent-ruby (1.2.3)
+    concurrent-ruby (1.3.3)
     connection_pool (2.4.1)
-    dnsruby (1.72.0)
+    dnsruby (1.72.2)
       simpleidn (~> 0.2.1)
     drb (2.2.1)
     em-websocket (0.5.3)
@@ -33,11 +33,21 @@ GEM
       ffi (>= 1.15.0)
     eventmachine (1.2.7)
     execjs (2.9.1)
-    faraday (2.9.0)
+    faraday (2.10.1)
       faraday-net_http (>= 2.0, < 3.2)
-    faraday-net_http (3.1.0)
+      logger
+    faraday-net_http (3.1.1)
       net-http
-    ffi (1.16.3)
+    ffi (1.17.0-aarch64-linux-gnu)
+    ffi (1.17.0-aarch64-linux-musl)
+    ffi (1.17.0-arm-linux-gnu)
+    ffi (1.17.0-arm-linux-musl)
+    ffi (1.17.0-arm64-darwin)
+    ffi (1.17.0-x86-linux-gnu)
+    ffi (1.17.0-x86-linux-musl)
+    ffi (1.17.0-x86_64-darwin)
+    ffi (1.17.0-x86_64-linux-gnu)
+    ffi (1.17.0-x86_64-linux-musl)
     forwardable-extended (2.6.0)
     gemoji (4.1.0)
     github-pages (231)
@@ -95,7 +105,7 @@ GEM
       activesupport (>= 2)
       nokogiri (>= 1.4)
     http_parser.rb (0.8.0)
-    i18n (1.14.4)
+    i18n (1.14.5)
       concurrent-ruby (~> 1.0)
     jekyll (3.9.5)
       addressable (~> 2.4)
@@ -213,38 +223,40 @@ GEM
     listen (3.9.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
+    logger (1.6.0)
     mercenary (0.3.6)
-    mini_portile2 (2.8.5)
     minima (2.5.1)
       jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    minitest (5.22.3)
+    minitest (5.24.1)
     mutex_m (0.2.0)
     net-http (0.4.1)
       uri
-    nokogiri (1.16.3)
-      mini_portile2 (~> 2.8.2)
+    nokogiri (1.16.7-aarch64-linux)
       racc (~> 1.4)
-    nokogiri (1.16.3-aarch64-linux)
+    nokogiri (1.16.7-arm-linux)
       racc (~> 1.4)
-    nokogiri (1.16.3-arm64-darwin)
+    nokogiri (1.16.7-arm64-darwin)
       racc (~> 1.4)
-    nokogiri (1.16.3-x86_64-darwin)
+    nokogiri (1.16.7-x86-linux)
       racc (~> 1.4)
-    nokogiri (1.16.3-x86_64-linux)
+    nokogiri (1.16.7-x86_64-darwin)
+      racc (~> 1.4)
+    nokogiri (1.16.7-x86_64-linux)
       racc (~> 1.4)
     octokit (4.25.1)
       faraday (>= 1, < 3)
       sawyer (~> 0.9)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (5.0.4)
-    racc (1.7.3)
+    public_suffix (5.1.1)
+    racc (1.8.1)
     rb-fsevent (0.11.2)
-    rb-inotify (0.10.1)
+    rb-inotify (0.11.1)
       ffi (~> 1.0)
-    rexml (3.2.6)
+    rexml (3.3.4)
+      strscan
     rouge (3.30.0)
     rubyzip (2.3.2)
     safe_yaml (1.0.5)
@@ -256,33 +268,36 @@ GEM
     sawyer (0.9.2)
       addressable (>= 2.3.5)
       faraday (>= 0.17.3, < 3)
-    simpleidn (0.2.1)
-      unf (~> 0.1.4)
+    simpleidn (0.2.3)
+    strscan (3.1.0)
     terminal-table (1.8.0)
       unicode-display_width (~> 1.1, >= 1.1.1)
     typhoeus (1.4.1)
       ethon (>= 0.9.0)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
-    unf (0.1.4)
-      unf_ext
-    unf_ext (0.0.9.1)
     unicode-display_width (1.8.0)
     uri (0.13.0)
     webrick (1.8.1)
 
 PLATFORMS
-  aarch64-linux
-  arm64-darwin-21
-  arm64-darwin-22
-  ruby
-  x86_64-darwin-20
-  x86_64-darwin-21
+  aarch64-linux-gnu
+  aarch64-linux-musl
+  arm-linux
+  arm-linux-gnu
+  arm-linux-musl
+  arm64-darwin
+  x86-linux
+  x86-linux-gnu
+  x86-linux-musl
+  x86_64-darwin
   x86_64-linux
+  x86_64-linux-gnu
+  x86_64-linux-musl
 
 DEPENDENCIES
   github-pages
   webrick (~> 1.7)
 
 BUNDLED WITH
-   2.4.19
+   2.5.10

_config.yml

@@ -16,6 +16,7 @@ exclude:
   - Gemfile
   - Gemfile.lock
   - README.md
+  - bin
 
 collections:
   pages:

_data/version.yml

@@ -1,3 +1,3 @@
-label: Rails 7.1.3.4
-date: June 4, 2024
-url: /2024/6/4/Rails-Versions-6-1-7-8-7-0-8-4-and-7-1-3-4-have-been-released
+label: Rails 7.2.0
+date: August 9, 2024
+url: /2024/8/9/Rails-7-2-0-has-been-released

_pages/maintenance.html

@@ -11,7 +11,7 @@
     <div class="heading__body">
       <div class="heading__headline common-headline">
         <h1>Maintenance policy.</h1>
-        <h4><strong>Support is divided into four groups:</strong> new features, bug fixes, security issues, and severe security issues.</h4>
+        <h4><strong>Support is divided into three groups:</strong> new features, bug fixes, and security issues, and severe security issues.</h4>
       </div>
     </div>
   </div>
@@ -21,25 +21,39 @@ <h4><strong>Support is divided into four groups:</strong> new features, bug fixe
   <div class="container">
     <div class="text__body">
       <div class="text__content common-content">
-        <h3>XYZ Formatting</h3>
+        <h3 id="new_features">New Features</h3>
+        <p>We aim to release a version containing new features every six months. In the rare case where
+          no release was made in one year, we will extend the support period for the previous release
+          until the next release is made.</p>
+        <hr class="divider" />
+        <h3 id="bug_fixes">Bug Fixes</h3>
+        <p>Minor releases will receive bug fixes for one year after the first release in
+          its series. For example, if a theoretical 1.1.0 is released on January 1, 2023, it
+          will receive bug fixes until January 1, 2024. After that, it will be considered
+          unsupported.</p>
+        <h6>List of currently supported releases</h6>
         <ul>
-          <li><strong>Major X: </strong> New features, will likely contain API changes. The difference between Rails’ minor and major releases is the magnitude of breaking changes, and usually reserved for special occasions.</li>
-          <li><strong>Minor Y: </strong> New features, may contain API changes. Breaking changes are paired with deprecation notices in the previous minor or major release.</li>
-          <li><strong>Patch Z: </strong> Only bug fixes, no API changes, no new features. Except as necessary for security fixes.</li>
+          <li><strong>7.2.x</strong> - Supported until August 9, 2025</li>
+          <li><strong>7.1.x</strong> - Supported until October 1, 2024</li>
+          </li>
         </ul>
         <hr class="divider" />
-        <h3>New Features</h3>
-        <p>Only added to the main branch and will not be made available in patch releases.</p>
-        <hr class="divider" />
-        <h3>Bug Fixes</h3>
-        <p>Only the latest release series will receive bug fixes. Bug fixes are typically added to the main branch, and backported to the x-y-stable branch of the latest release series if there is sufficient need. When enough bugs fixes have been added to an x-y-stable branch, a new patch release is built from it. For example, a theoretical 1.2.2 patch release would be built from the 1-2-stable branch.</p>
-        <p>In special situations, where someone from the <a href="/community#core">Rails core team</a> agrees to support more series, they are included in the list of supported series.</p>
-        <p><strong>Currently included series:</strong> 7.0.Z.</p>
-        <hr class="divider" />
-        <h3>Security Issues</h3>
-        <p>See the <a href="/security">Security policy</a> for more details.</p>
+        <h3 id="security">Security Issues</h3>
+        <p>
+          Minor releases will receive security fixes for two years after the first release in
+          its series. For example, if a theoretical 1.1.0 is released on January 1, 2023, it
+          will receive security fixes until January 1, 2025. After that, it will reach its
+          end-of-life.
+        </p>
+        <h6>List of currently supported releases</h6>
+        <ul>
+          <li><strong>7.2.x</strong> - Supported until August 9, 2026</li>
+          <li><strong>7.1.x</strong> - Supported until October 1, 2025</li>
+          <li><strong>7.0.x</strong> - Supported until April 1, 2025</li>
+          <li><strong>6.1.x</strong> - Supported until October 1, 2024</li>
+        </ul>
         <hr class="divider" />
-        <h3>Unsupported Release Series</h3>
+        <h3 id="unsupported">Unsupported Release Series</h3>
         <p>When a release series is no longer supported, it’s your own responsibility to deal with bugs and security issues. We may provide backports of the fixes and publish them to git, however there will be no new versions released. If you are not comfortable maintaining your own versions, you should upgrade to a supported version.</p>
       </div>
     </div>

_posts/2024-08-09-Rails-7-2-0-has-been-released.markdown

@@ -0,0 +1,99 @@
+---
+layout: post
+title: 'Rails 7.2: Better production defaults, Dev containers, new guides design, and more!'
+categories: releases
+author: rafaelfranca
+published: true
+date: 2024-08-09 21:30:00 -03:00
+---
+
+We are happy to announce the release of Rails 7.2!
+There has been [close to 2,500 commits](https://github.com/rails/rails/compare/v7.1.0...7-2-stable) made by [over 400 contributors](https://contributors.rubyonrails.org/edge/contributors) since Rails 7.1, so this release is packed with new features and improvements.
+
+## Better production defaults
+
+Rails 7.2 comes with better productions defaults to help you build more efficient applications.
+
+Starting with YJIT. YJIT is Ruby's JIT compiler that is available in CRuby since Ruby 3.1. It can provide significant performance improvements for Rails applications, offering 15-25% latency improvements.
+
+In Rails 7.2, [YJIT is enabled by default if running Ruby 3.3 or newer](https://edgeguides.rubyonrails.org/7_2_release_notes.html#enable-yjit-by-default-if-running-ruby-3-3).
+
+After careful consideration, investigation, and based on battle-tested experience from applications running in
+production, we decided to change the [default number of threads in Puma from 5 to 3](https://edgeguides.rubyonrails.org/7_2_release_notes.html#set-a-new-default-for-the-puma-thread-count).
+This change is to improve latency (request response time) by reducing the time Ruby spends waiting for the Global VM Lock (GVL) to release when the thread count is too high.
+
+And the default Dockerfile generated by Rails now includes [jemalloc to optimize memory allocation](https://edgeguides.rubyonrails.org/7_2_release_notes.html#setup-jemalloc-in-default-dockerfile-to-optimize-memory-allocation).
+
+https://guides.rubyonrails.org/7_2_release_notes.html
+
+## Development containers configuration for applications
+
+A [development container](https://containers.dev/) (or dev container for short) allows you to use a container
+as a full-featured development environment.
+
+Rails 7.2 adds the ability to generate a development container configuration for your application. This configuration
+includes a `.devcontainer` folder with a `Dockerfile`, a `docker-compose.yml` file, and a `devcontainer.json` file.
+
+By default, the dev container contains the following:
+
+* A Redis container for use with Kredis, Action Cable, etc.
+* A database (SQLite, Postgres, MySQL or MariaDB)
+* A Headless Chrome container for system tests
+* Active Storage configured to use the local disk and with preview features working
+
+To generate a new application with a development container, you can run:
+
+```bash
+rails new myapp --devcontainer
+```
+
+For existing applications, a `devcontainer` command is now available:
+
+```bash
+rails devcontainer
+```
+
+For more information, see the [Getting Started with Dev Containers](https://guides.rubyonrails.org/getting_started_with_devcontainer.html) guide.
+
+### New design for the Rails guides
+
+When Rails 7.0 landed in December 2021, it came with a fresh new homepage and a new boot screen. The design of the
+guides, however, has remained largely untouched since 2009 - a point which hasn’t gone unnoticed (we heard your feedback).
+
+With all of the work right now going into removing complexity from the Rails framework and making the documentation
+consistent, clear, and up-to-date, it was time to tackle the design of the guides and make them equally modern, simple,
+and fresh.
+
+We worked with UX designer [John Athayde](https://meticulous.com/) to take the look and feel of the homepage and
+transfer that over to the Rails guides to make them clean, sleek, and up-to-date.
+
+The layout will remain the same, but from today you will see the following changes reflected in the guides:
+
+* Cleaner, less busy design.
+* Fonts, color scheme, and logo more consistent with the home page.
+* Updated iconography.
+* Simplified navigation.
+* Sticky "Chapters" navbar when scrolling.
+
+See the [announcement blog post for some before/after images](https://rubyonrails.org/2024/3/20/rails-guides-get-a-facelift).
+
+## Other improvements
+
+Rails 7.2 also includes many other improvements and new features. Here are a few highlights:
+
+* Add browser version guard by default.
+* Make Ruby 3.1 the new minimum version.
+* Default Progressive Web Application (PWA) files.
+* Add omakase RuboCop rules by default.
+* Add GitHub CI workflow by default to new applications.
+* Add Brakeman by default to new applications.
+* Prevent jobs from being scheduled within transactions.
+* Per transaction commit and rollback callbacks.
+* Suggest puma-dev configuration in bin/setup.
+
+Please check the [Rails 7.2 release notes](https://guides.rubyonrails.org/7_2_release_notes.html) for more details.
+
+## What's next?
+
+The team is already hard at work on Rails 8.0, that we plan to release later this year and we are looking forward to
+interact with the community and share presents at Rails World, in September this year.

bin/jekyll

@@ -0,0 +1,27 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+#
+# This file was generated by Bundler.
+#
+# The application 'jekyll' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../Gemfile", __dir__)
+
+bundle_binstub = File.expand_path("bundle", __dir__)
+
+if File.file?(bundle_binstub)
+  if File.read(bundle_binstub, 300).include?("This file was generated by Bundler")
+    load(bundle_binstub)
+  else
+    abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
+Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.")
+  end
+end
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("jekyll", "jekyll")

bin/server

@@ -0,0 +1,5 @@
+#!/usr/bin/env bash
+
+set -e
+
+bin/jekyll s -I -w --livereload