sentry-good_job 6.2.1 → 7.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b4bbd328429c6b8c41e160e50472df58bcdf9e1686f1d7e5f0e641cf4a0f7d0b
-  data.tar.gz: 7ac0b2165cde063b7e0940e9ef121cb1314eb3c36b27554303c93cb7511ddce8
+  metadata.gz: 6614ae4fcea329de36cf94c4714ecea1e2d04a52cc9d1b6ce858191d4b64d215
+  data.tar.gz: b6b295bfb43f089ede9b08d877e7a15704a9304dc1effe8803c10f07356b26a4
 SHA512:
-  metadata.gz: 41ede499759ad573a7db70861480f9f724b8aa0918dbefc28d6799099e4afad7ca14fd061f8ecd87376f86051b0c6ba0ca6bbe3465c7ed78e7d47381719aba27
-  data.tar.gz: a3f15723bd45b30663df12f9ac9a0e1c9ee8f5702bb7a88a8f18cf70f4c11366a6a734cadb82ad60b11a3ac55408d77e44294b766454bb0afd925fc59ce9f840
+  metadata.gz: 8bd54198cb499fd5015958fd443a8371b1d2e65c383622a34c4ac44d318c33f063a948fae1bc08673b275d7fb00767c23e2144e7e9aa32bed83c76497f25f801
+  data.tar.gz: a903b8e7f34e2517a803477a5047cca172173670350ce4b4b67610c4bd1c6a1f904a68c58914b7e93582bfb0b2ba4dea13af8447d6436bf50fa21c9caabb3be3

data/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 7.0.0 (2026-09-07)
+
+- BREAKING: Require sentry-ruby 7 (`>= 7.0`, `< 8.0`)
+- Skip nested enqueue span when sentry-rails already records it
+- Collect job arguments through `config.data_collection.queues`
+
 ## 6.2.1
 
 - Relax dependencies to allow all current versions of sentry-ruby and good_job

data/CODE_OF_CONDUCT.md

@@ -1,37 +1,26 @@
 # Code of Conduct
 
-## Our Pledge
+## Pledge
 
-We pledge to make participation in our community a harassment-free experience for everyone. We operate on principles of mutual respect, privacy, and authentic engagement. We value substantive contributions and clarity on intentions.
+Participation is a harassment-free experience. Treat each other with respect. Keep private context private.
 
-## Our Standards
+## Expected behavior
 
-Examples of behavior that contributes to a positive environment include:
+- Engage with genuine curiosity. Admit uncertainty.
+- Own every line you submit, including generated code.
+- Correct errors politely.
+- Use language that welcomes people and respects identity and privacy.
 
-* **Authenticity:** Engaging with genuine curiosity and admitting uncertainty rather than feigning knowledge.
+## Unacceptable behavior
 
-* **Responsible Innovation:** Taking full responsibility for any content or code contributed, whether manually written or generated by automation tools.
+- Harassment, trolling, or insulting comments, public or private.
+- Using jargon or volume, including automated spam, to silence others.
+- Sharing others' data or personal context without permission.
 
-* **Gentle Correction:** Responding politely to errors. We view mistakes as opportunities for learning, provided they are addressed with humility.
+## Automation
 
-* **Inclusive Language:** Using language that welcomes diverse perspectives and respects the privacy and identity of all participants.
-
-Examples of unacceptable behavior include:
-
-* **Harassment:** Public or private harassment, trolling, or insulting comments.
-
-* **Weaponized Complexity:** Using jargon or overwhelming volume (including automated spam) to silence others.
-
-* **Publishing Private Information:** Sharing others' data or personal context without explicit permission.
-
-## Artificial Intelligence & Automation
-
-In accordance with our commitment to **Collective Awareness**:
-
-* Contributors are responsible for the accuracy and security of any AI-generated artifacts they submit.
-
-* "The AI wrote it" is not a valid excuse for introducing bugs, security vulnerabilities, or bias.
+You remain responsible for bugs, security holes, and bias in generated artifacts you submit.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact@kiskolabs.com. All complaints will be reviewed and investigated promptly and fairly.
+Report abusive or harassing behavior to contact@kiskolabs.com. Reports are reviewed and investigated.

