patches 3.7.0 → 4.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 895215b6ac8fa6eb09aea79add6efebcead371d5b50579d983b70eff79c58682
-  data.tar.gz: aa05b38f701c0c525364d16f0f22dc7fde9b33c2a34aac240751e78b02d1c3d6
+  metadata.gz: 4d3cb95acebf22bd69de36b12b559515c6c2cf39160bfb6a135af5677ef90ad8
+  data.tar.gz: db396ae1486ff61282a2b363dd3fc3dceb3bdad6247ba4bce5ae409ccef939d8
 SHA512:
-  metadata.gz: e454bd2d14b1cf02eca6fc4bd18d3732c83627032c0a6a2fb76dbf6c43d07da7ee6786f542c8f689290b75deedc48ea8fb1b8eeb0581363fd48e9719a3478e38
-  data.tar.gz: a286831eb61b05d4fbdee99989247671307d3881433e293eacda3afc533b262d0d82d1cb6e098a0c3f4153b01891bd0e4ecece47f235ed36d09715ebb81e3c64
+  metadata.gz: 672d33b4552fbdcd038949290361b9da0cbc346e300811ee423ee5bf95069d6399c90b6eab06600706377a5070bc6e6012ebea6c26f5bafea523d44d0daf7806
+  data.tar.gz: 47452cd282ccaa753399e74eecd97bc7407514de7f09cb22ac30e7a5d1d6e9c1b6786d43572408442d69b70378517cfbbd2b5482a73684a1e0ea6672a0e59a2c

data/CHANGELOG.md

@@ -6,7 +6,48 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
-## [3.7.0] - 2026-09-10
+## [4.0.0] - 2026-09-21
+
+Removes everything 3.7.0 deprecated. Nothing here is a surprise if you upgraded
+to 3.7.0 and cleared its warnings; see Upgrading from 3.x in README.md.
+
+### Breaking
+- Ruby 3.2 and Rails 7.2 are the minimum, enforced by `required_ruby_version`
+  and `railties`/`activerecord >= 7.2`. Every combination CI verifies is now at
+  or above the floors, which was not true before
+- `slack-notifier` is no longer a runtime dependency. `Patches::Notifier`
+  requires it inside a `begin`/`rescue`, so the `defined?(Slack)` guard it always
+  carried finally does something. Applications that set `config.use_slack` add
+  `gem 'slack-notifier'` themselves
+- The Capistrano integration is removed - `require 'patches/capistrano'` and its
+  `patches:run` task. Invoke `bundle exec rake patches:run` from your deployment
+  process instead; `docs/usage.md` shows where
+- The workers include `Sidekiq::Job` directly, so Sidekiq 6.3 or newer is
+  required when the integration is used. `Patches.sidekiq_job_module` and its
+  `Sidekiq::Worker` fallback are gone
+- The install migration declares `ActiveRecord::Migration[7.2]` rather than
+  `[5.0]`. A fresh `patches_patches` therefore gets `datetime(6)` timestamp
+  columns, matching what a modern Rails schema uses, where `[5.0]`
+  compatibility produced `datetime` without precision. Existing installs are
+  untouched - they ran their own copy of the file long ago
+- Rails is required rather than guarded for. `railties` and `activerecord` were
+  always hard dependencies and the gem ships an engine, so the `defined?(Rails)`
+  checks described a mode nobody used - one of them read `defined?(:Rails)`,
+  always truthy, unnoticed until 3.6.3. `lib/patches.rb` now requires `rails`,
+  because loading the engine without it fails
+
+### Removed
+- The deprecation warnings 3.7.0 added, now that what they announced has
+  happened. `Patches.deprecator` itself stays - applications were told to
+  configure it - and its horizon points at the next major
+
+### Changed
+- CI covers every combination the gemspec allows, 12 cells rather than a wider
+  range, plus a leg for each optional-integration state: Sidekiq 7.x and 8.x
+  with strict arguments on and off, Sidekiq absent, `slack-notifier` absent, and
+  neither installed - the last of which nothing covered before
+
+## [3.7.0] - 2026-09-17
 
 Declares dependencies the gem always relied on, and announces what 4.0 is
 expected to require. No public API changes and no version constraint moves, so

data/README.md

@@ -56,25 +56,22 @@ deployment and the Capistrano task.
 
 ## Compatibility
 
