sqewer 8.1.0.pre.1 → 9.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2e70ce730cb17b406aea473b69ae23be5f47416175b196e2d2dfd0cdda40fdfc
-  data.tar.gz: c8e9333070997feee75ed80cded51bbd444ee3bc0b3c5f32f518e7b283989e71
+  metadata.gz: a77289a915370519a947d35eca6c37eaca54fd319a1bb47cf9ab6889d509a3d0
+  data.tar.gz: dfb8c88266e50af819c66c93c56fffebb14f675f6e6f8ec4c8869f1e2a7a6edb
 SHA512:
-  metadata.gz: 34c20b7e17f72cb69d0e505110e1d3f2fd50bc2f6b97411f145cfabcb279b433672a8fbd34d0dc7611dc7447eb2d2d753ae78b98833c976a00aa793a37f5f383
-  data.tar.gz: 5038a056984b20d6f5b9b535cceefb54e01ebb3f16060f001133c61a93f4684cda3aacb0b4e18bef9a70be0912310dd4f362737870f0c3da52d283ec0308a115
+  metadata.gz: 89cf6418255c49a5ddb83d27bcf8e8bca8c017dc15cad9e6fd77a41cb44b795400f474667b72bc3c6849792dabbd6742be07bc90c4fa441659166749a8b55fbd
+  data.tar.gz: 71e0f5ee37e30ee4729179da5c29eb231c527b9f7e7415ae11ae2109e6ac2ef7e6ecaeebf38c14f1de70a9fb9892570c1f6abb531fcf340fe74a1ea079dce698

data/.github/workflows/main.yml

@@ -9,14 +9,12 @@ jobs:
     strategy:
       matrix:
         ruby:
+          - 3.2
           - 3.1
           - 3.0
-          - 2.7
-          - 2.6
         gemfile:
-          - gemfiles/Gemfile.rails-5.0.x
-          - gemfiles/Gemfile.rails-5.1.x
-          - gemfiles/Gemfile.rails-6.0.x
+          - gemfiles/Gemfile.rails-6.1.x
+          - gemfiles/Gemfile.rails-7.0.x
     env:
       SQS_QUEUE_URL: 'sqlite3://tmp/sqewer.sqlite3'
       AWS_REGION: 'eu-central-1'

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+### 9.0.0
+- Add support for Ruby 3.2 and Rails 7
+- Remove support for Ruby 2.6, 2.7 and Rails 5 and 6.0
+
 ### 8.1.0
 - dropped dependency on `ks` gem
 - added rails6 and ruby3/3.1 to test matrix

data/README.md

@@ -48,7 +48,7 @@ The messages will only be deleted from SQS once the job execution completes with
 
 ## Requirements
 
-Ruby 2.6+, version 2 of the AWS SDK. You can also run Sqewer backed by a SQLite database file, which can be handy for development situations.
+Ruby 3+, version 2 of the AWS SDK. You can also run Sqewer backed by a SQLite database file, which can be handy for development situations.
 
 ## Job storage
 
@@ -415,4 +415,3 @@ the Ruby standard library alone.
 ## Copyright
 
 Copyright (c) 2016 WeTransfer. See LICENSE.txt for further details.
-

data/gemfiles/{Gemfile.rails-5.1.x → Gemfile.rails-6.1.x}

@@ -4,5 +4,5 @@ source "http://rubygems.org"
 gemspec path: __dir__ + '/..'
 
 gem 'sqlite3', "~> 1.3", ">= 1.3.6"
-gem 'activejob', "~> 5.1.0"
-gem 'activerecord', "~> 5.1.0"
+gem 'activejob', "~> 6.1.0"
+gem 'activerecord', "~> 6.1.0"

data/gemfiles/{Gemfile.rails-6.0.x → Gemfile.rails-7.0.x}

@@ -4,5 +4,5 @@ source "http://rubygems.org"
 gemspec path: __dir__ + '/..'
 
 gem 'sqlite3', "~> 1.3", ">= 1.3.6"
-gem 'activejob', "~> 6.0.0"
-gem 'activerecord', "~> 6.0.0"
+gem 'activejob', "~> 7.0.0"
+gem 'activerecord', "~> 7.0.0"

data/lib/sqewer/extensions/active_job_adapter.rb

@@ -1,14 +1,6 @@
 # ActiveJob docs: http://edgeguides.rubyonrails.org/active_job_basics.html
 # Example adapters ref: https://github.com/rails/rails/tree/master/activejob/lib/active_job/queue_adapters
 module ActiveJob
