cloudtasker 0.14.rc1 → 0.14.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ca57b71a4e3552693d0a64720f423bf7ff1168d5078018a0177c65f09ad681d8
-  data.tar.gz: f886fe29dec2c4ce12286b3e5af843a02e4ea426fbef6db0d2cfcb300418ea34
+  metadata.gz: 5574bda23d3a128aeb279e7fae03d982cce7788d407d8c627508cb387a1d4d30
+  data.tar.gz: 24cf8b37d065ce49221d3e118f5579ee8495a09f4ee9be05079536c5c1b497e4
 SHA512:
-  metadata.gz: 8312536629168911d321d0630a126f0671eb9e7e6bdb51c86f675ac159d7294f8a1a87bf89d4b4948dae23f4e9411e5673718bc6edac8b73d10592f1a8527744
-  data.tar.gz: a6aeb550354e06413bcd21e3ce47f0b136184c236b4c908104ee1ae51412f4fbcad6cdc3ab392bf991046fe9a1747f32770ca1a0f8d3bddf35dd54813f8b646e
+  metadata.gz: f502740061baf6484214dcd23531521e253bbae1194af88b49623734976fd82b0e0e2762a3f4cc5d1585fd8229f6ae4c1262eadeff82a5e3dc0f1c0154e0880f
+  data.tar.gz: 4b148a1b8cf1b37c02918cf0d4e442e30e34383578538821815453d53656d8f26c873a6b31914cacde63fba9afddbedb3d263fcd959bbfcd09354f2984e67382

data/Appraisals

@@ -54,6 +54,11 @@ if RUBY_VERSION >= '2.7'
     gem 'rails', '~> 7.0.0'
     gem 'rspec-rails'
   end
+
+  appraise 'rails_7.1' do
+    gem 'rails', '~> 7.1'
+    gem 'rspec-rails'
+  end
 end
 
 appraise 'semantic_logger_3.4' do

data/CHANGELOG.md

@@ -1,8 +1,8 @@
 # Changelog
 
-## [v0.14.rc1](https://github.com/keypup-io/cloudtasker/tree/v0.14.rc1) (2024-09-22)
+## [v0.14.0](https://github.com/keypup-io/cloudtasker/tree/v0.14.0) (2025-02-11)
 