-This release changes no version constraint: the gemspec still requires only
-`railties >= 3.2` and sets no Ruby floor, so anything that installed 3.6.2
-installs 3.6.3. The table is what CI verifies, which is narrower than what the
-gem permits - older Ruby and Rails are untested here, not blocked.
-
-| | Rails 7.1 | Rails 7.2 | Rails 8.0 | Rails 8.1 |
-|---|---|---|---|---|
-| **Ruby 3.0** | ✅ | | | |
-| **Ruby 3.1** | ✅ | ✅ | | |
-| **Ruby 3.2** | ✅ | ✅ | ✅ | ✅ |
-| **Ruby 3.3** | ✅ | ✅ | ✅ | ✅ |
-| **Ruby 3.4** | | ✅ | ✅ | ✅ |
-| **Ruby 4.0** | | ✅ | ✅ | ✅ |
-
-A blank cell is a pairing Rails itself does not support. Ruby 2.7 and Rails
-6.1/7.0 are deliberately not exercised - they are well past upstream support -
-though the gem still installs and, as of this release, passes on them.
-
-Ruby 4.0 is newer than all of these Rails releases, so those cells record that
+| | Minimum |
+|---|---|
+| Ruby | 3.2 |
+| Rails | 7.2 |
+
+Every combination the gemspec allows is verified on each push and pull request -
+the floors and the matrix are the same set, which they were not before 4.0:
+
+| | Rails 7.2 | Rails 8.0 | Rails 8.1 |
+|---|---|---|---|
+| **Ruby 3.2** | ✅ | ✅ | ✅ |
+| **Ruby 3.3** | ✅ | ✅ | ✅ |
+| **Ruby 3.4** | ✅ | ✅ | ✅ |
+| **Ruby 4.0** | ✅ | ✅ | ✅ |
+
+Ruby 4.0 is newer than all three Rails releases, so those cells record that
 Patches is verified on it, not that Rails claims support for it.
 
 ### Sidekiq
@@ -83,17 +80,21 @@ Sidekiq is an **optional** integration, not a runtime dependency: Patches runs
 each patch inline when Sidekiq is absent. Set `config.use_sidekiq = true` to run
 them in the background - see [docs/usage.md](docs/usage.md).
 
-The workers resolve their mixin at load time via `Patches.sidekiq_job_module`,
-preferring `Sidekiq::Job` (the name Sidekiq has used since 6.3) and falling back
-to `Sidekiq::Worker`, so older Sidekiq keeps working. CI covers each state a
-consumer can be in:
+The workers include `Sidekiq::Job`, so Sidekiq 6.3 or newer is required when the
+integration is used - 6.2 and earlier predate that constant. CI covers each
+state a consumer can be in:
 
 | State | Covered by |
 |---|---|
 | Sidekiq not installed | A leg omitting the gem entirely, exercising the `defined?(Sidekiq)` guards |
 | Installed, strict arguments on | Sidekiq 7.x and 8.x at their default (`:raise`) |
 | Installed, strict arguments off | Sidekiq 7.x and 8.x with `Sidekiq.strict_args!(false)` |
-| Older Sidekiq | A 6.5 leg, plus a spec covering the `Sidekiq::Worker` fallback |
+
+### Slack
+
+Slack notifications are optional and Patches does not install
+`slack-notifier` - add `gem 'slack-notifier'` to your own Gemfile if you set
+`config.use_slack`. CI runs a leg without it to keep that path honest.
 
 ### Running one combination locally
 
@@ -146,26 +147,23 @@ combination again, and delete `test.db` when switching between them: the suite
 creates `patches_patches` only when it is missing, so a database left by an
 earlier run can mask ordering problems.
 
-## Deprecations
+## Upgrading from 3.x
 
-3.7.0 introduces no breaking changes. It announces what 4.0 is expected to
-require, so the upgrade is uneventful. Each warning names its replacement and
-goes through the gem's own deprecator, which a host application can silence or
-redirect:
+Everything 4.0 removes was deprecated in 3.7.0, so upgrade to that first and
+clear its warnings - `Patches.deprecator.behavior = :raise` in an initializer
+turns them into failures if you would rather find them that way.
 
-```ruby
-Patches.deprecator.behavior = :silence  # or :raise, :log, a lambda...
-```
-
-| Deprecated | Replacement |
+| Change | What to do |
 |---|---|