-  # Only prepend the module with keyword argument acceptance when the version is 4
-  # ActiveJob 5.x supports kwargs out of the box
-  if ActiveJob::VERSION::MAJOR <= 4
-    module Execution
-      prepend PerformWithKeywords
-    end
-  end
-
   module QueueAdapters
     # Handle Rails ActiveJob through sqewer.
     # Set it up like so:
@@ -56,48 +48,32 @@ module ActiveJob
             Base.execute(job)
           end
         end
-        
+
         private
-        
+
         def with_active_record_connection_from_pool
           ActiveRecord::Base.connection_pool.with_connection { yield }
         end
-        
+
         def active_record_defined_and_connected?
           defined?(ActiveRecord) && ActiveRecord::Base.connected?
         end
-        
+
       end
 
-      def self.enqueue(active_job) #:nodoc:
+      def enqueue(*args)
         wrapped_job = Performable.from_active_job(active_job)
 
         Sqewer.submit!(wrapped_job)
       end
 
-      def self.enqueue_at(active_job, timestamp) #:nodoc:
+      def enqueue_at(*args)
         wrapped_job = Performable.from_active_job(active_job)
 
         delta_t = (timestamp - Time.now.to_i).to_i
 
         Sqewer.submit!(wrapped_job, delay_seconds: delta_t)
       end
-
-      # ActiveJob in Rails 4 resolves the symbol value you give it
-      # and then tries to call enqueue_* methods directly on what
-      # got resolved. In Rails 5, first Rails will call .new on
-      # what it resolved from the symbol and _then_ call enqueue
-      # and enqueue_at on that what has gotten resolved. This means
-      # that we have to expose these methods _both_ as class methods
-      # and as instance methods.
-      # This can be removed when we stop supporting Rails 4.
-      def enqueue_at(*args)
-        self.class.enqueue_at(*args)
-      end
-      
-      def enqueue(*args)
-        self.class.enqueue(*args)
-      end
     end
   end
 end

data/lib/sqewer/version.rb

@@ -1,3 +1,3 @@
 module Sqewer
-  VERSION = '8.1.0.pre.1'
+  VERSION = '9.0.0'
 end

data/sqewer.gemspec

@@ -12,7 +12,7 @@ Gem::Specification.new do |spec|
   spec.summary       = %q{Process jobs from SQS}
   spec.description   = %q{A full-featured library for all them SQS worker needs}
   spec.homepage      = "https://github.com/WeTransfer/sqewer"
-  spec.required_ruby_version = Gem::Requirement.new(">= 2.6.0")
+  spec.required_ruby_version = Gem::Requirement.new(">= 3.0.0")
 
   # Prevent pushing this gem to RubyGems.org. To allow pushes either set the "allowed_push_host"
   # to allow pushing to a single host or delete this section to allow pushing to any host.

metadata

@@ -1,15 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: sqewer
 version: !ruby/object:Gem::Version
-  version: 8.1.0.pre.1
+  version: 9.0.0
 platform: ruby
 authors:
 - Julik Tarkhanov
 - Andrei Horak
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2022-11-09 00:00:00.000000000 Z
+date: 2023-09-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-sqs
@@ -260,9 +260,8 @@ files:
 - bin/sqewer
 - bin/sqewer_rails
 - example.env
-- gemfiles/Gemfile.rails-5.0.x
-- gemfiles/Gemfile.rails-5.1.x
-- gemfiles/Gemfile.rails-6.0.x
+- gemfiles/Gemfile.rails-6.1.x
+- gemfiles/Gemfile.rails-7.0.x
 - lib/sqewer.rb
 - lib/sqewer/atomic_counter.rb
 - lib/sqewer/cli.rb
@@ -288,7 +287,7 @@ homepage: https://github.com/WeTransfer/sqewer
 licenses: []
 metadata:
   allowed_push_host: https://rubygems.org
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -296,15 +295,15 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.6.0
+      version: 3.0.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
-rubygems_version: 3.0.3.1
-signing_key: 
+rubygems_version: 3.4.10
+signing_key:
 specification_version: 4
 summary: Process jobs from SQS
 test_files: []

data/gemfiles/Gemfile.rails-5.0.x

@@ -1,8 +0,0 @@
-source "http://rubygems.org"
-
-# Gemspec as base dependency set
-gemspec path: __dir__ + '/..'
-
-gem 'sqlite3', '~> 1.3.6'
-gem 'activejob', "~> 5.0.0"
-gem 'activerecord', "~> 5.0.0"