-[Full Changelog](https://github.com/keypup-io/cloudtasker/compare/v0.13.2...v0.14.rc1)
+[Full Changelog](https://github.com/keypup-io/cloudtasker/compare/v0.13.2...v0.14.0)
 
 **Improvements:**
 - Authentication: To support OIDC and regular Cloudtasker authentication, we moved the Cloudtasker Authentication header from `Authorization` to `X-Cloudtasker-Authorization`. Backward compatibility is maintained for existing jobs.

data/README.md

@@ -1,6 +1,4 @@
-![Build Status](https://github.com/keypup-io/cloudtasker/workflows/Test/badge.svg) [![Gem Version](https://badge.fury.io/rb/cloudtasker.svg)](https://badge.fury.io/rb/cloudtasker)
-
-🚀🚀🚀 Cloudtasker 0.14 release candidate (`v0.14.rc1`) is out and it's quite big ([Changelog](https://github.com/keypup-io/cloudtasker/blob/master/CHANGELOG.md)). Any help testing this release is welcome, and feel free to open issues if you spot any regression.
+![Build Status 3.x](https://github.com/keypup-io/cloudtasker/actions/workflows/test_ruby_3.x.yml/badge.svg) [![Gem Version](https://badge.fury.io/rb/cloudtasker.svg)](https://badge.fury.io/rb/cloudtasker)
 
 # Cloudtasker
 
@@ -428,7 +426,7 @@ Cloudtasker.configure do |config|
   # See https://cloud.google.com/tasks/docs/creating-http-target-tasks#sa for more information on
   # setting up service accounts for use with Cloud Tasks.
   #
-  # Supported since: v0.14.rc1
+  # Supported since: v0.14.0
   #
   # Default: nil 
   #
@@ -698,7 +696,7 @@ end
 See the [Cloudtasker::Worker class](lib/cloudtasker/worker.rb) for more information on attributes available to be logged in your `log_context_processor` proc.
 
 ### Truncating log arguments
-**Supported since**: `v0.14.rc1`  
+**Supported since**: `v0.14.0`  
 
 By default Cloudtasker does not log job arguments as arguments can contain sensitive data and generate voluminous logs, which may lead to noticeable costs with your log provider (e.g. GCP Logging). Also some providers (e.g. GCP Logging) will automatically truncate log entries that are too big and reduce their searchability.
 
@@ -834,7 +832,7 @@ By default jobs are retried 25 times - using an exponential backoff - before bei
 
 Note that the number of retries set on your Cloud Task queue should be many times higher than the number of retries configured in Cloudtasker because Cloud Task also includes failures to connect to your application. Ideally set the number of retries to `unlimited` in Cloud Tasks.
 
-**Note**: Versions prior to `v0.14.rc1` use the `X-CloudTasks-TaskRetryCount` header for retries instead of the `X-CloudTasks-TaskExecutionCount` header to detect the number of retries, because there a previous bug on the GCP side which made the `X-CloudTasks-TaskExecutionCount` stay at zero instead of increasing on successive executions. Versions prior to `v0.14.rc1` count any failure as failure, including failures due to the backend being unavailable (`HTTP 503`). Versions `v0.14.rc1` and later only count application failure (`HTTP 4xx`) as failure for retry purpose.
+**Note**: Versions prior to `v0.14.0` use the `X-CloudTasks-TaskRetryCount` header for retries instead of the `X-CloudTasks-TaskExecutionCount` header to detect the number of retries, because there a previous bug on the GCP side which made the `X-CloudTasks-TaskExecutionCount` stay at zero instead of increasing on successive executions. Versions prior to `v0.14.0` count any failure as failure, including failures due to the backend being unavailable (`HTTP 503`). Versions `v0.14.0` and later only count application failure (`HTTP 4xx`) as failure for retry purpose.
 
 E.g. Set max number of retries globally via the cloudtasker initializer.
 ```ruby
@@ -891,7 +889,7 @@ end
 ```
 
 ### Conditional reenqueues using retry errors
-**Supported since**: `v0.14.rc1`  
+**Supported since**: `v0.14.0`  
 
 If your worker is waiting for some precondition to occur and you want to re-enqueue it until the condition has been met, you can raise a `Cloudtasker::RetryWorkerError`. This special error will fail your job **without logging an error** while still increasing the number of retries.
 
@@ -1005,7 +1003,7 @@ Each testing mode accepts a block argument to temporarily switch to it:
 Cloudtasker::Testing.fake!
 
 # Enable inline! mode temporarily for a given test
-Cloudtasker.inline! do
+Cloudtasker::Testing.inline! do
    MyWorker.perform_async(1,2)
 end
 ```

data/app/controllers/cloudtasker/worker_controller.rb

@@ -94,7 +94,7 @@ module Cloudtasker
         # Verify content signature
         Authenticator.verify_signature!(signature, json_payload)
       else
-        # Get authorization token from custom header (since v0.14.rc1) or fallback to
+        # Get authorization token from custom header (since v0.14.0) or fallback to
         # former authorization header (jobs enqueued by v0.13 and below)
         bearer_token = request.headers[Cloudtasker::Config::CT_AUTHORIZATION_HEADER].to_s.split.last ||
                        request.headers[Cloudtasker::Config::OIDC_AUTHORIZATION_HEADER].to_s.split.last

data/docs/STORABLE_JOBS.md

@@ -1,6 +1,6 @@
 # Cloudtasker Storable Jobs
 
-**Supported since**: `v0.14.rc1`  
+**Supported since**: `v0.14.0`  
 **Note**: this extension requires redis
 
 The Cloudtasker storage extension allows you to park jobs in a specific garage lane and enqueue (pull) them when specific conditions have been met.

data/gemfiles/rails_7.1.gemfile

@@ -0,0 +1,18 @@
+# This file was generated by Appraisal
+
+source "https://rubygems.org"
+
+gem "appraisal", github: "thoughtbot/appraisal"
+gem "bundler", "~> 2.0"
+gem "rake", ">= 12.3.3"
+gem "rspec", "~> 3.0"
+gem "rspec-json_expectations", "~> 2.2"
+gem "rubocop", "~> 1.64.1"
+gem "rubocop-rspec", "~> 3.0.1"
+gem "semantic_logger"
+gem "timecop"
+gem "webmock"
+gem "rails", "~> 7.1"
+gem "rspec-rails"
+
+gemspec path: "../"

data/lib/cloudtasker/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Cloudtasker
-  VERSION = '0.14.rc1'
+  VERSION = '0.14.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cloudtasker
 version: !ruby/object:Gem::Version
-  version: 0.14.rc1
+  version: 0.14.0
 platform: ruby
 authors:
 - Arnaud Lachaume
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2024-09-22 00:00:00.000000000 Z
+date: 2025-02-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -153,6 +153,7 @@ files:
 - gemfiles/rails_6.0.gemfile
 - gemfiles/rails_6.1.gemfile
 - gemfiles/rails_7.0.gemfile
+- gemfiles/rails_7.1.gemfile
 - gemfiles/semantic_logger_3.4.gemfile
 - gemfiles/semantic_logger_4.6.gemfile
 - gemfiles/semantic_logger_4.7.0.gemfile