-| Relying on Patches to install `slack-notifier` | Add `gem 'slack-notifier'` to your Gemfile if you use `config.use_slack`. From 4.0 only applications that want it carry it |
-| `require 'patches/capistrano'` | Invoke `rake patches:run` from your deployment process. The Capistrano task is removed in 4.0 |
-| Sidekiq older than 6.3 | Any supported Sidekiq (7.x or 8.x). 4.0 is expected to include `Sidekiq::Job` directly instead of falling back to `Sidekiq::Worker` |
-| Ruby older than 3.2, Rails older than 7.2 | Ruby 3.2+ and Rails 7.2+. 4.0 is expected to raise the gemspec floors to these, which are higher than the range CI verifies today |
-
-Nothing is removed in this release, and the gemspec floors are unchanged, so
-anything that installed 3.6.x installs 3.7.0.
+| Ruby 3.2 and Rails 7.2 are now the minimum | Upgrade, or stay on 3.7.x |
+| `slack-notifier` is no longer a dependency | Add `gem 'slack-notifier'` to your Gemfile if you set `config.use_slack` |
+| The Capistrano task is gone | Invoke `bundle exec rake patches:run` from your deployment process |
+| The workers include `Sidekiq::Job` | Use Sidekiq 6.3 or newer - 7.x or 8.x are the supported lines |
+
+Nothing else changed: patch classes, `Patches::Base`, the generator, the rake
+tasks, the configuration and the `patches_patches` table are all as they were.
+`Patches.deprecator` remains, so an initializer that configures it keeps
+working.
 
 ## Development
 

data/db/migrate/201506011700_create_patch.rb

@@ -1,4 +1,4 @@
-class CreatePatch < ActiveRecord::Migration[5.0]
+class CreatePatch < ActiveRecord::Migration[7.2]
   def change
     create_table :patches_patches do |t|
       t.string :path, null: false

data/docs/usage.md

@@ -22,9 +22,8 @@ bundle exec rake db:migrate
 
 ## Configuration
 
-> **Note.** From 4.0 Patches will not depend on `slack-notifier`, so only
-> applications using Slack carry it. If you set `config.use_slack`, add
-> `gem 'slack-notifier'` to your Gemfile.
+> **Note.** Patches does not depend on `slack-notifier`. If you set
+> `config.use_slack`, add `gem 'slack-notifier'` to your own Gemfile.
 
 If you would like to run the patches asynchronously, or would like them to notify
 your Slack channel when they fail or succeed, you need to set up
@@ -117,26 +116,18 @@ bundle exec rake patches:run
 
 Patches will only ever run once, patches will run in order of creation date.
 
-### Capistrano
+### Running on deploy
 
-> **Deprecated.** `patches/capistrano` is removed in 4.0. Invoke
-> `rake patches:run` from your deployment process instead.
+Invoke the rake task from your deployment process, after the application code is
+in place:
 
-To run patches on deployment using Capistrano, edit your Capfile and add
-
-```ruby
-require 'patches/capistrano'
 ```
-
-And then in your deploy.rb
-
-```ruby
-after 'last_task_you_want_to_run' 'patches:run'
+bundle exec rake patches:run
 ```
 
-If you are using sidekiq and restarting the sidekiq process on the box
-as a part of the deploy process, please make sure that the patches run task runs
-after sidekiq restarts, otherwise there is no guarentee the tasks will run.
+If you use Sidekiq and restart it as part of the deploy, make sure the patches
+task runs after Sidekiq restarts - otherwise there is no guarantee the jobs will
+be picked up.
 
 ## File Download
 

data/lib/patches/config.rb

@@ -1,5 +1,3 @@
-require 'patches/deprecation'
-
 module Patches
   class Config
     class << self
@@ -32,18 +30,6 @@ module Patches
           @sidekiq_queue = 'default'
         end
 
-        # Warns only for applications that enable Slack, and only the first time
-        # - an initializer that reloads, or configures twice, should not repeat
-        # the notice.
-        def use_slack=(enabled)
-          if enabled && !@warned_about_slack_notifier
-            @warned_about_slack_notifier = true
-            Patches.warn_slack_notifier_dependency_removed_in_4_0
-          end
-
-          @use_slack = enabled
-        end
-
         def sidekiq_options
           @sidekiq_options ||= { retry: false, queue: sidekiq_queue }
         end

data/lib/patches/deprecation.rb

@@ -2,47 +2,11 @@ require 'active_support/deprecation'
 
 module Patches
   # A gem-owned deprecator rather than ActiveSupport::Deprecation's singleton,
-  # which Rails 7.1 deprecated and 8.0 removed. Host applications can silence or
-  # redirect it: Patches.deprecator.behavior = :silence.
+  # which Rails 7.1 deprecated and 8.0 removed. Nothing is deprecated in 4.0 -
+  # everything 3.7.0 announced has been removed - but this stays: applications
+  # were told to configure it to silence those warnings, so removing it would
+  # break their initializers. The horizon is the next major.
   def self.deprecator
