}
- ```
-
- After:
-
- ```ruby
- hash = { class: Object, module: Kernel }
- hash.deep_dup # => {:class=>Object, :module=>Kernel}
- ```
-
- *Jean Boussier*
-
-* Consistently raise an `ArgumentError` if the `ActiveSupport::Cache` key is blank.
-
- *Joshua Young*
-
-* Deprecate usage of the singleton `ActiveSupport::Deprecation`.
-
- All usage of `ActiveSupport::Deprecation` as a singleton is deprecated, the most common one being
- `ActiveSupport::Deprecation.warn`. Gem authors should now create their own deprecator (`ActiveSupport::Deprecation`
- object), and use it to emit deprecation warnings.
-
- Calling any of the following without specifying a deprecator argument is also deprecated:
- * Module.deprecate
- * deprecate_constant
- * DeprecatedObjectProxy
- * DeprecatedInstanceVariableProxy
- * DeprecatedConstantProxy
- * deprecation-related test assertions
-
- Use of `ActiveSupport::Deprecation.silence` and configuration methods like `behavior=`, `disallowed_behavior=`,
- `disallowed_warnings=` should now be aimed at the [application's deprecators](https://api.rubyonrails.org/classes/Rails/Application.html#method-i-deprecators).
-
- ```ruby
- Rails.application.deprecators.silence do
- # code that emits deprecation warnings
- end
- ```
-
- If your gem has a Railtie or Engine, it's encouraged to add your deprecator to the application's deprecators, that
- way the deprecation related configuration options will apply to it as well, e.g.
- `config.active_support.report_deprecations` set to `false` in the production environment will also disable your
- deprecator.
-
- ```ruby
- initializer "my_gem.deprecator" do |app|
- app.deprecators[:my_gem] = MyGem.deprecator
- end
- ```
-
- *Étienne Barrié*
-
-* Add `Object#with` to set and restore public attributes around a block
-
- ```ruby
- client.timeout # => 5
- client.with(timeout: 1) do
- client.timeout # => 1
- end
- client.timeout # => 5
- ```
-
- *Jean Boussier*
-
-* Remove deprecated support to generate incorrect RFC 4122 UUIDs when providing a namespace ID that is not one of the
- constants defined on `Digest::UUID`.
-
- *Rafael Mendonça França*
-
-* Deprecate `config.active_support.use_rfc4122_namespaced_uuids`.
-
- *Rafael Mendonça França*
-
-* Remove implicit conversion of objects into `String` by `ActiveSupport::SafeBuffer`.
-
- *Rafael Mendonça França*
-
-* Remove deprecated `active_support/core_ext/range/include_time_with_zone` file.
-
- *Rafael Mendonça França*
-
-* Deprecate `config.active_support.remove_deprecated_time_with_zone_name`.
-
- *Rafael Mendonça França*
-
-* Remove deprecated override of `ActiveSupport::TimeWithZone.name`.
-
- *Rafael Mendonça França*
-
-* Deprecate `config.active_support.disable_to_s_conversion`.
-
- *Rafael Mendonça França*
-
-* Remove deprecated option to passing a format to `#to_s` in `Array`, `Range`, `Date`, `DateTime`, `Time`,
- `BigDecimal`, `Float` and, `Integer`.
-
- *Rafael Mendonça França*
-
-* Remove deprecated `ActiveSupport::PerThreadRegistry`.
-
- *Rafael Mendonça França*
-
-* Remove deprecated override of `Enumerable#sum`.
-
- *Rafael Mendonça França*
-
-* Deprecated initializing a `ActiveSupport::Cache::MemCacheStore` with an instance of `Dalli::Client`.
-
- Deprecate the undocumented option of providing an already-initialized instance of `Dalli::Client` to `ActiveSupport::Cache::MemCacheStore`. Such clients could be configured with unrecognized options, which could lead to unexpected behavior. Instead, provide addresses as documented.
-
- *aledustet*
-
-* Stub `Time.new()` in `TimeHelpers#travel_to`
-
- ```ruby
- travel_to Time.new(2004, 11, 24) do
- # Inside the `travel_to` block `Time.new` is stubbed
- assert_equal 2004, Time.new.year
- end
- ```
-
- *fatkodima*
-
-* Raise `ActiveSupport::MessageEncryptor::InvalidMessage` from
- `ActiveSupport::MessageEncryptor#decrypt_and_verify` regardless of cipher.
- Previously, when a `MessageEncryptor` was using a non-AEAD cipher such as
- AES-256-CBC, a corrupt or tampered message would raise
- `ActiveSupport::MessageVerifier::InvalidSignature`. Now, all ciphers raise
- the same error:
-
- ```ruby
- encryptor = ActiveSupport::MessageEncryptor.new("x" * 32, cipher: "aes-256-gcm")
- message = encryptor.encrypt_and_sign("message")
- encryptor.decrypt_and_verify(message.next)
- # => raises ActiveSupport::MessageEncryptor::InvalidMessage
-
- encryptor = ActiveSupport::MessageEncryptor.new("x" * 32, cipher: "aes-256-cbc")
- message = encryptor.encrypt_and_sign("message")
- encryptor.decrypt_and_verify(message.next)
- # BEFORE:
- # => raises ActiveSupport::MessageVerifier::InvalidSignature
- # AFTER:
- # => raises ActiveSupport::MessageEncryptor::InvalidMessage
- ```
-
- *Jonathan Hefner*
-
-* Support `nil` original values when using `ActiveSupport::MessageVerifier#verify`.
- Previously, `MessageVerifier#verify` did not work with `nil` original
- values, though both `MessageVerifier#verified` and
- `MessageEncryptor#decrypt_and_verify` do:
-
- ```ruby
- encryptor = ActiveSupport::MessageEncryptor.new(secret)
- message = encryptor.encrypt_and_sign(nil)
-
- encryptor.decrypt_and_verify(message)
- # => nil
-
- verifier = ActiveSupport::MessageVerifier.new(secret)
- message = verifier.generate(nil)
-
- verifier.verified(message)
- # => nil
-
- verifier.verify(message)
- # BEFORE:
- # => raises ActiveSupport::MessageVerifier::InvalidSignature
- # AFTER:
- # => nil
- ```
-
- *Jonathan Hefner*
-
-* Maintain `html_safe?` on html_safe strings when sliced with `slice`, `slice!`, or `chr` method.
-
- Previously, `html_safe?` was only maintained when the html_safe strings were sliced
- with `[]` method. Now, `slice`, `slice!`, and `chr` methods will maintain `html_safe?` like `[]` method.
-
- ```ruby
- string = "test
".html_safe
- string.slice(0, 1).html_safe? # => true
- string.slice!(0, 1).html_safe? # => true
- # maintain html_safe? after the slice!
- string.html_safe? # => true
- string.chr.html_safe? # => true
- ```
-
- *Michael Go*
-
-* Add `Object#in?` support for open ranges.
-
- ```ruby
- assert Date.today.in?(..Date.tomorrow)
- assert_not Date.today.in?(Date.tomorrow..)
- ```
-
- *Ignacio Galindo*
-
-* `config.i18n.raise_on_missing_translations = true` now raises on any missing translation.
-
- Previously it would only raise when called in a view or controller. Now it will raise
- anytime `I18n.t` is provided an unrecognised key.
-
- If you do not want this behaviour, you can customise the i18n exception handler. See the
- upgrading guide or i18n guide for more information.
-
- *Alex Ghiculescu*
-
-* `ActiveSupport::CurrentAttributes` now raises if a restricted attribute name is used.
-
- Attributes such as `set` and `reset` cannot be used as they clash with the
- `CurrentAttributes` public API.
-
- *Alex Ghiculescu*
-
-* `HashWithIndifferentAccess#transform_keys` now takes a Hash argument, just
- as Ruby's `Hash#transform_keys` does.
-
- *Akira Matsuda*
-
-* `delegate` now defines method with proper arity when delegating to a Class.
- With this change, it defines faster method (3.5x faster with no argument).
- However, in order to gain this benefit, the delegation target method has to
- be defined before declaring the delegation.
-
- ```ruby
- # This defines 3.5 times faster method than before
- class C
- def self.x() end
- delegate :x, to: :class
- end
-
- class C
- # This works but silently falls back to old behavior because
- # `delegate` cannot find the definition of `x`
- delegate :x, to: :class
- def self.x() end
- end
- ```
-
- *Akira Matsuda*
-
-* `assert_difference` message now includes what changed.
-
- This makes it easier to debug non-obvious failures.
-
- Before:
-
- ```
- "User.count" didn't change by 32.
- Expected: 1611
- Actual: 1579
- ```
-
- After:
-
- ```
- "User.count" didn't change by 32, but by 0.
- Expected: 1611
- Actual: 1579
- ```
-
- *Alex Ghiculescu*
-
-* Add ability to match exception messages to `assert_raises` assertion
-
- Instead of this
- ```ruby
- error = assert_raises(ArgumentError) do
- perform_service(param: 'exception')
- end
- assert_match(/incorrect param/i, error.message)
- ```
-
- you can now write this
- ```ruby
- assert_raises(ArgumentError, match: /incorrect param/i) do
- perform_service(param: 'exception')
- end
- ```
-
- *fatkodima*
-
-* Add `Rails.env.local?` shorthand for `Rails.env.development? || Rails.env.test?`.
-
- *DHH*
-
-* `ActiveSupport::Testing::TimeHelpers` now accepts named `with_usec` argument
- to `freeze_time`, `travel`, and `travel_to` methods. Passing true prevents
- truncating the destination time with `change(usec: 0)`.
-
- *KevSlashNull*, and *serprex*
-
-* `ActiveSupport::CurrentAttributes.resets` now accepts a method name
-
- The block API is still the recommended approach, but now both APIs are supported:
-
- ```ruby
- class Current < ActiveSupport::CurrentAttributes
- resets { Time.zone = nil }
- resets :clear_time_zone
- end
- ```
-
- *Alex Ghiculescu*
-
-* Ensure `ActiveSupport::Testing::Isolation::Forking` closes pipes
-
- Previously, `Forking.run_in_isolation` opened two ends of a pipe. The fork
- process closed the read end, wrote to it, and then terminated (which
- presumably closed the file descriptors on its end). The parent process
- closed the write end, read from it, and returned, never closing the read
- end.
-
- This resulted in an accumulation of open file descriptors, which could
- cause errors if the limit is reached.
-
- *Sam Bostock*
-
-* Fix `Time#change` and `Time#advance` for times around the end of Daylight
- Saving Time.
-
- Previously, when `Time#change` or `Time#advance` constructed a time inside
- the final stretch of Daylight Saving Time (DST), the non-DST offset would
- always be chosen for local times:
-
- ```ruby
- # DST ended just before 2021-11-07 2:00:00 AM in US/Eastern.
- ENV["TZ"] = "US/Eastern"
-
- time = Time.local(2021, 11, 07, 00, 59, 59) + 1
- # => 2021-11-07 01:00:00 -0400
- time.change(day: 07)
- # => 2021-11-07 01:00:00 -0500
- time.advance(seconds: 0)
- # => 2021-11-07 01:00:00 -0500
-
- time = Time.local(2021, 11, 06, 01, 00, 00)
- # => 2021-11-06 01:00:00 -0400
- time.change(day: 07)
- # => 2021-11-07 01:00:00 -0500
- time.advance(days: 1)
- # => 2021-11-07 01:00:00 -0500
- ```
-
- And the DST offset would always be chosen for times with a `TimeZone`
- object:
-
- ```ruby
- Time.zone = "US/Eastern"
-
- time = Time.new(2021, 11, 07, 02, 00, 00, Time.zone) - 3600
- # => 2021-11-07 01:00:00 -0500
- time.change(day: 07)
- # => 2021-11-07 01:00:00 -0400
- time.advance(seconds: 0)
- # => 2021-11-07 01:00:00 -0400
-
- time = Time.new(2021, 11, 8, 01, 00, 00, Time.zone)
- # => 2021-11-08 01:00:00 -0500
- time.change(day: 07)
- # => 2021-11-07 01:00:00 -0400
- time.advance(days: -1)
- # => 2021-11-07 01:00:00 -0400
- ```
-
- Now, `Time#change` and `Time#advance` will choose the offset that matches
- the original time's offset when possible:
-
- ```ruby
- ENV["TZ"] = "US/Eastern"
-
- time = Time.local(2021, 11, 07, 00, 59, 59) + 1
- # => 2021-11-07 01:00:00 -0400
- time.change(day: 07)
- # => 2021-11-07 01:00:00 -0400
- time.advance(seconds: 0)
- # => 2021-11-07 01:00:00 -0400
-
- time = Time.local(2021, 11, 06, 01, 00, 00)
- # => 2021-11-06 01:00:00 -0400
- time.change(day: 07)
- # => 2021-11-07 01:00:00 -0400
- time.advance(days: 1)
- # => 2021-11-07 01:00:00 -0400
-
- Time.zone = "US/Eastern"
-
- time = Time.new(2021, 11, 07, 02, 00, 00, Time.zone) - 3600
- # => 2021-11-07 01:00:00 -0500
- time.change(day: 07)
- # => 2021-11-07 01:00:00 -0500
- time.advance(seconds: 0)
- # => 2021-11-07 01:00:00 -0500
-
- time = Time.new(2021, 11, 8, 01, 00, 00, Time.zone)
- # => 2021-11-08 01:00:00 -0500
- time.change(day: 07)
- # => 2021-11-07 01:00:00 -0500
- time.advance(days: -1)
- # => 2021-11-07 01:00:00 -0500
- ```
-
- *Kevin Hall*, *Takayoshi Nishida*, and *Jonathan Hefner*
-
-* Fix MemoryStore to preserve entries TTL when incrementing or decrementing
-
- This is to be more consistent with how MemCachedStore and RedisCacheStore behaves.
-
- *Jean Boussier*
-
-* `Rails.error.handle` and `Rails.error.record` filter now by multiple error classes.
-
- ```ruby
- Rails.error.handle(IOError, ArgumentError) do
- 1 + '1' # raises TypeError
- end
- 1 + 1 # TypeErrors are not IOErrors or ArgumentError, so this will *not* be handled
- ```
-
- *Martin Spickermann*
-
-* `Class#subclasses` and `Class#descendants` now automatically filter reloaded classes.
-
- Previously they could return old implementations of reloadable classes that have been
- dereferenced but not yet garbage collected.
-
- They now automatically filter such classes like `DescendantTracker#subclasses` and
- `DescendantTracker#descendants`.
-
- *Jean Boussier*
-
-* `Rails.error.report` now marks errors as reported to avoid reporting them twice.
-
- In some cases, users might want to report errors explicitly with some extra context
- before letting it bubble up.
-
- This also allows to safely catch and report errors outside of the execution context.
-
- *Jean Boussier*
-
-* Add `assert_error_reported` and `assert_no_error_reported`
-
- Allows to easily asserts an error happened but was handled
-
- ```ruby
- report = assert_error_reported(IOError) do
- # ...
- end
- assert_equal "Oops", report.error.message
- assert_equal "admin", report.context[:section]
- assert_equal :warning, report.severity
- assert_predicate report, :handled?
- ```
-
- *Jean Boussier*
-
-* `ActiveSupport::Deprecation` behavior callbacks can now receive the
- deprecator instance as an argument. This makes it easier for such callbacks
- to change their behavior based on the deprecator's state. For example,
- based on the deprecator's `debug` flag.
-
- 3-arity and splat-args callbacks such as the following will now be passed
- the deprecator instance as their third argument:
-
- * `->(message, callstack, deprecator) { ... }`
- * `->(*args) { ... }`
- * `->(message, *other_args) { ... }`
-
- 2-arity and 4-arity callbacks such as the following will continue to behave
- the same as before:
-
- * `->(message, callstack) { ... }`
- * `->(message, callstack, deprecation_horizon, gem_name) { ... }`
- * `->(message, callstack, *deprecation_details) { ... }`
-
- *Jonathan Hefner*
-
-* `ActiveSupport::Deprecation#disallowed_warnings` now affects the instance on
- which it is configured.
-
- This means that individual `ActiveSupport::Deprecation` instances can be
- configured with their own disallowed warnings, and the global
- `ActiveSupport::Deprecation.disallowed_warnings` now only affects the global
- `ActiveSupport::Deprecation.warn`.
-
- **Before**
-
- ```ruby
- ActiveSupport::Deprecation.disallowed_warnings = ["foo"]
- deprecator = ActiveSupport::Deprecation.new("2.0", "MyCoolGem")
- deprecator.disallowed_warnings = ["bar"]
-
- ActiveSupport::Deprecation.warn("foo") # => raise ActiveSupport::DeprecationException
- ActiveSupport::Deprecation.warn("bar") # => print "DEPRECATION WARNING: bar"
- deprecator.warn("foo") # => raise ActiveSupport::DeprecationException
- deprecator.warn("bar") # => print "DEPRECATION WARNING: bar"
- ```
-
- **After**
-
- ```ruby
- ActiveSupport::Deprecation.disallowed_warnings = ["foo"]
- deprecator = ActiveSupport::Deprecation.new("2.0", "MyCoolGem")
- deprecator.disallowed_warnings = ["bar"]
-
- ActiveSupport::Deprecation.warn("foo") # => raise ActiveSupport::DeprecationException
- ActiveSupport::Deprecation.warn("bar") # => print "DEPRECATION WARNING: bar"
- deprecator.warn("foo") # => print "DEPRECATION WARNING: foo"
- deprecator.warn("bar") # => raise ActiveSupport::DeprecationException
- ```
-
- Note that global `ActiveSupport::Deprecation` methods such as `ActiveSupport::Deprecation.warn`
- and `ActiveSupport::Deprecation.disallowed_warnings` have been deprecated.
-
- *Jonathan Hefner*
-
-* Add italic and underline support to `ActiveSupport::LogSubscriber#color`
-
- Previously, only bold text was supported via a positional argument.
- This allows for bold, italic, and underline options to be specified
- for colored logs.
-
- ```ruby
- info color("Hello world!", :red, bold: true, underline: true)
- ```
-
- *Gannon McGibbon*
-
-* Add `String#downcase_first` method.
-
- This method is the corollary of `String#upcase_first`.
-
- *Mark Schneider*
-
-* `thread_mattr_accessor` will call `.dup.freeze` on non-frozen default values.
-
- This provides a basic level of protection against different threads trying
- to mutate a shared default object.
-
- *Jonathan Hefner*
-
-* Add `raise_on_invalid_cache_expiration_time` config to `ActiveSupport::Cache::Store`
-
- Specifies if an `ArgumentError` should be raised if `Rails.cache` `fetch` or
- `write` are given an invalid `expires_at` or `expires_in` time.
-
- Options are `true`, and `false`. If `false`, the exception will be reported
- as `handled` and logged instead. Defaults to `true` if `config.load_defaults >= 7.1`.
-
- *Trevor Turk*
-
-* `ActiveSupport::Cache:Store#fetch` now passes an options accessor to the block.
-
- It makes possible to override cache options:
-
- Rails.cache.fetch("3rd-party-token") do |name, options|
- token = fetch_token_from_remote
- # set cache's TTL to match token's TTL
- options.expires_in = token.expires_in
- token
- end
-
- *Andrii Gladkyi*, *Jean Boussier*
-
-* `default` option of `thread_mattr_accessor` now applies through inheritance and
- also across new threads.
-
- Previously, the `default` value provided was set only at the moment of defining
- the attribute writer, which would cause the attribute to be uninitialized in
- descendants and in other threads.
-
- Fixes #43312.
-
- *Thierry Deo*
-
-* Redis cache store is now compatible with redis-rb 5.0.
-
- *Jean Boussier*
-
-* Add `skip_nil:` support to `ActiveSupport::Cache::Store#fetch_multi`.
-
- *Daniel Alfaro*
-
-* Add `quarter` method to date/time
-
- *Matt Swanson*
-
-* Fix `NoMethodError` on custom `ActiveSupport::Deprecation` behavior.
-
- `ActiveSupport::Deprecation.behavior=` was supposed to accept any object
- that responds to `call`, but in fact its internal implementation assumed that
- this object could respond to `arity`, so it was restricted to only `Proc` objects.
-
- This change removes this `arity` restriction of custom behaviors.
-
- *Ryo Nakamura*
-
-* Support `:url_safe` option for `MessageEncryptor`.
-
- The `MessageEncryptor` constructor now accepts a `:url_safe` option, similar
- to the `MessageVerifier` constructor. When enabled, this option ensures
- that messages use a URL-safe encoding.
-
- *Jonathan Hefner*
-
-* Add `url_safe` option to `ActiveSupport::MessageVerifier` initializer
-
- `ActiveSupport::MessageVerifier.new` now takes optional `url_safe` argument.
- It can generate URL-safe strings by passing `url_safe: true`.
-
- ```ruby
- verifier = ActiveSupport::MessageVerifier.new(url_safe: true)
- message = verifier.generate(data) # => URL-safe string
- ```
-
- This option is `false` by default to be backwards compatible.
-
- *Shouichi Kamiya*
-
-* Enable connection pooling by default for `MemCacheStore` and `RedisCacheStore`.
-
- If you want to disable connection pooling, set `:pool` option to `false` when configuring the cache store:
-
- ```ruby
- config.cache_store = :mem_cache_store, "cache.example.com", pool: false
- ```
-
- *fatkodima*
-
-* Add `force:` support to `ActiveSupport::Cache::Store#fetch_multi`.
-
- *fatkodima*
-
-* Deprecated `:pool_size` and `:pool_timeout` options for configuring connection pooling in cache stores.
-
- Use `pool: true` to enable pooling with default settings:
-
- ```ruby
- config.cache_store = :redis_cache_store, pool: true
- ```
-
- Or pass individual options via `:pool` option:
-
- ```ruby
- config.cache_store = :redis_cache_store, pool: { size: 10, timeout: 2 }
- ```
-
- *fatkodima*
-
-* Allow #increment and #decrement methods of `ActiveSupport::Cache::Store`
- subclasses to set new values.
-
- Previously incrementing or decrementing an unset key would fail and return
- nil. A default will now be assumed and the key will be created.
-
- *Andrej Blagojević*, *Eugene Kenny*
-
-* Add `skip_nil:` support to `RedisCacheStore`
-
- *Joey Paris*
-
-* `ActiveSupport::Cache::MemoryStore#write(name, val, unless_exist:true)` now
- correctly writes expired keys.
-
- *Alan Savage*
-
-* `ActiveSupport::ErrorReporter` now accepts and forward a `source:` parameter.
-
- This allow libraries to signal the origin of the errors, and reporters
- to easily ignore some sources.
-
- *Jean Boussier*
-
-* Fix and add protections for XSS in `ActionView::Helpers` and `ERB::Util`.
-
- Add the method `ERB::Util.xml_name_escape` to escape dangerous characters
- in names of tags and names of attributes, following the specification of XML.
-
- *Álvaro Martín Fraguas*
-
-* Respect `ActiveSupport::Logger.new`'s `:formatter` keyword argument
-
- The stdlib `Logger::new` allows passing a `:formatter` keyword argument to
- set the logger's formatter. Previously `ActiveSupport::Logger.new` ignored
- that argument by always setting the formatter to an instance of
- `ActiveSupport::Logger::SimpleFormatter`.
-
- *Steven Harman*
-
-* Deprecate preserving the pre-Ruby 2.4 behavior of `to_time`
-
- With Ruby 2.4+ the default for +to_time+ changed from converting to the
- local system time to preserving the offset of the receiver. At the time Rails
- supported older versions of Ruby so a compatibility layer was added to assist
- in the migration process. From Rails 5.0 new applications have defaulted to
- the Ruby 2.4+ behavior and since Rails 7.0 now only supports Ruby 2.7+
- this compatibility layer can be safely removed.
-
- To minimize any noise generated the deprecation warning only appears when the
- setting is configured to `false` as that is the only scenario where the
- removal of the compatibility layer has any effect.
-
- *Andrew White*
-
-* `Pathname.blank?` only returns true for `Pathname.new("")`
-
- Previously it would end up calling `Pathname#empty?` which returned true
- if the path existed and was an empty directory or file.
-
- That behavior was unlikely to be expected.
-
- *Jean Boussier*
-
-* Deprecate `Notification::Event`'s `#children` and `#parent_of?`
-
- *John Hawthorn*
-
-* Change the default serializer of `ActiveSupport::MessageVerifier` from
- `Marshal` to `ActiveSupport::JSON` when using `config.load_defaults 7.1`.
-
- Messages serialized with `Marshal` can still be read, but new messages will
- be serialized with `ActiveSupport::JSON`. For more information, see
- https://guides.rubyonrails.org/v7.1/configuring.html#config-active-support-message-serializer.
-
- *Saba Kiaei*, *David Buckley*, and *Jonathan Hefner*
-
-* Change the default serializer of `ActiveSupport::MessageEncryptor` from
- `Marshal` to `ActiveSupport::JSON` when using `config.load_defaults 7.1`.
-
- Messages serialized with `Marshal` can still be read, but new messages will
- be serialized with `ActiveSupport::JSON`. For more information, see
- https://guides.rubyonrails.org/v7.1/configuring.html#config-active-support-message-serializer.
-
- *Zack Deveau*, *Martin Gingras*, and *Jonathan Hefner*
-
-* Add `ActiveSupport::TestCase#stub_const` to stub a constant for the duration of a yield.
-
- *DHH*
-
-* Fix `ActiveSupport::EncryptedConfiguration` to be compatible with Psych 4
-
- *Stephen Sugden*
-
-* Improve `File.atomic_write` error handling
-
- *Daniel Pepper*
-
-* Fix `Class#descendants` and `DescendantsTracker#descendants` compatibility with Ruby 3.1.
-
- [The native `Class#descendants` was reverted prior to Ruby 3.1 release](https://bugs.ruby-lang.org/issues/14394#note-33),
- but `Class#subclasses` was kept, breaking the feature detection.
-
- *Jean Boussier*
-
-Please check [7-0-stable](https://github.com/rails/rails/blob/7-0-stable/activesupport/CHANGELOG.md) for previous changes.
+Please check [7-1-stable](https://github.com/rails/rails/blob/7-1-stable/activesupport/CHANGELOG.md) for previous changes.
diff --git a/activesupport/lib/active_support/deprecation.rb b/activesupport/lib/active_support/deprecation.rb
index 1feb4af2f7c..ad96ecb946f 100644
--- a/activesupport/lib/active_support/deprecation.rb
+++ b/activesupport/lib/active_support/deprecation.rb
@@ -65,7 +65,7 @@ module ActiveSupport
# and the second is a library name.
#
# ActiveSupport::Deprecation.new('2.0', 'MyLibrary')
- def initialize(deprecation_horizon = "7.2", gem_name = "Rails")
+ def initialize(deprecation_horizon = "7.3", gem_name = "Rails")
self.gem_name = gem_name
self.deprecation_horizon = deprecation_horizon
# By default, warnings are not silenced and debugging is off.
diff --git a/activesupport/lib/active_support/gem_version.rb b/activesupport/lib/active_support/gem_version.rb
index 775b21d3a56..eada318028a 100644
--- a/activesupport/lib/active_support/gem_version.rb
+++ b/activesupport/lib/active_support/gem_version.rb
@@ -8,9 +8,9 @@ module ActiveSupport
module VERSION
MAJOR = 7
- MINOR = 1
+ MINOR = 2
TINY = 0
- PRE = "rc1"
+ PRE = "alpha"
STRING = [MAJOR, MINOR, TINY, PRE].compact.join(".")
end
diff --git a/guides/CHANGELOG.md b/guides/CHANGELOG.md
index 70ac22afb41..f85e179b8b9 100644
--- a/guides/CHANGELOG.md
+++ b/guides/CHANGELOG.md
@@ -1,12 +1,2 @@
-## Rails 7.1.0.rc1 (September 27, 2023) ##
-* No changes.
-
-
-## Rails 7.1.0.beta1 (September 13, 2023) ##
-
-* Add "back to top" button to guides
-
- *Alysson Rosa*
-
-Please check [7-0-stable](https://github.com/rails/rails/blob/7-0-stable/guides/CHANGELOG.md) for previous changes.
+Please check [7-1-stable](https://github.com/rails/rails/blob/7-1-stable/guides/CHANGELOG.md) for previous changes.
diff --git a/guides/bug_report_templates/active_record_migrations_main.rb b/guides/bug_report_templates/active_record_migrations_main.rb
index 5836db3b7e2..49f7272447b 100644
--- a/guides/bug_report_templates/active_record_migrations_main.rb
+++ b/guides/bug_report_templates/active_record_migrations_main.rb
@@ -28,7 +28,7 @@ end
class Payment < ActiveRecord::Base
end
-class ChangeAmountToAddScale < ActiveRecord::Migration[7.1]
+class ChangeAmountToAddScale < ActiveRecord::Migration[7.2]
def change
reversible do |dir|
dir.up do
diff --git a/guides/source/7_2_release_notes.md b/guides/source/7_2_release_notes.md
new file mode 100644
index 00000000000..98d3a44464f
--- /dev/null
+++ b/guides/source/7_2_release_notes.md
@@ -0,0 +1,88 @@
+**DO NOT READ THIS FILE ON GITHUB, GUIDES ARE PUBLISHED ON https://guides.rubyonrails.org.**
+
+Ruby on Rails 7.2 Release Notes
+===============================
+
+Highlights in Rails 7.2:
+
+--------------------------------------------------------------------------------
+
+Upgrading to Rails 7.1
+----------------------
+
+If you're upgrading an existing application, it's a great idea to have good test
+coverage before going in. You should also first upgrade to Rails 7.1 in case you
+haven't and make sure your application still runs as expected before attempting
+an update to Rails 7.2. A list of things to watch out for when upgrading is
+available in the
+[Upgrading Ruby on Rails](upgrading_ruby_on_rails.html#upgrading-from-rails-7-1-to-rails-7-2)
+guide.
+
+Major Features
+--------------
+
+
+Railties
+--------
+
+Action Cable
+------------
+
+Action Pack
+-----------
+
+Action View
+-----------
+
+Action Mailer
+-------------
+
+Active Record
+-------------
+
+Active Storage
+--------------
+
+Active Model
+------------
+
+Active Support
+--------------
+
+Active Job
+----------
+
+Action Text
+----------
+
+Action Mailbox
+----------
+
+Ruby on Rails Guides
+--------------------
+
+Please refer to the [Changelog][guides] for detailed changes.
+
+### Notable changes
+
+Credits
+-------
+
+See the
+[full list of contributors to Rails](https://contributors.rubyonrails.org/)
+for the many people who spent many hours making Rails, the stable and robust
+framework it is. Kudos to all of them.
+
+[railties]: https://github.com/rails/rails/blob/main/railties/CHANGELOG.md
+[action-pack]: https://github.com/rails/rails/blob/main/actionpack/CHANGELOG.md
+[action-view]: https://github.com/rails/rails/blob/main/actionview/CHANGELOG.md
+[action-mailer]: https://github.com/rails/rails/blob/main/actionmailer/CHANGELOG.md
+[action-cable]: https://github.com/rails/rails/blob/main/actioncable/CHANGELOG.md
+[active-record]: https://github.com/rails/rails/blob/main/activerecord/CHANGELOG.md
+[active-storage]: https://github.com/rails/rails/blob/main/activestorage/CHANGELOG.md
+[active-model]: https://github.com/rails/rails/blob/main/activemodel/CHANGELOG.md
+[active-support]: https://github.com/rails/rails/blob/main/activesupport/CHANGELOG.md
+[active-job]: https://github.com/rails/rails/blob/main/activejob/CHANGELOG.md
+[action-text]: https://github.com/rails/rails/blob/main/actiontext/CHANGELOG.md
+[action-mailbox]: https://github.com/rails/rails/blob/main/actionmailbox/CHANGELOG.md
+[guides]: https://github.com/rails/rails/blob/main/guides/CHANGELOG.md
diff --git a/guides/source/_welcome.html.erb b/guides/source/_welcome.html.erb
index 8325b4cb60a..2a9d5490e73 100644
--- a/guides/source/_welcome.html.erb
+++ b/guides/source/_welcome.html.erb
@@ -10,12 +10,13 @@
<% else %>
- These are the new guides for Rails 7.1 based on <%= @version %>.
+ These are the new guides for Rails 7.2 based on <%= @version %>.
These guides are designed to make you immediately productive with Rails, and to help you understand how all of the pieces fit together.
<% end %>
The guides for earlier releases:
+Rails 7.1,
Rails 7.0,
Rails 6.1,
Rails 6.0,
diff --git a/guides/source/active_record_basics.md b/guides/source/active_record_basics.md
index 8f11320b768..11c7d3b3377 100644
--- a/guides/source/active_record_basics.md
+++ b/guides/source/active_record_basics.md
@@ -410,7 +410,7 @@ in files which are executed against any database that Active Record supports.
Here's a migration that creates a new table called `publications`:
```ruby
-class CreatePublications < ActiveRecord::Migration[7.1]
+class CreatePublications < ActiveRecord::Migration[7.2]
def change
create_table :publications do |t|
t.string :title
diff --git a/guides/source/active_record_composite_primary_keys.md b/guides/source/active_record_composite_primary_keys.md
index 1bef356d94d..d4e681034b1 100644
--- a/guides/source/active_record_composite_primary_keys.md
+++ b/guides/source/active_record_composite_primary_keys.md
@@ -36,7 +36,7 @@ You can create a table with a composite primary key by passing the
`:primary_key` option to `create_table` with an array value:
```ruby
-class CreateProducts < ActiveRecord::Migration[7.1]
+class CreateProducts < ActiveRecord::Migration[7.2]
def change
create_table :products, primary_key: [:store_id, :sku] do |t|
t.integer :store_id
diff --git a/guides/source/active_record_migrations.md b/guides/source/active_record_migrations.md
index a6e39253e79..ad1d353d98c 100644
--- a/guides/source/active_record_migrations.md
+++ b/guides/source/active_record_migrations.md
@@ -34,7 +34,7 @@ history to the latest version. Active Record will also update your
Here's an example of a migration:
```ruby
-class CreateProducts < ActiveRecord::Migration[7.1]
+class CreateProducts < ActiveRecord::Migration[7.2]
def change
create_table :products do |t|
t.string :name
@@ -73,7 +73,7 @@ If you wish for a migration to do something that Active Record doesn't know how
to reverse, you can use `reversible`:
```ruby
-class ChangeProductsPrice < ActiveRecord::Migration[7.1]
+class ChangeProductsPrice < ActiveRecord::Migration[7.2]
def change
reversible do |direction|
change_table :products do |t|
@@ -92,7 +92,7 @@ passed to `direction.up` and `direction.down` respectively.
Alternatively, you can use `up` and `down` instead of `change`:
```ruby
-class ChangeProductsPrice < ActiveRecord::Migration[7.1]
+class ChangeProductsPrice < ActiveRecord::Migration[7.2]
def up
change_table :products do |t|
t.change :price, :string
@@ -136,7 +136,7 @@ $ bin/rails generate migration AddPartNumberToProducts
This will create an appropriately named empty migration:
```ruby
-class AddPartNumberToProducts < ActiveRecord::Migration[7.1]
+class AddPartNumberToProducts < ActiveRecord::Migration[7.2]
def change
end
end
@@ -160,7 +160,7 @@ $ bin/rails generate migration AddPartNumberToProducts part_number:string
This will generate the following migration:
```ruby
-class AddPartNumberToProducts < ActiveRecord::Migration[7.1]
+class AddPartNumberToProducts < ActiveRecord::Migration[7.2]
def change
add_column :products, :part_number, :string
end
@@ -176,7 +176,7 @@ $ bin/rails generate migration AddPartNumberToProducts part_number:string:index
This will generate the appropriate [`add_column`][] and [`add_index`][] statements:
```ruby
-class AddPartNumberToProducts < ActiveRecord::Migration[7.1]
+class AddPartNumberToProducts < ActiveRecord::Migration[7.2]
def change
add_column :products, :part_number, :string
add_index :products, :part_number
@@ -194,7 +194,7 @@ Will generate a schema migration which adds two additional
columns to the `products` table.
```ruby
-class AddDetailsToProducts < ActiveRecord::Migration[7.1]
+class AddDetailsToProducts < ActiveRecord::Migration[7.2]
def change
add_column :products, :part_number, :string
add_column :products, :price, :decimal
@@ -213,7 +213,7 @@ $ bin/rails generate migration RemovePartNumberFromProducts part_number:string
This generates the appropriate [`remove_column`][] statements:
```ruby
-class RemovePartNumberFromProducts < ActiveRecord::Migration[7.1]
+class RemovePartNumberFromProducts < ActiveRecord::Migration[7.2]
def change
remove_column :products, :part_number, :string
end
@@ -233,7 +233,7 @@ $ bin/rails generate migration CreateProducts name:string part_number:string
generates
```ruby
-class CreateProducts < ActiveRecord::Migration[7.1]
+class CreateProducts < ActiveRecord::Migration[7.2]
def change
create_table :products do |t|
t.string :name
@@ -261,7 +261,7 @@ $ bin/rails generate migration AddUserRefToProducts user:references
generates the following [`add_reference`][] call:
```ruby
-class AddUserRefToProducts < ActiveRecord::Migration[7.1]
+class AddUserRefToProducts < ActiveRecord::Migration[7.2]
def change
add_reference :products, :user, foreign_key: true
end
@@ -281,7 +281,7 @@ $ bin/rails generate migration CreateJoinTableCustomerProduct customer product
will produce the following migration:
```ruby
-class CreateJoinTableCustomerProduct < ActiveRecord::Migration[7.1]
+class CreateJoinTableCustomerProduct < ActiveRecord::Migration[7.2]
def change
create_join_table :customers, :products do |t|
# t.index [:customer_id, :product_id]
@@ -310,7 +310,7 @@ $ bin/rails generate model Product name:string description:text
This will create a migration that looks like this:
```ruby
-class CreateProducts < ActiveRecord::Migration[7.1]
+class CreateProducts < ActiveRecord::Migration[7.2]
def change
create_table :products do |t|
t.string :name
@@ -338,7 +338,7 @@ $ bin/rails generate migration AddDetailsToProducts 'price:decimal{5,2}' supplie
will produce a migration that looks like this
```ruby
-class AddDetailsToProducts < ActiveRecord::Migration[7.1]
+class AddDetailsToProducts < ActiveRecord::Migration[7.2]
def change
add_column :products, :price, :decimal, precision: 5, scale: 2
add_reference :products, :supplier, polymorphic: true
@@ -635,7 +635,7 @@ You can create a table with a composite primary key by passing the
`:primary_key` option to `create_table` with an array value:
```ruby
-class CreateProducts < ActiveRecord::Migration[7.1]
+class CreateProducts < ActiveRecord::Migration[7.2]
def change
create_table :products, primary_key: [:customer_id, :product_sku] do |t|
t.integer :customer_id
@@ -744,7 +744,7 @@ reverse. You can use [`reversible`][] to specify what to do when running a
migration and what else to do when reverting it. For example:
```ruby
-class ExampleMigration < ActiveRecord::Migration[7.1]
+class ExampleMigration < ActiveRecord::Migration[7.2]
def change
create_table :distributors do |t|
t.string :zipcode
@@ -795,7 +795,7 @@ reverse order they were made in the `up` method. The example in the `reversible`
section is equivalent to:
```ruby
-class ExampleMigration < ActiveRecord::Migration[7.1]
+class ExampleMigration < ActiveRecord::Migration[7.2]
def up
create_table :distributors do |t|
t.string :zipcode
@@ -843,7 +843,7 @@ You can use Active Record's ability to rollback migrations using the [`revert`][
```ruby
require_relative "20121212123456_example_migration"
-class FixupExampleMigration < ActiveRecord::Migration[7.1]
+class FixupExampleMigration < ActiveRecord::Migration[7.2]
def change
revert ExampleMigration
@@ -861,7 +861,7 @@ For example, let's imagine that `ExampleMigration` is committed and it is later
decided that a Distributors view is no longer needed.
```ruby
-class DontUseDistributorsViewMigration < ActiveRecord::Migration[7.1]
+class DontUseDistributorsViewMigration < ActiveRecord::Migration[7.2]
def change
revert do
# copy-pasted code from ExampleMigration
@@ -1039,7 +1039,7 @@ Several methods are provided in migrations that allow you to control all this:
For example, take the following migration:
```ruby
-class CreateProducts < ActiveRecord::Migration[7.1]
+class CreateProducts < ActiveRecord::Migration[7.2]
def change
suppress_messages do
create_table :products do |t|
@@ -1144,7 +1144,7 @@ When `:ruby` is selected, then the schema is stored in `db/schema.rb`. If you lo
at this file you'll find that it looks an awful lot like one very big migration:
```ruby
-ActiveRecord::Schema[7.1].define(version: 2008_09_06_171750) do
+ActiveRecord::Schema[7.2].define(version: 2008_09_06_171750) do
create_table "authors", force: true do |t|
t.string "name"
t.datetime "created_at"
@@ -1229,7 +1229,7 @@ modify data. This is useful in an existing database that can't be destroyed and
recreated, such as a production database.
```ruby
-class AddInitialProducts < ActiveRecord::Migration[7.1]
+class AddInitialProducts < ActiveRecord::Migration[7.2]
def up
5.times do |i|
Product.create(name: "Product ##{i}", description: "A product.")
diff --git a/guides/source/association_basics.md b/guides/source/association_basics.md
index d40e440ab15..1075b94736d 100644
--- a/guides/source/association_basics.md
+++ b/guides/source/association_basics.md
@@ -112,7 +112,7 @@ NOTE: `belongs_to` associations _must_ use the singular term. If you used the pl
The corresponding migration might look like this:
```ruby
-class CreateBooks < ActiveRecord::Migration[7.1]
+class CreateBooks < ActiveRecord::Migration[7.2]
def change
create_table :authors do |t|
t.string :name
@@ -159,7 +159,7 @@ The main difference from `belongs_to` is that the link column `supplier_id` is l
The corresponding migration might look like this:
```ruby
-class CreateSuppliers < ActiveRecord::Migration[7.1]
+class CreateSuppliers < ActiveRecord::Migration[7.2]
def change
create_table :suppliers do |t|
t.string :name
@@ -205,7 +205,7 @@ NOTE: The name of the other model is pluralized when declaring a `has_many` asso
The corresponding migration might look like this:
```ruby
-class CreateAuthors < ActiveRecord::Migration[7.1]
+class CreateAuthors < ActiveRecord::Migration[7.2]
def change
create_table :authors do |t|
t.string :name
@@ -257,7 +257,7 @@ end
The corresponding migration might look like this:
```ruby
-class CreateAppointments < ActiveRecord::Migration[7.1]
+class CreateAppointments < ActiveRecord::Migration[7.2]
def change
create_table :physicians do |t|
t.string :name
@@ -343,7 +343,7 @@ end
The corresponding migration might look like this:
```ruby
-class CreateAccountHistories < ActiveRecord::Migration[7.1]
+class CreateAccountHistories < ActiveRecord::Migration[7.2]
def change
create_table :suppliers do |t|
t.string :name
@@ -386,7 +386,7 @@ end
The corresponding migration might look like this:
```ruby
-class CreateAssembliesAndParts < ActiveRecord::Migration[7.1]
+class CreateAssembliesAndParts < ActiveRecord::Migration[7.2]
def change
create_table :assemblies do |t|
t.string :name
@@ -425,7 +425,7 @@ end
The corresponding migration might look like this:
```ruby
-class CreateSuppliers < ActiveRecord::Migration[7.1]
+class CreateSuppliers < ActiveRecord::Migration[7.2]
def change
create_table :suppliers do |t|
t.string :name
@@ -510,7 +510,7 @@ Similarly, you can retrieve `@product.pictures`.
If you have an instance of the `Picture` model, you can get to its parent via `@picture.imageable`. To make this work, you need to declare both a foreign key column and a type column in the model that declares the polymorphic interface:
```ruby
-class CreatePictures < ActiveRecord::Migration[7.1]
+class CreatePictures < ActiveRecord::Migration[7.2]
def change
create_table :pictures do |t|
t.string :name
@@ -527,7 +527,7 @@ end
This migration can be simplified by using the `t.references` form:
```ruby
-class CreatePictures < ActiveRecord::Migration[7.1]
+class CreatePictures < ActiveRecord::Migration[7.2]
def change
create_table :pictures do |t|
t.string :name
@@ -622,7 +622,7 @@ With this setup, you can retrieve `@employee.subordinates` and `@employee.manage
In your migrations/schema, you will add a references column to the model itself.
```ruby
-class CreateEmployees < ActiveRecord::Migration[7.1]
+class CreateEmployees < ActiveRecord::Migration[7.2]
def change
create_table :employees do |t|
t.references :manager, foreign_key: { to_table: :employees }
@@ -696,7 +696,7 @@ end
This declaration needs to be backed up by a corresponding foreign key column in the books table. For a brand new table, the migration might look something like this:
```ruby
-class CreateBooks < ActiveRecord::Migration[7.1]
+class CreateBooks < ActiveRecord::Migration[7.2]
def change
create_table :books do |t|
t.datetime :published_at
@@ -710,7 +710,7 @@ end
Whereas for an existing table, it might look like this:
```ruby
-class AddAuthorToBooks < ActiveRecord::Migration[7.1]
+class AddAuthorToBooks < ActiveRecord::Migration[7.2]
def change
add_reference :books, :author
end
@@ -742,7 +742,7 @@ end
These need to be backed up by a migration to create the `assemblies_parts` table. This table should be created without a primary key:
```ruby
-class CreateAssembliesPartsJoinTable < ActiveRecord::Migration[7.1]
+class CreateAssembliesPartsJoinTable < ActiveRecord::Migration[7.2]
def change
create_table :assemblies_parts, id: false do |t|
t.bigint :assembly_id
@@ -760,7 +760,7 @@ We pass `id: false` to `create_table` because that table does not represent a mo
For simplicity, you can also use the method `create_join_table`:
```ruby
-class CreateAssembliesPartsJoinTable < ActiveRecord::Migration[7.1]
+class CreateAssembliesPartsJoinTable < ActiveRecord::Migration[7.2]
def change
create_join_table :assemblies, :parts do |t|
t.index :assembly_id
diff --git a/guides/source/command_line.md b/guides/source/command_line.md
index ead3642ab9c..5e0493e6e95 100644
--- a/guides/source/command_line.md
+++ b/guides/source/command_line.md
@@ -410,7 +410,7 @@ If you wish to test out some code without changing any data, you can do that by
```bash
$ bin/rails console --sandbox
-Loading development environment in sandbox (Rails 7.1.0)
+Loading development environment in sandbox (Rails 7.2.0)
Any modifications you make will be rolled back on exit
irb(main):001:0>
```
diff --git a/guides/source/contributing_to_ruby_on_rails.md b/guides/source/contributing_to_ruby_on_rails.md
index c31e19ca3b8..0eb985f7fa6 100644
--- a/guides/source/contributing_to_ruby_on_rails.md
+++ b/guides/source/contributing_to_ruby_on_rails.md
@@ -614,7 +614,7 @@ To ease the upgrade it's required to add the new default to the
value:
```ruby
-# new_framework_defaults_7_1.rb.tt
+# new_framework_defaults_7_2.rb.tt
# Rails.application.config.active_job.existing_behavior = false
```
diff --git a/guides/source/debugging_rails_applications.md b/guides/source/debugging_rails_applications.md
index 8c6817ab4d5..64a34893928 100644
--- a/guides/source/debugging_rails_applications.md
+++ b/guides/source/debugging_rails_applications.md
@@ -378,7 +378,7 @@ Processing by PostsController#index as HTML
10| # GET /posts/1 or /posts/1.json
11| def show
=>#0 PostsController#index at ~/projects/rails-guide-example/app/controllers/posts_controller.rb:7
- #1 ActionController::BasicImplicitRender#send_action(method="index", args=[]) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-7.1.0.alpha/lib/action_controller/metal/basic_implicit_render.rb:6
+ #1 ActionController::BasicImplicitRender#send_action(method="index", args=[]) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-7.2.0.alpha/lib/action_controller/metal/basic_implicit_render.rb:6
# and 72 frames (use `bt' command for all frames)
(rdbg)
```
@@ -444,14 +444,14 @@ When used without any options, `backtrace` lists all the frames on the stack:
```rb
=>#0 PostsController#index at ~/projects/rails-guide-example/app/controllers/posts_controller.rb:7
- #1 ActionController::BasicImplicitRender#send_action(method="index", args=[]) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-7.1.0.alpha/lib/action_controller/metal/basic_implicit_render.rb:6
- #2 AbstractController::Base#process_action(method_name="index", args=[]) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-7.1.0.alpha/lib/abstract_controller/base.rb:214
- #3 ActionController::Rendering#process_action(#arg_rest=nil) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-7.1.0.alpha/lib/action_controller/metal/rendering.rb:53
- #4 block in process_action at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-7.1.0.alpha/lib/abstract_controller/callbacks.rb:221
- #5 block in run_callbacks at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-7.1.0.alpha/lib/active_support/callbacks.rb:118
- #6 ActionText::Rendering::ClassMethods#with_renderer(renderer=#) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actiontext-7.1.0.alpha/lib/action_text/rendering.rb:20
- #7 block {|controller=#, action=# (4 levels) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actiontext-7.1.0.alpha/lib/action_text/engine.rb:69
- #8 [C] BasicObject#instance_exec at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-7.1.0.alpha/lib/active_support/callbacks.rb:127
+ #1 ActionController::BasicImplicitRender#send_action(method="index", args=[]) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-2.0.alpha/lib/action_controller/metal/basic_implicit_render.rb:6
+ #2 AbstractController::Base#process_action(method_name="index", args=[]) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-7.2.0.alpha/lib/abstract_controller/base.rb:214
+ #3 ActionController::Rendering#process_action(#arg_rest=nil) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-7.2.0.alpha/lib/action_controller/metal/rendering.rb:53
+ #4 block in process_action at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actionpack-7.2.0.alpha/lib/abstract_controller/callbacks.rb:221
+ #5 block in run_callbacks at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-7.2.0.alpha/lib/active_support/callbacks.rb:118
+ #6 ActionText::Rendering::ClassMethods#with_renderer(renderer=#) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actiontext-7.2.0.alpha/lib/action_text/rendering.rb:20
+ #7 block {|controller=#, action=# (4 levels) at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/actiontext-7.2.0.alpha/lib/action_text/engine.rb:69
+ #8 [C] BasicObject#instance_exec at ~/.rbenv/versions/3.0.1/lib/ruby/gems/3.0.0/gems/activesupport-7.2.0.alpha/lib/active_support/callbacks.rb:127
..... and more
```
diff --git a/guides/source/documents.yaml b/guides/source/documents.yaml
index b0b583cca20..6f7c4f64a8e 100644
--- a/guides/source/documents.yaml
+++ b/guides/source/documents.yaml
@@ -331,6 +331,11 @@
description: >
This guide provides steps to be followed when you upgrade your
applications to a newer version of Ruby on Rails.
+ -
+ name: Version 7.2 - ?
+ url: 7_2_release_notes.html
+ description: Release notes for Rails 7.1.
+ work_in_progress: true
-
name: Version 7.1 - ?
url: 7_1_release_notes.html
diff --git a/guides/source/maintenance_policy.md b/guides/source/maintenance_policy.md
index 3519adc8c16..4d1f87998f9 100644
--- a/guides/source/maintenance_policy.md
+++ b/guides/source/maintenance_policy.md
@@ -53,7 +53,7 @@ For unsupported series, bug fixes may coincidentally land in a stable branch,
but won't be released in an official version. It is recommended to point your
application at the stable branch using Git for unsupported versions.
-**Currently included series:** `7.1.Z`.
+**Currently included series:** `7.2.Z`.
Security Issues
---------------
@@ -78,7 +78,7 @@ there could be breaking changes in the security release. A security release
should only contain the changes needed to ensure the app is secure so that it's
easier for applications to remain upgraded.
-**Currently included series:** `7.1.Z`, `7.0.Z`, `6.1.Z`.
+**Currently included series:** `7.2.Z`, `7.1.Z`.
Severe Security Issues
----------------------
@@ -87,7 +87,7 @@ For severe security issues all releases in the current major series, and also th
last release in the previous major series will receive patches and new versions. The
classification of the security issue is judged by the core team.
-**Currently included series:** `7.1.Z`, `7.0.Z`, `6.1.Z`.
+**Currently included series:** `7.2.Z`, `7.1.Z`, `7.0.Z`, `6.1.Z`.
Unsupported Release Series
--------------------------
diff --git a/guides/source/upgrading_ruby_on_rails.md b/guides/source/upgrading_ruby_on_rails.md
index defd0a5e9e1..20e86e90af4 100644
--- a/guides/source/upgrading_ruby_on_rails.md
+++ b/guides/source/upgrading_ruby_on_rails.md
@@ -63,7 +63,7 @@ $ bin/rails app:update
conflict config/application.rb
Overwrite /myapp/config/application.rb? (enter "h" for help) [Ynaqdh]
force config/application.rb
- create config/initializers/new_framework_defaults_7_0.rb
+ create config/initializers/new_framework_defaults_7_2.rb
...
```
@@ -75,6 +75,11 @@ The new Rails version might have different configuration defaults than the previ
To allow you to upgrade to new defaults one by one, the update task has created a file `config/initializers/new_framework_defaults_X.Y.rb` (with the desired Rails version in the filename). You should enable the new configuration defaults by uncommenting them in the file; this can be done gradually over several deployments. Once your application is ready to run with new defaults, you can remove this file and flip the `config.load_defaults` value.
+Upgrading from Rails 7.1 to Rails 7.2
+-------------------------------------
+
+For more information on changes made to Rails 7.2 please see the [release notes](7_2_release_notes.html).
+
Upgrading from Rails 7.0 to Rails 7.1
-------------------------------------
diff --git a/railties/CHANGELOG.md b/railties/CHANGELOG.md
index f84b350f850..51387a52b16 100644
--- a/railties/CHANGELOG.md
+++ b/railties/CHANGELOG.md
@@ -1,816 +1,2 @@
-## Rails 7.1.0.rc1 (September 27, 2023) ##
-* Require `concurrent-ruby` in `config/puma.rb` so that Puma can boot in
- production when `WEB_CONCURRENCY` is not explicitly specified.
-
- Fixes #49323.
-
- *Matt Brictson*
-
-* Raise error when generating attribute with dangerous name.
-
- The following will now raise an error as `save` and `hash` are already
- defined by Active Record.
-
- ```bash
- $ bin/rails generate model Post save
- $ bin/rails generate model Post hash
- ```
-
- *Petrik de Heus*
-
-
-## Rails 7.1.0.beta1 (September 13, 2023) ##
-
-* Add ability to show slow tests to the test runner
-
- ```bash
- $ bin/test --profile # additionally prints 10 (default) slowest tests
- # or
- $ bin/test --profile 20 # prints 20 slowest tests
- ```
-
- *fatkodima*
-
-* `rails new --javascript` generator now supports Bun
-
- ```bash
- $ rails new my_new_app --javascript=bun
- ```
-
- *Jason Meller*
-
-* bin/setup uses `bun` instead of `yarn` when generated an app with bun
-
- Use `bun install` on `bin/setup` when using `bun`.
-
- *Cadu Ribeiro*
-
-* `config/application.rb` now includes
-
- ```ruby
- config.autoload_lib(ignore: %w(assets tasks))
- ```
-
- In practice, this means that new 7.1 applications autoload from `lib` out of the box.
-
- *Xavier Noria*
-
-* Add an option to start rails console in sandbox mode by default
-
- `sandbox_by_default` option is added to start rails console in sandbox
- mode by default. With this option turned on, `--no-sandbox` must be
- specified to start rails in non-sandbox mode.
-
- Note that this option is ignored when rails environment is development
- or test.
-
- *Shouichi Kamiya*
-
-* Omit `webdrivers` gem dependency from `Gemfile` template
-
- *Sean Doyle*
-
-* Support filtering tests by line ranges
-
- The new syntax allows you to filter tests by line ranges. For example, the
- following command runs tests from line 10 to 20.
-
- ```bash
- $ rails test test/models/user_test.rb:10-20
- ```
-
- *Shouichi Kamiya*, *Seonggi Yang*, *oljfte*, *Ryohei UEDA*
-
-* Update default scaffold templates to set 303 (See Other) as status code
- on redirect for the update action for XHR requests other than GET or POST
- to avoid issues (e.g browsers trying to follow the redirect using the
- original request method resulting in double PATCH/PUT)
-
- *Guillermo Iguaran*
-
-* The new `config.autoload_lib_once` is similar to `config.autoload_lib`,
- except that it adds `lib` to `config.autoload_once_paths` instead.
-
- By calling `config.autoload_lib_once`, classes and modules in `lib` can be
- autoloaded, even from application initializers, but won't be reloaded.
-
- Please, see further details in the [autoloading
- guide](https://guides.rubyonrails.org/v7.1/autoloading_and_reloading_constants.html).
-
- *Xavier Noria*
-
-* Add `config.action_dispatch.debug_exception_log_level` to configure the log
- level used by `ActionDispatch::DebugExceptions`.
-
- The default is `:fatal`, but with `load_defaults "7.1"` the default will be
- `:error`.
-
- *Hartley McGuire*
-
-* Add `DATABASE` option to `railties:install:migrations`
-
- This allows you to specify which database the migrations should be copied to
- when running `rails railties:install:migrations`.
-
- ```bash
- $ rails railties:install:migrations DATABASE=animals
- ```
-
- *Matthew Hirst*
-
-* The new method `config.autoload_lib(ignore:)` provides a simple way to
- autoload from `lib`:
-
- ```ruby
- # config/application.rb
- config.autoload_lib(ignore: %w(assets tasks))
- ```
-
- Please, see further details in the [autoloading
- guide](https://guides.rubyonrails.org/v7.1/autoloading_and_reloading_constants.html).
-
- *Xavier Noria*
-
-* Don't show secret_key_base for `Rails.application.config#inspect`.
-
- Before:
-
- ```ruby
- Rails.application.config.inspect
- "#"
- ```
-
- After:
-
- ```ruby
- Rails.application.config.inspect
- "#"
- ```
-
- *Petrik de Heus*
-
-* Deprecate calling `Rails.application.secrets`.
-
- Rails `secrets` have been deprecated in favor of `credentials`.
- Calling `Rails.application.secrets` should show a deprecation warning.
-
- *Petrik de Heus*
-
-* Store `secret_key_base` in `Rails.config` for local environments.
-
- Rails `secrets` have been deprecated in favor of `credentials`.
- For the local environments the `secret_key_base` is now stored in
- `Rails.config.secret_key_base` instead of the soft deprecated
- `Rails.application.secrets.secret_key_base`.
-
- *Petrik de Heus*
-
-* Enable force_ssl=true in production by default: Force all access to the app over SSL,
- use Strict-Transport-Security, and use secure cookies
-
- *Justin Searls*, *Aaron Patterson*, *Guillermo Iguaran*, *Vinícius Bispo*
-
-* Add engine's draw paths to application route set, so that the application
- can draw route files defined in engine paths.
-
- *Gannon McGibbon*
-
-* Support `VISUAL` environment variable for commands which open an editor,
- and prefer it over `EDITOR`.
-
- *Summer ☀️*
-
-* Add engine's `test/fixtures` path to `fixture_paths` in `on_load` hook if
- path exists and is under the Rails application root.
-
- *Chris Salzberg*
-
-* `bin/rails app:template` now runs `bundle install` and any `after_bundle`
- blocks after the template is executed.
-
- *Jonathan Hefner* and *Gerry Caulfield*
-
-* Enable passing column size to migration generator
-
- Previously you could pass a limit to the migration generator:
-
- `rails generate migration CreateAuthor name:text{65535}`
-
- Now, a size attribute can be passed to the migration generator:
-
- `rails generate migration CreateAuthor name:text{medium}`
-
- This generates a migration which includes the size attribute:
-
- ```ruby
- class CreateAuthor < ActiveRecord::Migration[7.1]
- def change
- create_table :authors do |t|
- t.text :name, size: :medium
- end
- end
- end
- ```
-
- *Josh Broughton*, *Hartley McGuire*
-
-* Trying to set a config key with the same name of a method now raises:
-
- ```ruby
- config.load_defaults = 7.0
- # NoMethodError: Cannot assign to `load_defaults`, it is a configuration method
- ```
-
- *Xavier Noria*
-
-* Deprecate `secrets:edit/show` and remove `secrets:setup`
-
- `bin/rails secrets:setup` has been deprecated since Rails 5.2 in favor of
- credentials. This command has been removed.
-
- `bin/rails secrets:show` and `bin/rails secrets:edit` have been deprecated
- in favor of credentials.
-
- Run `bin/rails credentials:help` for more information
-
- *Petrik de Heus*
-
-* `bin/rails --help` will now list only framework and plugin commands. Rake
- tasks defined in `lib/tasks/*.rake` files will no longer be included. For a
- list of those tasks, use `rake -T`.
-
- *Jonathan Hefner*
-
-* Allow calling `bin/rails restart` outside of app directory.
-
- The following would previously fail with a "No Rakefile found" error.
-
- ```bash
- $ blog/bin/rails restart
- ```
-
- *Petrik de Heus*
-
-* Support prerelease rubies in Gemfile template if RubyGems version is 3.3.13 or higher.
-
- *Yasuo Honda*, *David Rodríguez*
-
-* Autoloading setup honors root directories manually set by the user.
-
- This is relevant for custom namespaces. For example, if you'd like classes
- and modules under `app/services` to be defined in the `Services` namespace
- without an extra `app/services/services` directory, this is now enough:
-
- ```ruby
- # config/initializers/autoloading.rb
-
- # The namespace has to exist.
- #
- # In this example we define the module on the spot. Could also be created
- # elsewhere and its definition loaded here with an ordinary `require`. In
- # any case, `push_dir` expects a class or module object.
- module Services; end
-
- Rails.autoloaders.main.push_dir("#{Rails.root}/app/services", namespace: Services)
- ```
-
- Check the autoloading guide for further details.
-
- *Xavier Noria*
-
-* Railties now requires the irb gem as a dependency, which means when you install Rails, irb will also
- be installed as a gem. Rails will then use the installed version of irb for its console instead of
- relying on Ruby's built-in version.
- This ensures that Rails has access to the most up-to-date and reliable version of irb for its console.
-
- *Stan Lo*
-
-* Use infinitive form for all rails command descriptions verbs.
-
- *Petrik de Heus*
-
-* Credentials commands (e.g. `bin/rails credentials:edit`) now respect
- `config.credentials.content_path` and `config.credentials.key_path` when set
- in `config/application.rb` or `config/environments/#{Rails.env}.rb`.
-
- Before:
-
- * `bin/rails credentials:edit` ignored `RAILS_ENV`, and would always edit
- `config/credentials.yml.enc`.
-
- * `bin/rails credentials:edit --environment foo` would create and edit
- `config/credentials/foo.yml.enc`.
-
- * If `config.credentials.content_path` or `config.credentials.key_path`
- was set, `bin/rails credentials:edit` could not be used to edit the
- credentials. Editing credentials required using `bin/rails
- encrypted:edit path/to/credentials --key path/to/key`.
-
- After:
-
- * `bin/rails credentials:edit` will edit the credentials file that the app
- would load for the current `RAILS_ENV`.
-
- * `bin/rails credentials:edit` respects `config.credentials.content_path`
- and `config.credentials.key_path` when set in `config/application.rb`
- or `config/environments/#{Rails.env}.rb`.
-
- * `bin/rails credentials:edit --environment foo` will create and edit
- `config/credentials/foo.yml.enc` _if_ `config.credentials.content_path`
- has not been set for the `foo` environment. Ultimately, it will edit
- the credentials file that the app would load for the `foo` environment.
-
- *Jonathan Hefner*
-
-* Add descriptions for non-Rake commands when running `rails -h`.
-
- *Petrik de Heus*
-
-* Show relevant commands when calling help
-
- When running `rails -h` or just `rails` outside a Rails application,
- Rails outputs all options for running the `rails new` command. This can be
- confusing to users when they probably want to see the common Rails commands.
-
- Instead, we should always show the common commands when running `rails -h`
- inside or outside a Rails application.
-
- As the relevant commands inside a Rails application differ from the
- commands outside an application, the help USAGE file has been split to
- show the most relevant commands for the context.
-
- *Petrik de Heus*
-
-* Add Rails::HealthController#show and map it to /up for newly generated applications.
- Load balancers and uptime monitors all need a basic endpoint to tell whether the app is up.
- This is a good starting point that'll work in many situations.
-
- *DHH*
-
-* Only use HostAuthorization middleware if `config.hosts` is not empty
-
- *Hartley McGuire*
-
-* Raise an exception when a `before_action`'s "only" or "except" filter
- options reference an action that doesn't exist. This will be enabled by
- default but can be overridden via config.
-
- ```ruby
- # config/environments/production.rb
- config.action_controller.raise_on_missing_callback_actions = false
- ```
-
- *Jess Bees*
-
-* Use physical processor count as the default Puma worker count in production.
- This can be overridden by setting `ENV["WEB_CONCURRENCY"]` or editing the
- generated "config/puma.rb" directly.
-
- *DHH*
-
-* Add Docker files by default to new apps: Dockerfile, .dockerignore, bin/docker-entrypoint.
- These files can be skipped with `--skip-docker`. They're intended as a starting point for
- a production deploy of the application. Not intended for development (see Docked Rails for that).
-
- Example:
-
- ```bash
- $ docker build -t app .
- $ docker volume create app-storage
- $ docker run --rm -it -v app-storage:/rails/storage -p 3000:3000 --env RAILS_MASTER_KEY= app
- ```
-
- You can also start a console or a runner from this image:
-
- ```bash
- $ docker run --rm -it -v app-storage:/rails/storage --env RAILS_MASTER_KEY= app console
- ```
-
- To create a multi-platform image on Apple Silicon to deploy on AMD or Intel and push to Docker Hub for user/app:
-
- ```bash
- $ docker login -u
- $ docker buildx create --use
- $ docker buildx build --push --platform=linux/amd64,linux/arm64 -t .
- ```
-
- *DHH, Sam Ruby*
-
-* Add ENV["SECRET_KEY_BASE_DUMMY"] for starting production environment with a generated secret base key,
- which can be used to run tasks like `assets:precompile` without making the RAILS_MASTER_KEY available
- to the build process.
-
- Dockerfile layer example:
-
- ```
- RUN SECRET_KEY_BASE_DUMMY=1 bundle exec rails assets:precompile
- ```
-
- *DHH*
-
-* Show descriptions for all commands in Rails help
-
- When calling `rails help` most commands missed their description. We now
- show the same descriptions as shown in `rails -T`.
-
- *Petrik de Heus*
-
-* Always generate the storage/ directory with rails new to ensure there's a stable place to
- put permanent files, and a single mount point for containers to map. Then default sqlite3 databases
- to live there instead of db/, which is only meant for configuration, not data.
-
- *DHH*
-
-* Rails console now disables `IRB`'s autocompletion feature in production by default.
-
- Setting `IRB_USE_AUTOCOMPLETE=true` can override this default.
-
- *Stan Lo*
-
-* Add `config.precompile_filter_parameters`, which enables precompilation of
- `config.filter_parameters` using `ActiveSupport::ParameterFilter.precompile_filters`.
- Precompilation can improve filtering performance, depending on the quantity
- and types of filters.
-
- `config.precompile_filter_parameters` defaults to `true` for
- `config.load_defaults 7.1` and above.
-
- *Jonathan Hefner*
-
-* Add `after_routes_loaded` hook to `Rails::Railtie::Configuration` for
- engines to add a hook to be called after application routes have been
- loaded.
-
- ```ruby
- MyEngine.config.after_routes_loaded do
- # code that must happen after routes have been loaded
- end
- ```
-
- *Chris Salzberg*
-
-* Send 303 See Other status code back for the destroy action on newly generated
- scaffold controllers.
-
- *Tony Drake*
-
-* Add `Rails.application.deprecators` as a central point to manage deprecators
- for an application.
-
- Individual deprecators can be added and retrieved from the collection:
-
- ```ruby
- Rails.application.deprecators[:my_gem] = ActiveSupport::Deprecation.new("2.0", "MyGem")
- Rails.application.deprecators[:other_gem] = ActiveSupport::Deprecation.new("3.0", "OtherGem")
- ```
-
- And the collection's configuration methods affect all deprecators in the
- collection:
-
- ```ruby
- Rails.application.deprecators.debug = true
-
- Rails.application.deprecators[:my_gem].debug
- # => true
- Rails.application.deprecators[:other_gem].debug
- # => true
- ```
-
- Additionally, all deprecators in the collection can be silenced for the
- duration of a given block:
-
- ```ruby
- Rails.application.deprecators.silence do
- Rails.application.deprecators[:my_gem].warn # => silenced (no warning)
- Rails.application.deprecators[:other_gem].warn # => silenced (no warning)
- end
- ```
-
- *Jonathan Hefner*
-
-* Move dbconsole logic to Active Record connection adapter.
-
- Instead of hosting the connection logic in the command object, the
- database adapter should be responsible for connecting to a console session.
- This patch moves #find_cmd_and_exec to the adapter and exposes a new API to
- lookup the adapter class without instantiating it.
-
- *Gannon McGibbon*, *Paarth Madan*
-
-* Add `Rails.application.message_verifiers` as a central point to configure
- and create message verifiers for an application.
-
- This allows applications to, for example, rotate old `secret_key_base`
- values:
-
- ```ruby
- config.before_initialize do |app|
- app.message_verifiers.rotate(secret_key_base: "old secret_key_base")
- end
- ```
-
- And for libraries to create preconfigured message verifiers:
-
- ```ruby
- ActiveStorage.verifier = Rails.application.message_verifiers["ActiveStorage"]
- ```
-
- *Jonathan Hefner*
-
-* Support MySQL's ssl-mode option for the dbconsole command.
-
- Verifying the identity of the database server requires setting the ssl-mode
- option to VERIFY_CA or VERIFY_IDENTITY. This option was previously ignored
- for the dbconsole command.
-
- *Petrik de Heus*
-
-* Delegate application record generator description to orm hooked generator.
-
- *Gannon McGibbon*
-
-* Show BCC recipients when present in Action Mailer previews.
-
- *Akshay Birajdar*
-
-* Extend `routes --grep` to also filter routes by matching against path.
-
- Example:
-
- ```bash
- $ bin/rails routes --grep /cats/1
- Prefix Verb URI Pattern Controller#Action
- cat GET /cats/:id(.:format) cats#show
- PATCH /cats/:id(.:format) cats#update
- PUT /cats/:id(.:format) cats#update
- DELETE /cats/:id(.:format) cats#destroy
- ```
-
- *Orhan Toy*
-
-* Improve `rails runner` output when given a file path that doesn't exist.
-
- *Tekin Suleyman*
-
-* `config.allow_concurrency = false` now use a `Monitor` instead of a `Mutex`
-
- This allows to enable `config.active_support.executor_around_test_case` even
- when `config.allow_concurrency` is disabled.
-
- *Jean Boussier*
-
-* Add `routes --unused` option to detect extraneous routes.
-
- Example:
-
- ```bash
- $ bin/rails routes --unused
-
- Found 2 unused routes:
-
- Prefix Verb URI Pattern Controller#Action
- one GET /one(.:format) action#one
- two GET /two(.:format) action#two
- ```
-
- *Gannon McGibbon*
-
-* Add `--parent` option to controller generator to specify parent class of job.
-
- Example:
-
- `bin/rails g controller admin/users --parent=admin_controller` generates:
-
- ```ruby
- class Admin::UsersController < AdminController
- # ...
- end
- ```
-
- *Gannon McGibbon*
-
-* In-app custom credentials templates are now supported. When a credentials
- file does not exist, `rails credentials:edit` will now try to use
- `lib/templates/rails/credentials/credentials.yml.tt` to generate the
- credentials file, before falling back to the default template.
-
- This allows e.g. an open-source Rails app (which would not include encrypted
- credentials files in its repo) to include a credentials template, so that
- users who install the app will get a custom pre-filled credentials file when
- they run `rails credentials:edit`.
-
- *Jonathan Hefner*
-
-* Except for `dev` and `test` environments, newly generated per-environment
- credentials files (e.g. `config/credentials/production.yml.enc`) now include
- a `secret_key_base` for convenience, just as `config/credentials.yml.enc`
- does.
-
- *Jonathan Hefner*
-
-* `--no-*` options now work with the app generator's `--minimal` option, and
- are both comprehensive and precise. For example:
-
- ```bash
- $ rails new my_cool_app --minimal
- Based on the specified options, the following options will also be activated:
-
- --skip-active-job [due to --minimal]
- --skip-action-mailer [due to --skip-active-job, --minimal]
- --skip-active-storage [due to --skip-active-job, --minimal]
- --skip-action-mailbox [due to --skip-active-storage, --minimal]
- --skip-action-text [due to --skip-active-storage, --minimal]
- --skip-javascript [due to --minimal]
- --skip-hotwire [due to --skip-javascript, --minimal]
- --skip-action-cable [due to --minimal]
- --skip-bootsnap [due to --minimal]
- --skip-dev-gems [due to --minimal]
- --skip-system-test [due to --minimal]
-
- ...
-
- $ rails new my_cool_app --minimal --no-skip-active-storage
- Based on the specified options, the following options will also be activated:
-
- --skip-action-mailer [due to --minimal]
- --skip-action-mailbox [due to --minimal]
- --skip-action-text [due to --minimal]
- --skip-javascript [due to --minimal]
- --skip-hotwire [due to --skip-javascript, --minimal]
- --skip-action-cable [due to --minimal]
- --skip-bootsnap [due to --minimal]
- --skip-dev-gems [due to --minimal]
- --skip-system-test [due to --minimal]
-
- ...
- ```
-
- *Brad Trick* and *Jonathan Hefner*
-
-* Add `--skip-dev-gems` option to app generator to skip adding development
- gems (like `web-console`) to the Gemfile.
-
- *Brad Trick*
-
-* Skip Active Storage and Action Mailer if Active Job is skipped.
-
- *Étienne Barrié*
-
-* Correctly check if frameworks are disabled when running app:update.
-
- *Étienne Barrié* and *Paulo Barros*
-
-* Delegate model generator description to orm hooked generator.
-
- *Gannon McGibbon*
-
-* Execute `rails runner` scripts inside the executor.
-
- Enables error reporting, query cache, etc.
-
- *Jean Boussier*
-
-* Avoid booting in development then test for test tasks.
-
- Running one of the rails test subtasks (e.g. test:system, test:models) would
- go through Rake and cause the app to be booted twice. Now all the test:*
- subtasks are defined as Thor tasks and directly load the test environment.
-
- *Étienne Barrié*
-
-* Deprecate `Rails::Generators::Testing::Behaviour` in favor of `Rails::Generators::Testing::Behavior`.
-
- *Gannon McGibbon*
-
-* Allow configuration of logger size for local and test environments
-
- `config.log_file_size`
-
- Defaults to `100` megabytes.
-
- *Bernie Chiu*
-
-* Enroll new apps in decrypted diffs of credentials by default. This behavior
- can be opted out of with the app generator's `--skip-decrypted-diffs` flag.
-
- *Jonathan Hefner*
-
-* Support declarative-style test name filters with `bin/rails test`.
-
- This makes it possible to run a declarative-style test such as:
-
- ```ruby
- class MyTest < ActiveSupport::TestCase
- test "does something" do
- # ...
- end
- end
- ```
-
- Using its declared name:
-
- ```bash
- $ bin/rails test test/my_test.rb -n "does something"
- ```
-
- Instead of having to specify its expanded method name:
-
- ```bash
- $ bin/rails test test/my_test.rb -n test_does_something
- ```
-
- *Jonathan Hefner*
-
-* Add `--js` and `--skip-javascript` options to `rails new`
-
- `--js` alias to `rails new --javascript ...`
-
- Same as `-j`, e.g. `rails new --js esbuild ...`
-
- `--skip-js` alias to `rails new --skip-javascript ...`
-
- Same as `-J`, e.g. `rails new --skip-js ...`
-
- *Dorian Marié*
-
-* Allow relative paths with leading dot slash to be passed to `rails test`.
-
- Fix `rails test ./test/model/post_test.rb` to run a single test file.
-
- *Shouichi Kamiya* and *oljfte*
-
-* Deprecate `config.enable_dependency_loading`. This flag addressed a limitation of the `classic` autoloader and has no effect nowadays. To fix this deprecation, please just delete the reference.
-
- *Xavier Noria*
-
-* Define `config.enable_reloading` to be `!config.cache_classes` for a more intuitive name. While `config.enable_reloading` and `config.reloading_enabled?` are preferred from now on, `config.cache_classes` is supported for backwards compatibility.
-
- *Xavier Noria*
-
-* Add JavaScript dependencies installation on bin/setup
-
- Add `yarn install` to bin/setup when using esbuild, webpack, or rollout.
-
- *Carlos Ribeiro*
-
-* Use `controller_class_path` in `Rails::Generators::NamedBase#route_url`
-
- The `route_url` method now returns the correct path when generating
- a namespaced controller with a top-level model using `--model-name`.
-
- Previously, when running this command:
-
- ```bash
- $ bin/rails generate scaffold_controller Admin/Post --model-name Post
- ```
-
- the comments above the controller action would look like:
-
- ``` ruby
- # GET /posts
- def index
- @posts = Post.all
- end
- ```
-
- afterwards, they now look like this:
-
- ``` ruby
- # GET /admin/posts
- def index
- @posts = Post.all
- end
- ```
-
- Fixes #44662.
-
- *Andrew White*
-
-* No longer add autoloaded paths to `$LOAD_PATH`.
-
- This means it won't be possible to load them with a manual `require` call, the class or module can be referenced instead.
-
- Reducing the size of `$LOAD_PATH` speed-up `require` calls for apps not using `bootsnap`, and reduce the
- size of the `bootsnap` cache for the others.
-
- *Jean Boussier*
-
-* Remove default `X-Download-Options` header
-
- This header is currently only used by Internet Explorer which
- will be discontinued in 2022 and since Rails 7 does not fully
- support Internet Explorer this header should not be a default one.
-
- *Harun Sabljaković*
-
-* Add .node-version files for Rails apps that use Node.js
-
- Node version managers that make use of this file:
- https://github.com/shadowspawn/node-version-usage#node-version-file-usage
-
- The generated Dockerfile will use the same node version.
-
- *Sam Ruby*
-
-Please check [7-0-stable](https://github.com/rails/rails/blob/7-0-stable/railties/CHANGELOG.md) for previous changes.
+Please check [7-1-stable](https://github.com/rails/rails/blob/7-1-stable/railties/CHANGELOG.md) for previous changes.
diff --git a/railties/lib/rails/application/configuration.rb b/railties/lib/rails/application/configuration.rb
index 0db049117ac..beef8821f04 100644
--- a/railties/lib/rails/application/configuration.rb
+++ b/railties/lib/rails/application/configuration.rb
@@ -329,6 +329,8 @@ module Rails
action_text.sanitizer_vendor = Rails::HTML::Sanitizer.best_supported_vendor
end
end
+ when "7.2"
+ load_defaults "7.1"
else
raise "Unknown version #{target_version.to_s.inspect}"
end
diff --git a/railties/lib/rails/gem_version.rb b/railties/lib/rails/gem_version.rb
index e640dcd35b4..61a891d6b92 100644
--- a/railties/lib/rails/gem_version.rb
+++ b/railties/lib/rails/gem_version.rb
@@ -8,9 +8,9 @@ module Rails
module VERSION
MAJOR = 7
- MINOR = 1
+ MINOR = 2
TINY = 0
- PRE = "rc1"
+ PRE = "alpha"
STRING = [MAJOR, MINOR, TINY, PRE].compact.join(".")
end
diff --git a/railties/lib/rails/generators/rails/app/templates/config/initializers/new_framework_defaults_7_1.rb.tt b/railties/lib/rails/generators/rails/app/templates/config/initializers/new_framework_defaults_7_1.rb.tt
deleted file mode 100644
index d41af162ad3..00000000000
--- a/railties/lib/rails/generators/rails/app/templates/config/initializers/new_framework_defaults_7_1.rb.tt
+++ /dev/null
@@ -1,223 +0,0 @@
-# Be sure to restart your server when you modify this file.
-#
-# This file eases your Rails 7.1 framework defaults upgrade.
-#
-# Uncomment each configuration one by one to switch to the new default.
-# Once your application is ready to run with all new defaults, you can remove
-# this file and set the `config.load_defaults` to `7.1`.
-#
-# Read the Guide for Upgrading Ruby on Rails for more info on each option.
-# https://guides.rubyonrails.org/upgrading_ruby_on_rails.html
-
-# No longer add autoloaded paths into `$LOAD_PATH`. This means that you won't be able
-# to manually require files that are managed by the autoloader, which you shouldn't do anyway.
-# This will reduce the size of the load path, making `require` faster if you don't use bootsnap, or reduce the size
-# of the bootsnap cache if you use it.
-# Rails.application.config.add_autoload_paths_to_load_path = false
-
-# Remove the default X-Download-Options headers since it is used only by Internet Explorer.
-# If you need to support Internet Explorer, add back `"X-Download-Options" => "noopen"`.
-# Rails.application.config.action_dispatch.default_headers = {
-# "X-Frame-Options" => "SAMEORIGIN",
-# "X-XSS-Protection" => "0",
-# "X-Content-Type-Options" => "nosniff",
-# "X-Permitted-Cross-Domain-Policies" => "none",
-# "Referrer-Policy" => "strict-origin-when-cross-origin"
-# }
-
-# Do not treat an `ActionController::Parameters` instance
-# as equal to an equivalent `Hash` by default.
-# Rails.application.config.action_controller.allow_deprecated_parameters_hash_equality = false
-
-# Active Record Encryption now uses SHA-256 as its hash digest algorithm. Important: If you have
-# data encrypted with previous Rails versions, there are two scenarios to consider:
-#
-# 1. If you have +config.active_support.key_generator_hash_digest_class+ configured as SHA1 (the default
-# before Rails 7.0), you need to configure SHA-1 for Active Record Encryption too:
-# Rails.application.config.active_record.encryption.hash_digest_class = OpenSSL::Digest::SHA1
-# 2. If you have +config.active_support.key_generator_hash_digest_class+ configured as SHA256 (the new default
-# in 7.0), then you need to configure SHA-256 for Active Record Encryption:
-# Rails.application.config.active_record.encryption.hash_digest_class = OpenSSL::Digest::SHA256
-#
-# If you don't currently have data encrypted with Active Record encryption, you can disable this setting to
-# configure the default behavior starting 7.1+:
-# Rails.application.config.active_record.encryption.support_sha1_for_non_deterministic_encryption = false
-
-# No longer run after_commit callbacks on the first of multiple Active Record
-# instances to save changes to the same database row within a transaction.
-# Instead, run these callbacks on the instance most likely to have internal
-# state which matches what was committed to the database, typically the last
-# instance to save.
-# Rails.application.config.active_record.run_commit_callbacks_on_first_saved_instances_in_transaction = false
-
-# Configures SQLite with a strict strings mode, which disables double-quoted string literals.
-#
-# SQLite has some quirks around double-quoted string literals.
-# It first tries to consider double-quoted strings as identifier names, but if they don't exist
-# it then considers them as string literals. Because of this, typos can silently go unnoticed.
-# For example, it is possible to create an index for a non existing column.
-# See https://www.sqlite.org/quirks.html#double_quoted_string_literals_are_accepted for more details.
-# Rails.application.config.active_record.sqlite3_adapter_strict_strings_by_default = true
-
-# Disable deprecated singular associations names
-# Rails.application.config.active_record.allow_deprecated_singular_associations_name = false
-
-# Enable the Active Job `BigDecimal` argument serializer, which guarantees
-# roundtripping. Without this serializer, some queue adapters may serialize
-# `BigDecimal` arguments as simple (non-roundtrippable) strings.
-#
-# When deploying an application with multiple replicas, old (pre-Rails 7.1)
-# replicas will not be able to deserialize `BigDecimal` arguments from this
-# serializer. Therefore, this setting should only be enabled after all replicas
-# have been successfully upgraded to Rails 7.1.
-# Rails.application.config.active_job.use_big_decimal_serializer = true
-
-# Specify if an `ArgumentError` should be raised if `Rails.cache` `fetch` or
-# `write` are given an invalid `expires_at` or `expires_in` time.
-# Options are `true`, and `false`. If `false`, the exception will be reported
-# as `handled` and logged instead.
-# Rails.application.config.active_support.raise_on_invalid_cache_expiration_time = true
-
-# Specify whether Query Logs will format tags using the SQLCommenter format
-# (https://open-telemetry.github.io/opentelemetry-sqlcommenter/), or using the legacy format.
-# Options are `:legacy` and `:sqlcommenter`.
-# Rails.application.config.active_record.query_log_tags_format = :sqlcommenter
-
-# Specify the default serializer used by `MessageEncryptor` and `MessageVerifier`
-# instances.
-#
-# The legacy default is `:marshal`, which is a potential vector for
-# deserialization attacks in cases where a message signing secret has been
-# leaked.
-#
-# In Rails 7.1, the new default is `:json_allow_marshal` which serializes and
-# deserializes with `ActiveSupport::JSON`, but can fall back to deserializing
-# with `Marshal` so that legacy messages can still be read.
-#
-# In Rails 7.2, the default will become `:json` which serializes and
-# deserializes with `ActiveSupport::JSON` only.
-#
-# Alternatively, you can choose `:message_pack` or `:message_pack_allow_marshal`,
-# which serialize with `ActiveSupport::MessagePack`. `ActiveSupport::MessagePack`
-# can roundtrip some Ruby types that are not supported by JSON, and may provide
-# improved performance, but it requires the `msgpack` gem.
-#
-# For more information, see
-# https://guides.rubyonrails.org/v7.1/configuring.html#config-active-support-message-serializer
-#
-# If you are performing a rolling deploy of a Rails 7.1 upgrade, wherein servers
-# that have not yet been upgraded must be able to read messages from upgraded
-# servers, first deploy without changing the serializer, then set the serializer
-# in a subsequent deploy.
-# Rails.application.config.active_support.message_serializer = :json_allow_marshal
-
-# Enable a performance optimization that serializes message data and metadata
-# together. This changes the message format, so messages serialized this way
-# cannot be read by older versions of Rails. However, messages that use the old
-# format can still be read, regardless of whether this optimization is enabled.
-#
-# To perform a rolling deploy of a Rails 7.1 upgrade, wherein servers that have
-# not yet been upgraded must be able to read messages from upgraded servers,
-# leave this optimization off on the first deploy, then enable it on a
-# subsequent deploy.
-# Rails.application.config.active_support.use_message_serializer_for_metadata = true
-
-# Set the maximum size for Rails log files.
-#
-# `config.load_defaults 7.1` does not set this value for environments other than
-# development and test.
-#
-# if Rails.env.local?
-# Rails.application.config.log_file_size = 100 * 1024 * 1024
-# end
-
-# Enable raising on assignment to attr_readonly attributes. The previous
-# behavior would allow assignment but silently not persist changes to the
-# database.
-# Rails.application.config.active_record.raise_on_assign_to_attr_readonly = true
-
-# Enable validating only parent-related columns for presence when the parent is mandatory.
-# The previous behavior was to validate the presence of the parent record, which performed an extra query
-# to get the parent every time the child record was updated, even when parent has not changed.
-# Rails.application.config.active_record.belongs_to_required_validates_foreign_key = false
-
-# Enable precompilation of `config.filter_parameters`. Precompilation can
-# improve filtering performance, depending on the quantity and types of filters.
-# Rails.application.config.precompile_filter_parameters = true
-
-# Enable before_committed! callbacks on all enrolled records in a transaction.
-# The previous behavior was to only run the callbacks on the first copy of a record
-# if there were multiple copies of the same record enrolled in the transaction.
-# Rails.application.config.active_record.before_committed_on_all_records = true
-
-# Disable automatic column serialization into YAML.
-# To keep the historic behavior, you can set it to `YAML`, however it is
-# recommended to explicitly define the serialization method for each column
-# rather than to rely on a global default.
-# Rails.application.config.active_record.default_column_serializer = nil
-
-# Enable a performance optimization that serializes Active Record models
-# in a faster and more compact way.
-#
-# To perform a rolling deploy of a Rails 7.1 upgrade, wherein servers that have
-# not yet been upgraded must be able to read caches from upgraded servers,
-# leave this optimization off on the first deploy, then enable it on a
-# subsequent deploy.
-# Rails.application.config.active_record.marshalling_format_version = 7.1
-
-# Run `after_commit` and `after_*_commit` callbacks in the order they are defined in a model.
-# This matches the behaviour of all other callbacks.
-# In previous versions of Rails, they ran in the inverse order.
-# Rails.application.config.active_record.run_after_transaction_callbacks_in_order_defined = true
-
-# Whether a `transaction` block is committed or rolled back when exited via `return`, `break` or `throw`.
-#
-# Rails.application.config.active_record.commit_transaction_on_non_local_return = true
-
-# Controls when to generate a value for has_secure_token declarations.
-#
-# Rails.application.config.active_record.generate_secure_token_on = :initialize
-
-# ** Please read carefully, this must be configured in config/application.rb **
-# Change the format of the cache entry.
-# Changing this default means that all new cache entries added to the cache
-# will have a different format that is not supported by Rails 7.0
-# applications.
-# Only change this value after your application is fully deployed to Rails 7.1
-# and you have no plans to rollback.
-# When you're ready to change format, add this to `config/application.rb` (NOT
-# this file):
-# config.active_support.cache_format_version = 7.1
-
-# Configure Action View to use HTML5 standards-compliant sanitizers when they are supported on your
-# platform.
-#
-# `Rails::HTML::Sanitizer.best_supported_vendor` will cause Action View to use HTML5-compliant
-# sanitizers if they are supported, else fall back to HTML4 sanitizers.
-#
-# In previous versions of Rails, Action View always used `Rails::HTML4::Sanitizer` as its vendor.
-#
-# Rails.application.config.action_view.sanitizer_vendor = Rails::HTML::Sanitizer.best_supported_vendor
-
-# Configure Action Text to use an HTML5 standards-compliant sanitizer when it is supported on your
-# platform.
-#
-# `Rails::HTML::Sanitizer.best_supported_vendor` will cause Action Text to use HTML5-compliant
-# sanitizers if they are supported, else fall back to HTML4 sanitizers.
-#
-# In previous versions of Rails, Action Text always used `Rails::HTML4::Sanitizer` as its vendor.
-#
-# Rails.application.config.action_text.sanitizer_vendor = Rails::HTML::Sanitizer.best_supported_vendor
-
-# Configure the log level used by the DebugExceptions middleware when logging
-# uncaught exceptions during requests
-# Rails.application.config.action_dispatch.debug_exception_log_level = :error
-
-# Configure the test helpers in Action View, Action Dispatch, and rails-dom-testing to use HTML5
-# parsers.
-#
-# Nokogiri::HTML5 isn't supported on JRuby, so JRuby applications must set this to :html4.
-#
-# In previous versions of Rails, these test helpers always used an HTML4 parser.
-#
-# Rails.application.config.dom_testing_default_html_version = :html5
diff --git a/railties/lib/rails/generators/rails/app/templates/config/initializers/new_framework_defaults_7_2.rb.tt b/railties/lib/rails/generators/rails/app/templates/config/initializers/new_framework_defaults_7_2.rb.tt
new file mode 100644
index 00000000000..fcf2024ecf0
--- /dev/null
+++ b/railties/lib/rails/generators/rails/app/templates/config/initializers/new_framework_defaults_7_2.rb.tt
@@ -0,0 +1,10 @@
+# Be sure to restart your server when you modify this file.
+#
+# This file eases your Rails 7.2 framework defaults upgrade.
+#
+# Uncomment each configuration one by one to switch to the new default.
+# Once your application is ready to run with all new defaults, you can remove
+# this file and set the `config.load_defaults` to `7.2`.
+#
+# Read the Guide for Upgrading Ruby on Rails for more info on each option.
+# https://guides.rubyonrails.org/upgrading_ruby_on_rails.html
diff --git a/version.rb b/version.rb
index e640dcd35b4..61a891d6b92 100644
--- a/version.rb
+++ b/version.rb
@@ -8,9 +8,9 @@ module Rails
module VERSION
MAJOR = 7
- MINOR = 1
+ MINOR = 2
TINY = 0
- PRE = "rc1"
+ PRE = "alpha"
STRING = [MAJOR, MINOR, TINY, PRE].compact.join(".")
end
diff --git a/yarn.lock b/yarn.lock
index af5d112bbf6..4b16f80d62a 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -29,24 +29,31 @@
integrity sha512-KE/SxsDqNs3rrWwFHcRh15ZLVFrI0YoZtgAdIyIq9k5hUNmiWRXXThPomIxHuL20sLdgzbDFyvkUMna14bvtrw==
"@rails/actioncable@file:/workspaces/rails/actioncable":
- version "7.1.0-rc1"
+ version "7.2.0-alpha"
resolved "file:actioncable"
"@rails/actiontext@file:/workspaces/rails/actiontext":
- version "7.1.0-rc1"
+ version "7.2.0-alpha"
resolved "file:actiontext"
dependencies:
"@rails/activestorage" ">= 7.1.0-alpha"
webpack "^4.17.1"
-"@rails/activestorage@>= 7.1.0-alpha", "@rails/activestorage@file:/workspaces/rails/activestorage":
- version "7.1.0-rc1"
+"@rails/activestorage@>= 7.1.0-alpha":
+ version "7.1.0-beta1"
+ resolved "https://registry.npmjs.org/@rails/activestorage/-/activestorage-7.1.0-beta1.tgz"
+ integrity sha512-5qQ5/65tBOVeFMgGq8F+PhXKrmBLMAnVpyZAe8WsCW5DbINRD8l8ysA8+zBmwCIxBMqn+M9hZoQVjuMPr35bvQ==
+ dependencies:
+ spark-md5 "^3.0.1"
+
+"@rails/activestorage@file:/workspaces/rails/activestorage":
+ version "7.2.0-alpha"
resolved "file:activestorage"
dependencies:
spark-md5 "^3.0.1"
"@rails/ujs@file:/workspaces/rails/actionview":
- version "7.1.0-rc1"
+ version "7.2.0-alpha"
resolved "file:actionview"
"@rollup/plugin-commonjs@^19.0.1":
-