patches 3.6.3 → 4.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7eea93b86dd926979c0b3cf0fcf292711d7ce1cb6256950458eed354a4783749
-  data.tar.gz: f3305c8346f6d2b5d657de8c25b69ed820ff8149dca2fb5724204d77a9cda5f4
+  metadata.gz: 4d3cb95acebf22bd69de36b12b559515c6c2cf39160bfb6a135af5677ef90ad8
+  data.tar.gz: db396ae1486ff61282a2b363dd3fc3dceb3bdad6247ba4bce5ae409ccef939d8
 SHA512:
-  metadata.gz: 52fa0f3c8458a92cc8e4fa9e8ec65856943ab06148bec02c706175699dcb2d5042b71699039c14461e272fe0e8bfcdf2cda4eb68639f3100fd75fb9cd8539224
-  data.tar.gz: c4548f2c1d92fd32648062443e5c156838c9b02c3b4e02d755b376a9583adc59bf8c3df3bb707494b4d1605660403ed00b56e2835eef0996f9275fc54d28183a
+  metadata.gz: 672d33b4552fbdcd038949290361b9da0cbc346e300811ee423ee5bf95069d6399c90b6eab06600706377a5070bc6e6012ebea6c26f5bafea523d44d0daf7806
+  data.tar.gz: 47452cd282ccaa753399e74eecd97bc7407514de7f09cb22ac30e7a5d1d6e9c1b6786d43572408442d69b70378517cfbbd2b5482a73684a1e0ea6672a0e59a2c

data/CHANGELOG.md

@@ -6,7 +6,96 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
-Converted to GitHub Actions for CI
+## [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
+anything that installed 3.6.x installs this.
+
+### Added
+- Gem metadata (`source_code_uri`, `changelog_uri`, `bug_tracker_uri`,
+  `documentation_uri`). None were declared, so rubygems.org kept showing values
+  carried over from older releases - 3.6.3 still lists `source_code_uri` as
+  `http://github.com/jobready/patches`, from before the org was renamed
+- `activerecord` as an explicit runtime dependency, at the same `>= 3.2` floor
+  as `railties` so nothing currently installable is excluded. `Patches::Patch`
+  subclasses `ActiveRecord::Base` and `Patches::Base#execute` calls
+  `ActiveRecord::Base.connection`, but only `railties` had been declared
+- `Patches.deprecator`, a gem-owned `ActiveSupport::Deprecation` instance rather
+  than the singleton Rails 7.1 deprecated and 8.0 removed. Host applications can
+  silence or redirect it with `Patches.deprecator.behavior = :silence`
+- A deprecation warning when `config.use_slack` is set: from 4.0 Patches will
+  not depend on `slack-notifier`, so only applications using Slack carry it.
+  Add `gem 'slack-notifier'` to your Gemfile to keep notifications working
+- A deprecation warning on `require 'patches/capistrano'`. The Capistrano task
+  is removed in 4.0; invoke `rake patches:run` from your deployment process
+  instead. It remains opt-in and loads nothing unless a Capfile requires it
+- Deprecation warnings for the two other things 4.0 is expected to require:
+  Sidekiq 6.3 or newer, which is where `Sidekiq::Job` arrives, and Ruby 3.2 /
+  Rails 7.2. Those floors are higher than the range CI verifies - Ruby 3.0 and
+  Rails 7.1 still pass - so anyone below them hears about it a release ahead.
+  The Ruby and Rails notice runs from a Rails initializer, after the
+  application's own, so `Patches.deprecator.behavior` can silence it
+
+### Changed
+- The published gem carries only what a consumer needs - 27 files rather than
+  42. `Dockerfile`, `docker-compose.yml`, `.devcontainer/`, `.github/`, `bin/`,
+  `Rakefile`, `RELEASING.md` and a decorative image were being packaged. `lib`,
+  the install migration, `docs/usage.md` and the top-level docs remain
+- The development container works again. It was pinned to `ruby:2.3`, which
+  cannot satisfy the current Gemfile, and had not been touched since 2018. The
+  Ruby version is now a build argument and the gem versions are passed through
+  from the shell, so any cell of the matrix in README.md is reproducible in it.
+  A `.devcontainer/` referencing the same compose service comes with it, for
+  VS Code and Codespaces
+
+### Removed
+- `.github/workflows/publish.yml`. It published on `release: published` using a
+  `GEM_HOST_API_KEY`, had never run in the four years since it was added, and
+  would now attempt a duplicate push if a GitHub Release were created after a
+  tag. Releases come from `.github/workflows/release.yml` - see
+  [RELEASING.md](RELEASING.md)
 
 ## [3.6.3] - 2026-09-09
 