data/CONTRIBUTING.md

@@ -1,35 +1,23 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing. We value **learning over perfection** but require **rigor and responsibility**.
+## Automation authorship
 
-## The Golden Rule of Automation
+You may use AI and automation tools. You remain the author of every line you submit: review, debug, and understand the change.
 
-We welcome the use of AI and automation tools to reduce toil, but you must strictly adhere to the following:
+Keep pull requests small enough to review. Annotate non-obvious logic.
 
-1.  **You are the Author:** You act as the responsible agent for any code you submit. You must review, debug, and understand every line.
+Never send project secrets or private context to public models.
 
-2.  **Manage Cognitive Load:** Do not submit massive, unreviewed automated dumps. Respect the reviewers' time by annotating complex logic.
+## How to contribute
 
-3.  **Security:** Never feed project secrets or private context into public AI models.
+### Reporting issues
 
-## How to Contribute
+Verify the facts before filing. Use issue templates for goals, constraints, and reproduction steps.
 
-### 1. Reporting Issues
+### Pull requests
 
-* **Verify Accuracy:** Before posting, verify your information. Avoid generalizations.
+Keep one pull request to one goal. Explain why the change is needed. Run smoke tests and regression checks locally before opening the request.
 
-* **Use Structured Inputs:** Use our Issue Templates to provide clear goals, constraints, and reproduction steps. This helps us understand the context immediately.
+### Review
 
-### 2. Pull Request Process
-
-* **Scope:** Keep PRs focused on a single goal.
-
-* **Context:** Explain *why* the change is necessary. Transparency builds trust.
-
-* **Testing:** Run all smoke tests and regression checks locally. We prioritize "Safety First."
-
-### 3. Review Process
-
-* We encourage **productive friction**. Expect questions about your approach.
-
-* If a reviewer suggests a change, view it as **mutual aid**, not criticism.
+Reviewers will ask about approach and trade-offs. Treat suggested changes as part of the work.

data/GOVERNANCE.md

@@ -1,31 +1,25 @@
 # Project Governance
 
-## Overview
-
-This project balances **individual autonomy** with **collective coordination**. We aim for a workflow that supports rapid iteration while maintaining strict guardrails for safety and architectural integrity.
-
 ## Roles
 
 ### Contributors
 
-Anyone who submits code, documentation, or participates in discussions. Contributors are expected to exercise **Direct Action**—taking ownership of problems they identify—while adhering to our quality standards.
-
-### Maintainers (Human Oversight)
-
-Maintainers are responsible for:
+Anyone who submits code, documentation, or participates in discussions. Contributors take ownership of problems they identify and follow the project's quality standards.
 
-1.  **Strategic Judgment:** Defining scope and architectural direction.
+### Maintainers
 
-2.  **Review:** verifying that contributions (human or automated) meet security and logic standards.
+Maintainers:
 
-3.  **Consensus Building:** Facilitating decisions when the community is divided.
+1. Set scope and architectural direction.
+2. Review contributions (human or automated) against security and logic standards.
+3. Decide when the community is divided.
 
-## Decision Making process
+## Decision making
 
-### Lazy Consensus
+### Lazy consensus
 
-For most routine changes, we operate on "lazy consensus." If a proposal is made and no objections are raised within two weeks, it is considered approved.
+For routine changes, a proposal that draws no objection within two weeks is approved.
 
-### Strategic Alignment
+### Maintainer approval
 
-Major architectural changes, high-risk automation integrations, or changes that affect business logic require explicit approval from the Maintainers. We prioritize **substance over performance**—a change must solve a real problem, not just appear polished.
+Major architectural changes, high-risk automation integrations, or changes that affect business logic need explicit maintainer approval. A change must solve a real problem.

data/README.md

