patches 3.6.3 → 3.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7eea93b86dd926979c0b3cf0fcf292711d7ce1cb6256950458eed354a4783749
-  data.tar.gz: f3305c8346f6d2b5d657de8c25b69ed820ff8149dca2fb5724204d77a9cda5f4
+  metadata.gz: 895215b6ac8fa6eb09aea79add6efebcead371d5b50579d983b70eff79c58682
+  data.tar.gz: aa05b38f701c0c525364d16f0f22dc7fde9b33c2a34aac240751e78b02d1c3d6
 SHA512:
-  metadata.gz: 52fa0f3c8458a92cc8e4fa9e8ec65856943ab06148bec02c706175699dcb2d5042b71699039c14461e272fe0e8bfcdf2cda4eb68639f3100fd75fb9cd8539224
-  data.tar.gz: c4548f2c1d92fd32648062443e5c156838c9b02c3b4e02d755b376a9583adc59bf8c3df3bb707494b4d1605660403ed00b56e2835eef0996f9275fc54d28183a
+  metadata.gz: e454bd2d14b1cf02eca6fc4bd18d3732c83627032c0a6a2fb76dbf6c43d07da7ee6786f542c8f689290b75deedc48ea8fb1b8eeb0581363fd48e9719a3478e38
+  data.tar.gz: a286831eb61b05d4fbdee99989247671307d3881433e293eacda3afc533b262d0d82d1cb6e098a0c3f4153b01891bd0e4ecece47f235ed36d09715ebb81e3c64

data/CHANGELOG.md

@@ -6,7 +6,55 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
-Converted to GitHub Actions for CI
+## [3.7.0] - 2026-09-10
+
+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,19 +1,58 @@
 # 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'
+```
+
+Then install the migration that records which patches have run:
+
+```
+bundle exec rake patches:install:migrations
+bundle exec rake db:migrate
+```
+
+## Usage
+
+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
+```
 
-## Version 2.0
+Run the pending ones - each patch runs once, and is recorded in
+`patches_patches`:
 
-Please note the breaking change release around deployment. See [docs/usage.md](docs/usage.md) for the full change.
+```
+bundle exec rake patches:run
+```
 
-TL;DR You need to manually declare the patches task to run in your deploy.rb
+`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
 
@@ -107,30 +146,58 @@ 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
+## Deprecations
 
-Add this line to your application's Gemfile:
+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:
 
 ```ruby
-gem 'patches'
+Patches.deprecator.behavior = :silence  # or :raise, :log, a lambda...
 ```
-And then execute:
 
-    $ bundle
+| Deprecated | Replacement |
+|---|---|
+| 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 |
 
-Or install it yourself as:
+Nothing is removed in this release, and the gemspec floors are unchanged, so
+anything that installed 3.6.x installs 3.7.0.
 
-    $ gem install patches
+## Development
 
-## Usage
+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:
 
-see [docs/usage.md](docs/usage.md)
+```
+docker compose build
+docker compose run --rm app
+```
 
-## Development
+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:
 
 ```
-docker-compose build
-docker-compose run app bundle exec rspec
+docker compose build --build-arg RUBY_VERSION=3.1
+
+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"'
+```
+
+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 +213,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/docs/usage.md

@@ -22,6 +22,10 @@ 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.
+
 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,6 +117,11 @@ bundle exec rake patches:run
 
 Patches will only ever run once, patches will run in order of creation date.
 
+### Capistrano
+
+> **Deprecated.** `patches/capistrano` is removed in 4.0. Invoke
+> `rake patches:run` from your deployment process instead.
+
 To run patches on deployment using Capistrano, edit your Capfile and add
 
 ```ruby

data/lib/patches/capistrano.rb

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

data/lib/patches/config.rb

@@ -1,3 +1,5 @@
+require 'patches/deprecation'
+
 module Patches
   class Config
     class << self
@@ -30,6 +32,18 @@ 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

@@ -0,0 +1,48 @@
+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.
+  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}."
+    )
+  end
+end

data/lib/patches/engine.rb

@@ -3,5 +3,14 @@ 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/sidekiq_job.rb

@@ -1,4 +1,5 @@
 require 'sidekiq'
+require 'patches/deprecation'
 
 module Patches
   # Sidekiq renamed Sidekiq::Worker to Sidekiq::Job in 6.3 and still ships the
@@ -6,6 +7,12 @@ module Patches
   # 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
+    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

data/lib/patches/version.rb

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

data/lib/patches.rb

@@ -19,6 +19,7 @@ module Patches
   end
 end
 
+require "patches/deprecation"
 require "patches/base"
 require "patches/config"
 require "patches/tenant_run_concern"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: patches
 version: !ruby/object:Gem::Version
-  version: 3.6.3
+  version: 3.7.0
 platform: ruby
 authors:
 - ReadyTech
@@ -23,6 +23,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '3.2'
+- !ruby/object:Gem::Dependency
+  name: activerecord
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '3.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
@@ -134,23 +148,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
@@ -161,6 +162,7 @@ files:
 - 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
@@ -173,11 +175,14 @@ files:
 - 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/v3.7.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
 rdoc_options: []
 require_paths:
 - lib

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/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