data/README.md

@@ -1,41 +1,77 @@
 # Patches
 [![Run specs](https://github.com/rdytech/patches/actions/workflows/specs.yml/badge.svg)](https://github.com/rdytech/patches/actions/workflows/specs.yml)
-[![Maintainability](https://api.codeclimate.com/v1/badges/39d142050017ffeb2564/maintainability)](https://codeclimate.com/repos/557f93b76956807f81000001/maintainability)
-[![Test Coverage](https://api.codeclimate.com/v1/badges/39d142050017ffeb2564/test_coverage)](https://codeclimate.com/repos/557f93b76956807f81000001/test_coverage)
 [![Gem Version](https://badge.fury.io/rb/patches.svg)](https://badge.fury.io/rb/patches)
 
 ![patches](docs/patches.jpg)
 
+A simple gem for one off tasks - the things that do not belong in a schema
+migration. Back-filling a column, correcting bad data, kicking off a one-time
+import: write it as a class, deploy it, and Patches runs it once and records
+that it ran.
 
-A simple gem for one off tasks
+## Installation
+
+Add the gem to your application's Gemfile:
+
+```ruby
+gem 'patches'
+```
 
-## Version 2.0
+Then install the migration that records which patches have run:
 
-Please note the breaking change release around deployment. See [docs/usage.md](docs/usage.md) for the full change.
+```
+bundle exec rake patches:install:migrations
+bundle exec rake db:migrate
+```
+
+## Usage
 
-TL;DR You need to manually declare the patches task to run in your deploy.rb
+Generate a patch:
+
+```
+bundle exec rails g patches:patch PreferenceUpdate
+```
+
+Fill in `run`:
+
+```ruby
+class PreferenceUpdate < Patches::Base
+  def run
+    User.where(preference: nil).update_all(preference: 'default')
+  end
+end
+```
+
+Run the pending ones - each patch runs once, and is recorded in
+`patches_patches`:
+
+```
+bundle exec rake patches:run
+```
+
+`rake patches:pending` lists what has not run yet. Patches can run inline or in
+the background via Sidekiq, across all tenants when you use Apartment, and
+report to Slack. See [docs/usage.md](docs/usage.md) for configuration, tenants,
+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
@@ -44,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
 
@@ -107,30 +147,55 @@ 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.
 
-## Installation
+## Upgrading from 3.x
 
-Add this line to your application's Gemfile:
+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
-gem 'patches'
-```
-And then execute:
+| Change | What to do |
+|---|---|
+| 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.
 
-    $ bundle
+## Development
 
-Or install it yourself as:
+In VS Code or Codespaces, open the repository in the dev container - it reuses
+the `app` service from `docker-compose.yml`, so there is one definition of the
+environment rather than two. Otherwise, from a shell:
 
-    $ gem install patches
+```
+docker compose build
+docker compose run --rm app
+```
 
-## Usage
+The container's default command runs the specs. Any cell of the matrix above is
+reproducible in it: the Ruby version is a build argument, and the gem versions
+are passed through from your shell. The image is built with the default
+versions, so a non-default cell has to install them first:
 
-see [docs/usage.md](docs/usage.md)
+```
+docker compose build --build-arg RUBY_VERSION=3.1
 
-## Development
+RAILS_VERSION="~> 7.1.0" docker compose run --rm app \
+  sh -c 'bundle install && bundle exec rspec'
 
+SIDEKIQ_VERSION=none docker compose run --rm app \
+  sh -c 'bundle install && bundle exec rspec --exclude-pattern "sidekiq/**/*_spec.rb"'
 ```
-docker-compose build
-docker-compose run app bundle exec rspec
+
+Or without Docker, if you have the Ruby you want on your path:
+
+```
+bundle install
+bundle exec rspec
 ```
 
 To install this gem onto your local machine, run `bundle exec rake install`.
@@ -146,4 +211,4 @@ Releases are published by GitHub Actions from a `vX.Y.Z` tag — see
 2. Create your feature branch (`git checkout -b feature/my-feature-name`)
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin feature/my-new-feature`)
-5. Create a new Pull Request
+5. Create a new Pull Request against `develop`

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,6 +22,9 @@ bundle exec rake db:migrate
 
 ## Configuration
 
+> **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
 an initializer to set those options.
@@ -113,21 +116,18 @@ bundle exec rake patches:run
 
 Patches will only ever run once, patches will run in order of creation date.
 
-To run patches on deployment using Capistrano, edit your Capfile and add
-
-```ruby
-require 'patches/capistrano'
-```
+### Running on deploy
 
-And then in your deploy.rb
+Invoke the rake task from your deployment process, after the application code is
+in place:
 
-```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/deprecation.rb

@@ -0,0 +1,12 @@
+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. 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('5.0', 'patches')
+  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 = 6
-  PATCH = 3
+  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)
@@ -19,13 +26,13 @@ module Patches
   end
 end
 
+require "patches/deprecation"
 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.6.3
+  version: 4.0.0
 platform: ruby
 authors:
 - ReadyTech
@@ -15,28 +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: slack-notifier
+  name: activerecord
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '7.2'
   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
@@ -134,23 +134,10 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".github/workflows/publish.yml"
-- ".github/workflows/release.yml"
-- ".github/workflows/specs.yml"
-- ".gitignore"
-- ".rspec"
 - CHANGELOG.md
-- Dockerfile
-- Gemfile
 - LICENSE.md
 - README.md
-- RELEASING.md
-- Rakefile
-- bin/console
-- bin/setup
 - db/migrate/201506011700_create_patch.rb
-- docker-compose.yml
-- docs/patches.jpg
 - docs/usage.md
 - lib/generators/patches/patch_generator.rb
 - lib/generators/patches/templates/patch.rb.erb
@@ -158,26 +145,27 @@ 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
 - lib/patches/notifier.rb
 - 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
 - lib/patches/version.rb
 - lib/patches/worker.rb
 - lib/tasks/patches.rake
-- patches.gemspec
 homepage: https://github.com/rdytech/patches
 licenses:
 - MIT
-metadata: {}
+metadata:
+  source_code_uri: https://github.com/rdytech/patches
+  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/v4.0.0/docs/usage.md
 rdoc_options: []
 require_paths:
 - lib
@@ -185,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/.github/workflows/publish.yml

@@ -1,26 +0,0 @@
-name: Publish
-
-on:
-  release:
-    types: [published]
-
-jobs:
-  build:
-    name: Build + Publish
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
-
-    steps:
-    - uses: actions/checkout@v3
-    - uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: '2.7'
-
-    - name: Publish to RubyGems
-      run: |
-        gem build *.gemspec
-        gem push *.gem
-      env:
-        GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"

data/.github/workflows/release.yml

@@ -1,35 +0,0 @@
-name: Release
-
-on:
-  push:
-    tags: ["v*"]
-
-permissions:
-  contents: write   # rake release (via rubygems/release-gem) pushes the tag; no-op here since it's already pushed
-  id-token: write   # RubyGems.org OIDC trusted publishing
-  packages: write   # GitHub Packages push
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v5
-        with:
-          fetch-depth: 0
-          persist-credentials: false
-
-      - name: Verify tag is reachable from develop
-        run: |
-          if ! git merge-base --is-ancestor "$GITHUB_SHA" origin/develop; then
-            echo "::error::$GITHUB_REF_NAME is not reachable from develop. Refusing to publish."
-            exit 1
-          fi
-
-      - name: Set up Ruby
-        uses: ruby/setup-ruby@v1
-        with:
-          bundler-cache: true
-          ruby-version: "3.4"
-
-      - name: Publish to RubyGems.org
-        uses: rubygems/release-gem@v1

data/.github/workflows/specs.yml

@@ -1,113 +0,0 @@
-name: Run specs
-on:
-  workflow_dispatch:
-  pull_request:
-    branches:
-      - develop
-  push:
-    branches:
-      - develop
-
-jobs:
-  # This patch release changes no version constraint, so the matrix records the
-  # range the gem is verified against rather than narrowing what it allows -
-  # older Ruby and Rails remain permitted, just untested. Rails 6.1/7.0 and
-  # Ruby 2.7 are left out deliberately: they are long past upstream support,
-  # and they were the cells that needed harness pins (Rails <= 7.0 pins its
-  # sqlite3 adapter to `~> 1.4`, Rails < 7.1 predates concurrent-ruby 1.3.5
-  # dropping a Logger constant) or a pinned runner image. The Gemfile still
-  # accepts those overrides for reproducing an old combination locally.
-  specs:
-    name: Ruby ${{ matrix.ruby }} / Rails ${{ matrix.rails }}
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-          - { ruby: '3.0', rails: '~> 7.1.0' }
-          - { ruby: '3.1', rails: '~> 7.1.0' }
-          - { ruby: '3.1', rails: '~> 7.2.0' }
-          - { ruby: '3.2', rails: '~> 7.1.0' }
-          - { ruby: '3.2', rails: '~> 7.2.0' }
-          - { ruby: '3.2', rails: '~> 8.0.0' }
-          - { ruby: '3.2', rails: '~> 8.1.0' }
-          - { ruby: '3.3', rails: '~> 7.1.0' }
-          - { ruby: '3.3', rails: '~> 7.2.0' }
-          - { ruby: '3.3', rails: '~> 8.0.0' }
-          - { ruby: '3.3', rails: '~> 8.1.0' }
-          - { ruby: '3.4', rails: '~> 7.2.0' }
-          - { ruby: '3.4', rails: '~> 8.0.0' }
-          - { ruby: '3.4', rails: '~> 8.1.0' }
-          - { ruby: '4.0', rails: '~> 7.2.0' }
-          - { ruby: '4.0', rails: '~> 8.0.0' }
-          - { ruby: '4.0', rails: '~> 8.1.0' }
-    env:
-      RAILS_VERSION: ${{ matrix.rails }}
-    steps:
-      - uses: actions/checkout@v4
-      - uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: ${{ matrix.ruby }}
-          bundler-cache: true
-      - name: Run specs
-        run: bundle exec rspec
-
-  # Sidekiq is optional, so it gets its own axis rather than multiplying the
-  # matrix above. All three states a consumer can be in are covered: absent,
-  # present with strict argument checking (the Sidekiq 7+ default), and present
-  # with it disabled. The 6.5 leg covers the Sidekiq::Worker-era fallback path.
-  sidekiq:
-    name: Sidekiq ${{ matrix.sidekiq }} (strict args ${{ matrix.strict_args || 'absent' }})
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-          - { sidekiq: '~> 6.5' }
-          - { sidekiq: '~> 7.0', strict_args: 'raise' }
-          - { sidekiq: '~> 7.0', strict_args: 'false' }
-          - { sidekiq: '~> 8.0', strict_args: 'raise' }
-          - { sidekiq: '~> 8.0', strict_args: 'false' }
-          - { sidekiq: 'none' }
-    env:
-      SIDEKIQ_VERSION: ${{ matrix.sidekiq }}
-      SIDEKIQ_STRICT_ARGS: ${{ matrix.strict_args }}
-    steps:
-      - uses: actions/checkout@v4
-      - uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: '3.4'
-          bundler-cache: true
-      - name: Run specs
-        run: |
-          if [ "$SIDEKIQ_VERSION" = "none" ]; then
-            bundle exec rspec --exclude-pattern "sidekiq/**/*_spec.rb"
-          else
-            bundle exec rspec
-          fi
-
-  sonarqube:
-    name: SonarQube
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: '3.2'
-          bundler-cache: true
-      - name: Run specs
-        run: bundle exec rspec
-
-      - name: SonarQube Scan
-        uses: sonarsource/sonarqube-scan-action@master
-        with:
-          args: >
-            -Dsonar.projectKey=rdytech_patches_4fe7fcf4-bbfc-4b19-be78-87e73d1f301e
-            -Dsonar.host.url=https://sonarqube.readytech.io
-            -Dsonar.sources=lib/
-            -Dsonar.inclusions=**/*.rb
-            -Dsonar.tests=spec/
-            -Dsonar.ruby.coverage.reportPaths=coverage/.resultset.json
-            -Dsonar.plugins.downloadOnlyRequired=true
-        env:
-          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}

data/.gitignore

@@ -1,13 +0,0 @@
-/.bundle/
-/.yardoc
-/Gemfile.lock
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-/coverage/
-/test.db
-/*.gem
-.byebug_history

data/.rspec

@@ -1,2 +0,0 @@
---color
---require spec_helper

data/Dockerfile

@@ -1,9 +0,0 @@
-FROM ruby:2.3
-
-RUN touch ~/.gemrc && echo "gem: --no-ri --no-rdoc" >> ~/.gemrc
-
-WORKDIR /app/
-ADD . /app/
-RUN bundle install
-
-CMD bundle exec rake -T

data/Gemfile

@@ -1,39 +0,0 @@
-source 'https://rubygems.org'
-
-gemspec
-
-# rails, sqlite3, concurrent-ruby and sidekiq are declared here rather than in
-# the gemspec so that CI can vary them across the support matrix in README.md.
-# Reproduce any CI cell locally by setting the same variables:
-#
-#   RAILS_VERSION="~> 7.0.0" SQLITE3_VERSION="~> 1.4" bundle install
-#   bundle exec rspec
-#
-# An unset *or empty* value falls back to the default, because GitHub Actions
-# passes an empty string for matrix keys a given cell doesn't define.
-def version_requirement(name, default = nil)
-  value = ENV.fetch(name, '').strip
-  value.empty? ? default : value
-end
-
-# Unset, this resolves to the newest Rails the running Ruby allows. The gemspec
-# floor stays at railties >= 3.2; see Compatibility in README.md for the range
-# CI verifies.
-gem 'rails', version_requirement('RAILS_VERSION', '>= 7.1')
-
-# Rails pins its sqlite3 adapter: <= 7.0 needs `~> 1.4`, 7.1 accepts either,
-# 8.0+ needs `>= 2.1`. Unset, bundler picks the newest 2.x.
-gem 'sqlite3', version_requirement('SQLITE3_VERSION', '>= 1.4')
-
-# Rails < 7.1 predates concurrent-ruby 1.3.5 removing the Logger constant that
-# ActiveSupport::LoggerThreadSafeLevel expects.
-concurrent_ruby = version_requirement('CONCURRENT_RUBY_VERSION')
-gem 'concurrent-ruby', concurrent_ruby if concurrent_ruby
-
-# Sidekiq is an optional integration, not a runtime dependency. SIDEKIQ_VERSION
-# =none leaves it out entirely so the `defined?(Sidekiq)` guards get exercised.
-# The library itself still supports older Sidekiq through
-# Patches.sidekiq_job_module; this default only picks what the suite runs
-# against by default.
-sidekiq = version_requirement('SIDEKIQ_VERSION')
-gem 'sidekiq', *[sidekiq].compact unless sidekiq == 'none'

data/RELEASING.md

@@ -1,50 +0,0 @@
-# Releasing patches
-
-Publishing is only ever done by GitHub Actions (`.github/workflows/release.yml`), triggered by
-a `vX.Y.Z` tag whose commit is reachable from `develop`. Tags on any other branch are rejected by
-the workflow before anything is built. No one needs local publishing credentials — the workflow
-authenticates to RubyGems.org via OIDC trusted publishing.
-
-The `v` prefix is required: the workflow triggers on `v*`, and it is the tag `rake release`
-creates. RubyGems.org strips it, so `v3.6.3` publishes version `3.6.3` — which is why the
-versions listed on rubygems.org never carry the prefix.
-
-## Cutting a release
-
-1. Bump `MAJOR` / `MINOR` / `PATCH` in `lib/patches/version.rb`.
-2. Add a new `## [X.Y.Z] - YYYY-MM-DD` entry to the top of `CHANGELOG.md` describing the changes.
-3. Commit both changes and get them onto `develop` (PR + merge, as normal).
-4. From an up-to-date `develop`, tag the commit and push the tag:
-
-   ```bash
-   git tag vX.Y.Z
-   git push origin vX.Y.Z
-   ```
-
-5. Watch the "Release" workflow run in the Actions tab.
-6. Confirm the new version shows up on [rubygems.org](https://rubygems.org/gems/patches).
-
-Do **not** run `bundle exec rake release` from a workstation. It would push the gem under your own
-credentials *and* push the tag, and the workflow's own `rake release` would then fail because the
-version already exists.
-
-## One-time setup
-
-- **RubyGems.org**: an existing owner of the `patches` gem must add a Trusted Publisher for
-  `rdytech/patches`, workflow `release.yml` (no environment). See
-  [Trusted Publishing: adding a publisher](https://guides.rubygems.org/trusted-publishing/adding-a-publisher/).
-  Until this is done, the release will fail while configuring credentials. The gem currently lists
-  a single owner, handle `jr`.
-- **GitHub Packages**: the workflow carries a `packages: write` permission, inherited from the
-  shared workflow, but no step publishes there and nothing is pushed to it.
-
-## Why this exists
-
-Six tagged versions never reached RubyGems.org — `2.0.1`, `2.1.0`, `2.2.0`, `2.3.0`, `3.0.0` and
-`3.6.1` — and nothing reported the gap. The `3.6.2` entry in `CHANGELOG.md` ("Fixes incorrect
-release - tag and published gem back in sync") is the visible trace of the most recent one:
-`3.6.1` was tagged and released on GitHub but never published, because
-`.github/workflows/publish.yml` was added the same day and has never run.
-
-`rubygems/release-gem` waits for the new version to appear on RubyGems.org before the job
-succeeds, so a release that does not land now fails loudly instead of passing unnoticed.

data/Rakefile

@@ -1,2 +0,0 @@
-require "bundler/gem_tasks"
-

data/bin/console

@@ -1,14 +0,0 @@
-#!/usr/bin/env ruby
-
-require "bundler/setup"
-require "patches"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start

data/bin/setup

@@ -1,7 +0,0 @@
-#!/bin/bash
-set -euo pipefail
-IFS=$'\n\t'
-
-bundle install
-
-# Do any other automated setup that you need to do here

data/docker-compose.yml

@@ -1,11 +0,0 @@
-version: '3.2'
-services:
-  app:
-    build: .
-    volumes:
-      - .:/app
-      - app-gems:/usr/local/bundle
-
-volumes:
-  app-gems:
-    driver: local

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 +0,0 @@
-load File.expand_path("capistrano/tasks.rake", File.dirname(__FILE__))

data/lib/patches/sidekiq_job.rb

@@ -1,11 +0,0 @@
-require 'sidekiq'
-
-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
-    defined?(::Sidekiq::Job) ? ::Sidekiq::Job : ::Sidekiq::Worker
-  end
-end

data/patches.gemspec

@@ -1,43 +0,0 @@
-# coding: utf-8
-lib = File.expand_path('../lib', __FILE__)
-$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require 'patches/version'
-
-Gem::Specification.new do |spec|
-  spec.name          = "patches"
-  spec.version       = Patches::VERSION
-  spec.authors       = ["ReadyTech"]
-  spec.email         = ["ruby_gems@readytech.io"]
-
-  spec.licenses    = ['MIT']
-  spec.summary       = %q{A simple gem for one off tasks}
-  spec.description   = %q{A simple gem for one off tasks for example database patches}
-  spec.homepage      = "https://github.com/rdytech/patches"
-
-  spec.files         = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
-  spec.bindir        = "exe"
-  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
-  spec.require_paths = ["lib"]
-
-  # Runtime constraints are deliberately unchanged here: raising a minimum can
-  # block an install that works today, which is a major-version change.
-  # README.md records the range CI actually verifies. Declaring activerecord
-  # (Patches::Patch subclasses ActiveRecord::Base) and bounding slack-notifier
-  # are queued for the next minor.
-  spec.add_dependency "railties", ">= 3.2"
-  spec.add_dependency "slack-notifier"
-
-  spec.add_development_dependency "bundler", "> 1.8"
-  spec.add_development_dependency "rake", "> 10.0"
-  spec.add_development_dependency "rspec", "~> 3.13"
-  spec.add_development_dependency "simplecov", "~> 0.17", '< 0.18' # sonarscanner requires < 0.18
-  spec.add_development_dependency "pry"
-  spec.add_development_dependency "webmock"
-
-  # rails, sqlite3, sidekiq and concurrent-ruby live in the Gemfile so CI can
-  # vary them across the range documented in README.md. capybara, factory_girl,
-  # timecop, generator_spec, byebug and database_cleaner were referenced by no
-  # spec, and rspec-rails was never required, so plain rspec replaces it.
-  # Sidekiq is an optional integration, not a runtime dependency, and the suite
-  # is expected to pass without it installed.
-end