@@ -11,8 +11,8 @@
 
 [![Gem Version](https://img.shields.io/gem/v/sentry-good_job.svg)](https://rubygems.org/gems/sentry-good_job)
 [![Build Status](https://github.com/amkisko/sentry-good_job/actions/workflows/test.yml/badge.svg?branch=main)](https://github.com/amkisko/sentry-good_job/actions/workflows/test.yml)
-[![Coverage Status](https://img.shields.io/codecov/c/github/amkisko/sentry-good_job/main?logo=codecov)](https://app.codecov.io/gh/amkisko/sentry-good_job)
-[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=amkisko_sentry-good_job&metric=alert_status)](https://sonarcloud.io/summary/new_code?id=amkisko_sentry-good_job)
+[![Coverage Status](https://img.shields.io/codecov/c/github/amkisko/sentry-good_job/main?logo=codecov)](https://app.codecov.io/github/amkisko/sentry-good_job)
+[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=amkisko_sentry-good_job&metric=alert_status)](https://sonarcloud.io/project/overview?id=amkisko_sentry-good_job)
 [![Gem](https://img.shields.io/gem/dt/sentry-good_job.svg)](https://rubygems.org/gems/sentry-good_job/)
 [![SemVer](https://api.dependabot.com/badges/compatibility_score?dependency-name=sentry-good_job&package-manager=bundler&version-scheme=semver)](https://dependabot.com/compatibility-score.html?dependency-name=sentry-good_job&package-manager=bundler&version-scheme=semver)
 
@@ -53,7 +53,7 @@ Sentry.init do |config|
   
   # ActiveJob configuration (handled by sentry-rails)
   config.rails.active_job_report_on_retry_error = false
-  config.send_default_pii = false
+  config.data_collection.queues = false
 
   # Optional: Configure logging for debugging
   config.sdk_logger = Rails.logger
@@ -69,7 +69,7 @@ end
 #### ActiveJob Options (handled by sentry-rails)
 
 - `config.rails.active_job_report_on_retry_error` (default: `false`): Only report errors after all retry attempts are exhausted
-- `config.send_default_pii` (default: `false`): Include job arguments in error context (be careful with sensitive data)
+- `config.data_collection.queues` (default: `true`): Include job arguments in error context (be careful with sensitive data)
 - `config.sdk_logger` (default: `nil`): Configure the SDK logger for custom logging needs (general Sentry configuration)
 
 **Note**: The Good Job integration now leverages sentry-rails for core ActiveJob functionality, including trace propagation, user context preservation, and error reporting. This provides better integration and reduces duplication.
@@ -183,20 +183,32 @@ The integration automatically adds relevant context to error reports:
 - Execution count (GoodJob-specific)
 - Priority (GoodJob-specific)
 - Enqueued and scheduled timestamps
-- Job arguments (if enabled via send_default_pii)
+- Job arguments (if enabled via `config.data_collection.queues`)
 - Latency metrics (GoodJob-specific)
 
 ## Compatibility
 
-- Ruby 2.4+
-- Rails 5.2+
-- Good Job 4.x
-- Sentry Ruby SDK 6.x
+- Ruby 3.4+
+- Good Job 3.x and 4.x
+- Sentry Ruby SDK 7.x
 
 ## Contributing
 
 We welcome contributions! Please see our [contributing guidelines](./CONTRIBUTING.md) for details.
 
+## Links
+
+- [GitHub](https://github.com/amkisko/sentry-good_job)
+- [GitLab](https://gitlab.com/amkisko/sentry-good_job)
+- [RubyGems](https://rubygems.org/gems/sentry-good_job)
+- [Versions Atom](https://rubygems.org/gems/sentry-good_job/versions.atom) (feed id `10143542922948`)
+- [libraries.io](https://libraries.io/rubygems/sentry-good_job)
+- [Deps.dev](https://deps.dev/rubygems/sentry-good_job)
+- [SonarCloud](https://sonarcloud.io/project/overview?id=amkisko_sentry-good_job)
+- [Snyk](https://snyk.io/test/github/amkisko/sentry-good_job)
+- [Codecov](https://app.codecov.io/github/amkisko/sentry-good_job)
+- [OpenSSF Scorecard](https://scorecard.dev/viewer/?uri=github.com/amkisko/sentry-good_job)
+
 ## License
 
 This project is licensed under the MIT License. See the [LICENSE](LICENSE.txt) file for details.

data/SECURITY.md

@@ -2,27 +2,24 @@
 
 ## Reporting a Vulnerability
 
-**Do NOT** open a public GitHub issue for security vulnerabilities.
+Email security details to: security@kiskolabs.com
 
-Email security details to: **security@kiskolabs.com**
-
-Include: description, steps to reproduce, potential impact, and suggested fix (if available).
+Send the report only to that address. Include description, steps to reproduce, potential impact, and a suggested fix when you have one.
 
 ### Response Timeline
 
-- We will acknowledge receipt of your report
-- We will provide an initial assessment
-- We will keep you informed of our progress and resolution timeline
+- We will acknowledge receipt of your report.
+- We will provide an initial assessment.
+- We will keep you informed of our progress and resolution timeline.
 
 ### Disclosure Policy
 
-- We will work with you to understand and resolve the issue
-- We will credit you for the discovery (unless you prefer to remain anonymous)
-- We will publish a security advisory after the vulnerability is patched
-- We will coordinate public disclosure with you
+- We will work with you to understand and resolve the issue.
+- We will credit you for the discovery unless you prefer to remain anonymous.
+- We will publish a security advisory after the vulnerability is patched.
+- We will coordinate public disclosure with you.
 
 ## Automation Security
 
-* **Context Isolation:** It is strictly forbidden to include production credentials, API keys, or Personally Identifiable Information (PII) in prompts sent to third-party LLMs or automation services.
-
-* **Supply Chain:** All automated dependencies must be verified.
+- Keep production credentials, API keys, and personal data out of prompts sent to third-party models or automation services.
+- Verify automated dependencies.

data/bin/polyrun

@@ -0,0 +1,108 @@
+#!/usr/bin/env bash
+# Delegates to `bundle exec polyrun` with repo config.
+# - No args → same as `polyrun` with no subcommand (auto parallel RSpec from polyrun.yml / spec/**/*_spec.rb).
+# - Path-like argv (spec files, globs, dirs) → polyrun implicit parallel (path-only argv).
+# - Named subcommands (plan, config, parallel-rspec, ci-shard-rspec, …) → pass through.
+# - Otherwise (RSpec flags first, e.g. --format) → `start --workers N -- bundle exec rspec "$@"`.
+# Globals: -c/--config, -v/--verbose, -h/--help, --help (same as bundle exec polyrun).
+# Workers: POLYRUN_WORKERS (default 5, max 10, min 1) — read by polyrun run-shards/start.
+set -eo pipefail
+ROOT="$(cd "$(dirname "$0")/.." && pwd)"
+cd "$ROOT"
+
+W="${POLYRUN_WORKERS:-5}"
+case "$W" in ''|*[!0-9]*) W=5 ;; esac
+if [ "$W" -gt 10 ]; then W=10; fi
+if [ "$W" -lt 1 ]; then W=1; fi
+
+CONFIG="${POLYRUN_CONFIG:-polyrun.yml}"
+polyrun_prefix=()
+have_config=0
+
+while [ $# -gt 0 ]; do
+  case "$1" in
+    -c|--config)
+      polyrun_prefix+=("$1" "$2")
+      CONFIG="$2"
+      have_config=1
+      shift 2
+      ;;
+    -v|--verbose)
+      polyrun_prefix+=("$1")
+      shift
+      ;;
+    -h|--help)
+      if [ "$have_config" -eq 0 ]; then
+        exec bundle exec polyrun "${polyrun_prefix[@]}" -c "$CONFIG" -h
+      else
+        exec bundle exec polyrun "${polyrun_prefix[@]}" -h
+      fi
+      ;;
+    *)
+      break
+      ;;
+  esac
+done
+
+if [ "${1:-}" = "--version" ]; then
+  if [ "$have_config" -eq 0 ]; then
+    exec bundle exec polyrun "${polyrun_prefix[@]}" -c "$CONFIG" version
+  else
+    exec bundle exec polyrun "${polyrun_prefix[@]}" version
+  fi
+fi
+
+is_polyrun_command() {
+  case "$1" in
+    plan|prepare|merge-coverage|report-coverage|report-junit|report-timing|env|config|merge-timing|\
+    db:setup-template|db:setup-shard|db:clone-shards|run-shards|parallel-rspec|start|build-paths|\
+    ci-shard-run|ci-shard-rspec|init|queue|quick|help|version)
+      return 0 ;;
+    *)
+      return 1 ;;
+  esac
+}
+
+# True if argv should use polyrun implicit path parallel (any path-like token).
+implicit_path_in_argv() {
+  for a in "$@"; do
+    case "$a" in
+      -*) [ "$a" = "-" ] || continue ;;
+    esac
+    case "$a" in
+      *.rb|spec/*|test/*|./|/*|*[\*\?[]*) return 0 ;;
+    esac
+    [ -e "$a" ] && return 0
+  done
+  return 1
+}
+
+run_polyrun() {
+  if [ "$have_config" -eq 0 ]; then
+    exec bundle exec polyrun "${polyrun_prefix[@]}" -c "$CONFIG" "$@"
+  else
+    exec bundle exec polyrun "${polyrun_prefix[@]}" "$@"
+  fi
+}
+
+exec_parallel_rspec() {
+  if [ "$have_config" -eq 0 ]; then
+    exec bundle exec polyrun "${polyrun_prefix[@]}" -c "$CONFIG" start --workers "$W" -- bundle exec rspec "$@"
+  else
+    exec bundle exec polyrun "${polyrun_prefix[@]}" start --workers "$W" -- bundle exec rspec "$@"
+  fi
+}
+
+if [ $# -eq 0 ]; then
+  run_polyrun
+fi
+
+if is_polyrun_command "$1"; then
+  run_polyrun "$@"
+fi
+
+if implicit_path_in_argv "$@"; then
+  run_polyrun "$@"
+fi
+
+exec_parallel_rspec "$@"

data/lib/sentry/good_job/active_job_extensions.rb

@@ -80,7 +80,6 @@ module Sentry
           # Ensure the sentry-rails integration is properly set up
           # by checking if the ActiveJobExtensions module is already included
           if defined?(::Sentry::Rails::ActiveJobExtensions) && !ancestors.include?(::Sentry::Rails::ActiveJobExtensions)
-            require "sentry/rails/active_job"
             prepend ::Sentry::Rails::ActiveJobExtensions
           end
         end
@@ -93,11 +92,14 @@ module Sentry
         extend ActiveSupport::Concern
 
         included do
-          # Set up around_enqueue hook for GoodJob-specific enqueue span
           around_enqueue do |job, block|
             next block.call unless ::Sentry.initialized?
 
-            # Create enqueue span with GoodJob-specific data
+            if defined?(::Sentry::Rails::ActiveJobExtensions::SentryReporter) &&
+                ::Sentry::Rails::ActiveJobExtensions::SentryReporter.respond_to?(:record_producer_span)
+              next block.call
+            end
+
             ::Sentry.with_child_span(op: "queue.publish", description: job.class.name) do |span|
               _sentry_set_span_data(span, job)
               block.call

data/lib/sentry/good_job/context_helpers.rb

@@ -16,8 +16,7 @@ module Sentry
           priority: job.respond_to?(:priority) ? job.priority : nil
         }
 
-        # Note: Job arguments are handled by sentry-rails via send_default_pii configuration
-        # This is controlled by Sentry.configuration.send_default_pii, not GoodJob-specific config
+        # Job arguments stay on sentry-rails via config.data_collection.queues
 
         # Merge with base context
         base_context.merge(good_job: good_job_context)

data/lib/sentry/good_job/version.rb

@@ -2,6 +2,6 @@
 
 module Sentry
   module GoodJob
-    VERSION = "6.2.1"
+    VERSION = "7.0.0"
   end
 end

data/sentry-good_job.gemspec

@@ -12,7 +12,7 @@ Gem::Specification.new do |spec|
   spec.license = "MIT"
 
   spec.platform = Gem::Platform::RUBY
-  spec.required_ruby_version = ">= 2.4"
+  spec.required_ruby_version = ">= 3.4"
   spec.extra_rdoc_files = ["README.md", "LICENSE.txt"]
   spec.files = Dir.chdir(File.expand_path(__dir__)) do
     Dir[
@@ -40,10 +40,21 @@ Gem::Specification.new do |spec|
     "documentation_uri" => "http://www.rubydoc.info/gems/#{spec.name}/#{spec.version}"
   }
 
-  spec.bindir = "exe"
-  spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
 
-  spec.add_dependency "sentry-ruby", ">= 6.0", "< 7.0"
+  spec.add_dependency "sentry-ruby", ">= 7.0", "< 8.0"
   spec.add_dependency "good_job", ">= 3.0", "< 5.0"
+
+  spec.add_development_dependency "appraisal", "~> 2"
+  spec.add_development_dependency "bundler", ">= 2"
+  spec.add_development_dependency "polyrun", ">= 2.2.0"
+  spec.add_development_dependency "rake", "~> 13.0"
+  spec.add_development_dependency "rspec", "~> 3"
+  spec.add_development_dependency "rspec_junit_formatter", "~> 0.6"
+  spec.add_development_dependency "rubocop-rspec", "~> 3.8"
+  spec.add_development_dependency "rubocop-thread_safety", "~> 0.7"
+  spec.add_development_dependency "standard", "~> 1.52"
+  spec.add_development_dependency "standard-custom", "~> 1.0"
+  spec.add_development_dependency "standard-performance", "~> 1.8"
+  spec.add_development_dependency "standard-rspec", "~> 0.3"
 end

metadata

@@ -1,12 +1,12 @@
 --- !ruby/object:Gem::Specification
 name: sentry-good_job
 version: !ruby/object:Gem::Version
-  version: 6.2.1
+  version: 7.0.0
 platform: ruby
 authors:
 - Sentry Team
 - Andrei Makarov
-bindir: exe
+bindir: bin
 cert_chain: []
 date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
@@ -16,20 +16,20 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '6.0'
+        version: '7.0'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '7.0'
+        version: '8.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '6.0'
+        version: '7.0'
     - - "<"
       - !ruby/object:Gem::Version
-        version: '7.0'
+        version: '8.0'
 - !ruby/object:Gem::Dependency
   name: good_job
   requirement: !ruby/object:Gem::Requirement
@@ -50,6 +50,174 @@ dependencies:
     - - "<"
       - !ruby/object:Gem::Version
         version: '5.0'
+- !ruby/object:Gem::Dependency
+  name: appraisal
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2'
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '2'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '2'
+- !ruby/object:Gem::Dependency
+  name: polyrun
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.2.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.2.0
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '13.0'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3'
+- !ruby/object:Gem::Dependency
+  name: rspec_junit_formatter
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.6'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.6'
+- !ruby/object:Gem::Dependency
+  name: rubocop-rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.8'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.8'
+- !ruby/object:Gem::Dependency
+  name: rubocop-thread_safety
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.7'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.7'
+- !ruby/object:Gem::Dependency
+  name: standard
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.52'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.52'
+- !ruby/object:Gem::Dependency
+  name: standard-custom
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+- !ruby/object:Gem::Dependency
+  name: standard-performance
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.8'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.8'
+- !ruby/object:Gem::Dependency
+  name: standard-rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.3'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.3'
 description: Adds Sentry instrumentation, context helpers, and cron monitoring support
   to GoodJob-backed ActiveJob workloads.
 email: contact@kiskolabs.com
@@ -67,6 +235,7 @@ files:
 - README.md
 - SECURITY.md
 - bin/console
+- bin/polyrun
 - bin/setup
 - lib/sentry-good_job.rb
 - lib/sentry/good_job.rb
@@ -84,7 +253,7 @@ metadata:
   source_code_uri: https://github.com/amkisko/sentry-good_job/tree/main
   changelog_uri: https://github.com/amkisko/sentry-good_job/blob/main/CHANGELOG.md
   bug_tracker_uri: https://github.com/amkisko/sentry-good_job/issues
-  documentation_uri: http://www.rubydoc.info/gems/sentry-good_job/6.2.1
+  documentation_uri: http://www.rubydoc.info/gems/sentry-good_job/7.0.0
 rdoc_options: []
 require_paths:
 - lib
@@ -92,14 +261,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '2.4'
+      version: '3.4'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.6.9
+rubygems_version: 4.0.3
 specification_version: 4
 summary: GoodJob integration for the Sentry error logger
 test_files: []