-    @deprecator ||= ActiveSupport::Deprecation.new('4.0', 'patches')
-  end
-
-  # The floors 4.0 is expected to set. Deliberately higher than what CI verifies
-  # today - Ruby 3.0 and Rails 7.1 still pass - so consumers on those versions
-  # hear about it a release ahead rather than at upgrade time.
-  MINIMUM_RUBY_IN_4_0 = '3.2'.freeze
-  MINIMUM_RAILS_IN_4_0 = '7.2'.freeze
-
-  def self.warn_slack_notifier_dependency_removed_in_4_0
-    deprecator.warn(
-      'patches will stop depending on slack-notifier in 4.0, so that only ' \
-      "applications using Slack carry it. Add gem 'slack-notifier' to your " \
-      'Gemfile to keep notifications working.'
-    )
-  end
-
-  def self.warn_capistrano_support_removed_in_4_0
-    deprecator.warn(
-      'patches/capistrano is deprecated and will be removed in 4.0. Invoke ' \
-      '`rake patches:run` from your deployment process instead.'
-    )
-  end
-
-  def self.warn_about_versions_dropped_in_4_0
-    if Gem::Version.new(RUBY_VERSION) < Gem::Version.new(MINIMUM_RUBY_IN_4_0)
-      deprecator.warn(
-        "Ruby #{RUBY_VERSION} will not be supported by patches 4.0, which is " \
-        "expected to require Ruby >= #{MINIMUM_RUBY_IN_4_0}."
-      )
-    end
-
-    return unless defined?(::Rails::VERSION::STRING)
-    return if Gem::Version.new(::Rails::VERSION::STRING) >= Gem::Version.new(MINIMUM_RAILS_IN_4_0)
-
-    deprecator.warn(
-      "Rails #{::Rails::VERSION::STRING} will not be supported by patches 4.0, " \
-      "which is expected to require Rails >= #{MINIMUM_RAILS_IN_4_0}."
-    )
+    @deprecator ||= ActiveSupport::Deprecation.new('5.0', 'patches')
   end
 end

data/lib/patches/engine.rb

@@ -3,14 +3,5 @@ require 'rails/engine'
 module Patches
   class Engine < Rails::Engine
     isolate_namespace Patches
-
-    # After the application's own initializers, so that a host which sets
-    # Patches.deprecator.behavior in config/initializers can actually silence
-    # this. Warning at require time - which happens during Bundler.require,
-    # before any initializer - meant the documented mechanism could not work.
-    # It also means Rails::VERSION is always loaded by the time we look.
-    initializer 'patches.version_deprecations', after: :load_config_initializers do
-      Patches.warn_about_versions_dropped_in_4_0
-    end
   end
 end

data/lib/patches/notifier.rb

@@ -1,4 +1,12 @@
-require 'slack-notifier'
+# Optional: an application that sets config.use_slack adds slack-notifier to its
+# own Gemfile. Patches runs without it, and send_slack_message's `defined?(Slack)`
+# guard - which could never be false while this require was unconditional - now
+# does its job.
+begin
+  require 'slack-notifier'
+rescue LoadError
+  nil
+end
 
 class Patches::Notifier
   class << self
@@ -28,7 +36,7 @@ class Patches::Notifier
     end
 
     def environment_prefix
-      Rails.env.upcase if defined?(Rails)
+      Rails.env.upcase
     end
 
     def notification_suffix

data/lib/patches/tenant_worker.rb

@@ -1,8 +1,8 @@
 require 'active_support/core_ext/hash/keys'
-require 'patches/sidekiq_job'
+require 'sidekiq'
 
 class Patches::TenantWorker
-  include Patches.sidekiq_job_module
+  include Sidekiq::Job
   include Patches::TenantRunConcern
   include Patches::ApplicationVersionValidation
 

data/lib/patches/version.rb

@@ -1,6 +1,6 @@
 module Patches
-  MAJOR = 3
-  MINOR = 7
+  MAJOR = 4
+  MINOR = 0
   PATCH = 0
   VERSION = [MAJOR, MINOR, PATCH].compact.join(".").freeze
 end

data/lib/patches/worker.rb

@@ -1,8 +1,8 @@
 require 'active_support/core_ext/hash/keys'
-require 'patches/sidekiq_job'
+require 'sidekiq'
 
 class Patches::Worker
-  include Patches.sidekiq_job_module
+  include Sidekiq::Job
   include Patches::ApplicationVersionValidation
 
   sidekiq_options Patches::Config.configuration.sidekiq_options

data/lib/patches.rb

@@ -1,8 +1,15 @@
+# railties and activerecord are hard dependencies, and the engine, the install
+# migration and Patches.default_path all assume a Rails application. The gem
+# used to guard on `defined?(Rails)` as though Rails were optional; one of those
+# guards read `defined?(:Rails)`, which is always truthy, and went unnoticed for
+# years - nobody was running this outside Rails.
+require 'rails'
+
 require "patches/version"
 
 module Patches
   def self.default_path
-    Rails.root.join('db/patches/') if defined?(Rails)
+    Rails.root.join('db/patches/')
   end
 
   def self.class_name(path)
@@ -24,9 +31,8 @@ require "patches/base"
 require "patches/config"
 require "patches/tenant_run_concern"
 require "patches/application_version_validation"
-require "patches/sidekiq_job" if defined?(Sidekiq)
 require "patches/tenant_worker" if defined?(Sidekiq)
-require "patches/engine" if defined?(Rails)
+require "patches/engine"
 require "patches/patch"
 require "patches/pending"
 require "patches/runner"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: patches
 version: !ruby/object:Gem::Version
-  version: 3.7.0
+  version: 4.0.0
 platform: ruby
 authors:
 - ReadyTech
@@ -15,42 +15,28 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '3.2'
+        version: '7.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '3.2'
+        version: '7.2'
 - !ruby/object:Gem::Dependency
   name: activerecord
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '3.2'
+        version: '7.2'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '3.2'
-- !ruby/object:Gem::Dependency
-  name: slack-notifier
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
+        version: '7.2'
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -159,8 +145,6 @@ files:
 - lib/patches.rb
 - lib/patches/application_version_validation.rb
 - lib/patches/base.rb
-- lib/patches/capistrano.rb
-- lib/patches/capistrano/tasks.rake
 - lib/patches/config.rb
 - lib/patches/deprecation.rb
 - lib/patches/engine.rb
@@ -168,7 +152,6 @@ files:
 - lib/patches/patch.rb
 - lib/patches/pending.rb
 - lib/patches/runner.rb
-- lib/patches/sidekiq_job.rb
 - lib/patches/tenant_run_concern.rb
 - lib/patches/tenant_runner.rb
 - lib/patches/tenant_worker.rb
@@ -180,9 +163,9 @@ licenses:
 - MIT
 metadata:
   source_code_uri: https://github.com/rdytech/patches
-  changelog_uri: https://github.com/rdytech/patches/blob/v3.7.0/CHANGELOG.md
+  changelog_uri: https://github.com/rdytech/patches/blob/v4.0.0/CHANGELOG.md
   bug_tracker_uri: https://github.com/rdytech/patches/issues
-  documentation_uri: https://github.com/rdytech/patches/blob/v3.7.0/docs/usage.md
+  documentation_uri: https://github.com/rdytech/patches/blob/v4.0.0/docs/usage.md
 rdoc_options: []
 require_paths:
 - lib
@@ -190,7 +173,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '0'
+      version: '3.2'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="

data/lib/patches/capistrano/tasks.rake

@@ -1,12 +0,0 @@
-namespace :patches do
-  desc 'Runs rake patches:run'
-  task :run do
-     on primary fetch(:migration_role) do
-        within release_path do
-           with rails_env: fetch(:rails_env) do
-              execute :rake, "patches:run"
-           end
-        end
-     end
-  end
-end

data/lib/patches/capistrano.rb

@@ -1,5 +0,0 @@
-require 'patches/deprecation'
-
-Patches.warn_capistrano_support_removed_in_4_0
-
-load File.expand_path("capistrano/tasks.rake", File.dirname(__FILE__))

data/lib/patches/sidekiq_job.rb

@@ -1,18 +0,0 @@
-require 'sidekiq'
-require 'patches/deprecation'
-
-module Patches
-  # Sidekiq renamed Sidekiq::Worker to Sidekiq::Job in 6.3 and still ships the
-  # old name as a deprecated alias. Resolving it at include time keeps the
-  # workers working on every Sidekiq this gem has ever supported, so the change
-  # needs no version bump from consumers.
-  def self.sidekiq_job_module
-    return ::Sidekiq::Job if defined?(::Sidekiq::Job)
-
-    deprecator.warn(
-      'Sidekiq older than 6.3 does not provide Sidekiq::Job; patches 4.0 is ' \
-      'expected to require it. Upgrade Sidekiq, which supports 7.x and 8.x.'
-    )
-    ::Sidekiq::Worker
-  end
-end