transaction_guard 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 81a99a71dbadc26e6a02101a9c4200d9ebd4a79b6417caf62613005ab9872a33
+  data.tar.gz: 940ff5a7174f7d5b6919dbac739a7d6e0e9d488987197e584f78318acf0f5b8a
+SHA512:
+  metadata.gz: 9ec48718d32eac1488296881b2e2f0c2acee3ebdb2002ba2f616871e4dfb0b30ecbfda144c9e964e636d6577c11c91c54e0b051f1711b964ff7f58dac0ff997e
+  data.tar.gz: '092340c5d26c0b1d7fb388569afcfcf7740bc17cad3debbccf247805c7b9ab72088575160f5b0faac2600eaa684e149dd2f112645126d002138d46f5cccb0c1e'

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,20 @@
+AllCops:
+  TargetRubyVersion: 3.1
+  NewCops: enable
+  SuggestExtensions: false
+  Exclude:
+    - "vendor/**/*"
+    - "tmp/**/*"
+    - "bin/setup"
+    - "sig/**/*"
+
+Metrics/BlockLength:
+  Exclude:
+    - "spec/**/*"
+    - "*.gemspec"
+
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  EnforcedStyle: double_quotes

data/CHANGELOG.md

@@ -0,0 +1,12 @@
+## [Unreleased]
+
+## [0.1.0] - 2026-09-18
+
+### Added
+
+- Detect `Net::HTTP` requests inside ActiveRecord transactions
+- Detect ActionMailer `deliver_now` / `deliver_later` inside transactions
+- Detect ActiveJob `perform_later` / `perform_now` inside transactions
+- Configuration modes: `:warn` (default), `:raise`, and `:off`
+- Rails Railtie with development/test `:warn` and production `:off` defaults
+- Caller location in warning and error messages

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+yashikavijay2799@gmail.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# Contributing to TransactionGuard
+
+Thanks for helping improve TransactionGuard.
+
+## How to contribute
+
+`master` is protected. Direct pushes are not accepted.
+
+1. **Fork** the repository on GitHub.
+2. **Clone your fork** and create a branch from `master`.
+3. Make your changes, then open a **pull request** against `master` on
+   [yashika279/transaction_guard](https://github.com/yashika279/transaction_guard).
+
+```bash
+git clone https://github.com/<your-username>/transaction_guard.git
+cd transaction_guard
+git remote add upstream https://github.com/yashika279/transaction_guard.git
+git checkout -b my-change
+bundle install
+```
+
+Keep your branch up to date before opening the PR:
+
+```bash
+git fetch upstream
+git rebase upstream/master
+```
+
+## Feedback and issues
+
+Use [GitHub Issues](https://github.com/yashika279/transaction_guard/issues) for:
+
+* Bug reports
+* Feature ideas
+* Questions and general feedback
+
+Prefer the issue templates when they fit. Include:
+
+1. Ruby / Rails / ActiveRecord versions
+2. TransactionGuard mode (`:warn`, `:raise`, or `:off`)
+3. A minimal reproduction if possible
+
+Security vulnerabilities should be reported privately — see [SECURITY.md](SECURITY.md).
+
+## Checks before opening a PR
+
+```bash
+bundle exec rspec
+bundle exec rubocop
+```
+
+CI must pass on your pull request before it can be merged.
+
+## Guidelines
+
+- Keep the public API small and focused on detecting side effects inside ActiveRecord transactions.
+- Prefer optional integrations (load when the library is present) over hard runtime dependencies.
+- Add or update specs for behavior changes.
+- Update `CHANGELOG.md` under `[Unreleased]` when relevant.
+- Be respectful and follow the [Code of Conduct](CODE_OF_CONDUCT.md).

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2026 Yashika
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,278 @@
+# TransactionGuard
+
+TransactionGuard detects external side effects performed inside ActiveRecord transactions.
+
+Database transactions can roll back database changes, but they cannot automatically roll back operations such as:
+
+* HTTP requests
+* Email delivery
+* Background job enqueueing
+
+For example:
+
+```ruby
+User.transaction do
+  user = User.create!(name: "Yashika")
+
+  SomeExternalApi.create_user(user)
+end
+```
+
+If the transaction later rolls back, the external API request cannot automatically be rolled back with it.
+
+TransactionGuard helps identify these situations during development and testing.
+
+## Installation
+
+Add the gem to your application's Gemfile:
+
+```ruby
+gem "transaction_guard"
+```
+
+Then run:
+
+```bash
+bundle install
+```
+
+For local development, you can use the gem directly from a local path:
+
+```ruby
+gem "transaction_guard", path: "../transaction_guard"
+```
+
+## Configuration
+
+TransactionGuard supports three modes:
+
+* `:warn` — report external side effects
+* `:raise` — raise an error when a side effect is detected
+* `:off` — disable detection
+
+The default mode is `:warn`.
+
+In Rails applications, the included Railtie sets:
+
+* `:warn` in development and test
+* `:off` in production
+
+Override this in an initializer:
+
+```ruby
+# config/initializers/transaction_guard.rb
+TransactionGuard.configure do |config|
+  config.mode = :warn
+end
+```
+
+### Warn mode
+
+This is the default:
+
+```ruby
+TransactionGuard.configure do |config|
+  config.mode = :warn
+end
+```
+
+When an external side effect is detected inside a transaction, TransactionGuard reports a warning including the operation and caller location.
+
+### Raise mode
+
+Use `:raise` when you want to prevent the transaction from continuing after an external side effect is detected:
+
+```ruby
+TransactionGuard.configure do |config|
+  config.mode = :raise
+end
+```
+
+An invalid configuration value raises an `ArgumentError`:
+
+```ruby
+TransactionGuard.configure do |config|
+  config.mode = :invalid
+end
+```
+
+### Off mode
+
+Detection can be disabled:
+
+```ruby
+TransactionGuard.configure do |config|
+  config.mode = :off
+end
+```
+
+## HTTP detection
+
+TransactionGuard detects HTTP requests made through `Net::HTTP` while an ActiveRecord transaction is open.
+
+Example:
+
+```ruby
+User.transaction do
+  Net::HTTP.get(URI("https://example.com"))
+end
+```
+
+TransactionGuard reports the external HTTP operation.
+
+The detector covers common `Net::HTTP` methods including:
+
+```ruby
+get
+post
+put
+patch
+delete
+head
+options
+```
+
+Clients that build on `Net::HTTP` (for example some Faraday adapters) may also be detected. Direct Faraday, HTTParty, httpx, and similar clients are not hooked in 0.1.0.
+
+## Email detection
+
+TransactionGuard detects email delivery performed inside an ActiveRecord transaction.
+
+For example:
+
+```ruby
+User.transaction do
+  user = User.create!
+
+  TestMailer.welcome(user).deliver_now
+end
+```
+
+It also detects:
+
+```ruby
+User.transaction do
+  TestMailer.welcome(user).deliver_later
+end
+```
+
+`deliver_later` is reported as an email side effect rather than generating an additional warning for the internal ActiveJob enqueue.
+
+## Background job detection
+
+TransactionGuard detects ActiveJob operations performed inside transactions.
+
+### Enqueueing a job
+
+```ruby
+User.transaction do
+  user = User.create!
+
+  WelcomeJob.perform_later(user.id)
+end
+```
+
+This is reported as a job enqueue operation.
+
+### Executing a job immediately
+
+```ruby
+User.transaction do
+  WelcomeJob.perform_now
+end
+```
+
+This is reported as job execution.
+
+Sidekiq, Resque, and other non-ActiveJob APIs are not detected in 0.1.0.
+
+## Why does this matter?
+
+Consider:
+
+```ruby
+User.transaction do
+  user = User.create!
+
+  WelcomeJob.perform_later(user.id)
+
+  raise ActiveRecord::Rollback
+end
+```
+
+The database record is rolled back, but the background job may already have been enqueued.
+
+The job could therefore execute with an ID that no longer exists.
+
+Similar problems can occur with HTTP requests and email delivery.
+
+## Recommended alternatives
+
+When an external side effect depends on a successful database transaction, consider moving the operation until after the transaction commits.
+
+For example:
+
+```ruby
+user = User.create!
+
+User.transaction do
+  user.update!(status: "active")
+end
+
+WelcomeJob.perform_later(user.id)
+```
+
+For more complex workflows, consider patterns such as:
+
+* `after_commit`
+* ActiveJob triggered after a successful commit
+* transactional outbox
+* reliable event publishing
+
+TransactionGuard does not automatically move, delay, retry, or otherwise modify external operations. It reports the potentially unsafe operation so the application can decide how to handle it.
+
+## Development
+
+Clone the repository and install dependencies:
+
+```bash
+git clone https://github.com/yashika279/transaction_guard.git
+cd transaction_guard
+bundle install
+```
+
+Run the test suite:
+
+```bash
+bundle exec rspec
+```
+
+Run RuboCop:
+
+```bash
+bundle exec rubocop
+```
+
+Build the gem locally:
+
+```bash
+bundle exec gem build transaction_guard.gemspec
+```
+
+## Contributing
+
+Bug reports, feature ideas, feedback, and pull requests are welcome.
+
+- Open an [issue](https://github.com/yashika279/transaction_guard/issues/new/choose) for bugs, features, or feedback.
+- `master` is protected — **fork the repo**, push your branch, and open a PR against `master`.
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for setup, the fork workflow, and the PR checklist.
+Please make sure tests and RuboCop pass before submitting a pull request.
+
+## Security
+
+See [SECURITY.md](SECURITY.md) for how to report vulnerabilities.
+
+## License
+
+TransactionGuard is available as open source under the MIT License.

data/Rakefile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+RuboCop::RakeTask.new
+
+task default: %i[spec rubocop]

data/SECURITY.md

@@ -0,0 +1,19 @@
+# Security Policy
+
+## Supported versions
+
+Security fixes are applied to the latest released version of TransactionGuard.
+
+## Reporting a vulnerability
+
+Please report security issues privately by emailing **yashikavijay2799@gmail.com**.
+
+Do not open a public GitHub issue for vulnerabilities until a fix is available.
+
+Include:
+
+- A description of the issue
+- Steps to reproduce
+- Impact assessment if known
+
+You should receive an acknowledgment within a few days.

data/lib/transaction_guard/configuration.rb

@@ -0,0 +1,24 @@
+# frozen_string_literal: true
+
+module TransactionGuard
+  # Stores TransactionGuard configuration.
+  class Configuration
+    MODES = %i[off warn raise].freeze
+
+    attr_reader :mode
+
+    def initialize
+      @mode = :warn
+    end
+
+    def mode=(value)
+      raise ArgumentError, "Invalid mode: #{value.inspect}" unless MODES.include?(value)
+
+      @mode = value
+    end
+
+    def enabled?
+      mode != :off
+    end
+  end
+end

data/lib/transaction_guard/detectors/http.rb

@@ -0,0 +1,56 @@
+# frozen_string_literal: true
+
+module TransactionGuard
+  module Detectors
+    # Detects HTTP requests made inside ActiveRecord transactions.
+    module HTTP
+      HTTP_METHODS = %i[
+        delete
+        get
+        head
+        options
+        patch
+        post
+        put
+      ].freeze
+
+      def request(...)
+        report_http_request("HTTP request") unless http_request_in_progress?
+
+        with_http_request { super }
+      end
+
+      HTTP_METHODS.each do |method|
+        define_method(method) do |*args, **kwargs, &block|
+          report_http_request("HTTP #{method.upcase}") unless http_request_in_progress?
+
+          with_http_request do
+            super(*args, **kwargs, &block)
+          end
+        end
+      end
+
+      private
+
+      def report_http_request(operation)
+        return unless TransactionGuard.configuration.enabled?
+        return unless TransactionGuard::Transaction.open?
+
+        TransactionGuard::Reporter.report(operation: operation)
+      end
+
+      def http_request_in_progress?
+        Thread.current[:transaction_guard_http_request]
+      end
+
+      def with_http_request
+        previous_state = Thread.current[:transaction_guard_http_request]
+        Thread.current[:transaction_guard_http_request] = true
+
+        yield
+      ensure
+        Thread.current[:transaction_guard_http_request] = previous_state
+      end
+    end
+  end
+end

data/lib/transaction_guard/detectors/job.rb

@@ -0,0 +1,32 @@
+# frozen_string_literal: true
+
+module TransactionGuard
+  module Detectors
+    # Detects background job operations inside ActiveRecord transactions.
+    module Job
+      def perform_later(...)
+        report_job("Job enqueue")
+        super
+      end
+
+      def perform_now(...)
+        report_job("Job execution")
+        super
+      end
+
+      private
+
+      def report_job(operation)
+        return if mail_delivery_in_progress?
+        return unless TransactionGuard.configuration.enabled?
+        return unless TransactionGuard::Transaction.open?
+
+        TransactionGuard::Reporter.report(operation: operation)
+      end
+
+      def mail_delivery_in_progress?
+        Thread.current[:transaction_guard_mail_delivery]
+      end
+    end
+  end
+end

data/lib/transaction_guard/detectors/mail.rb

@@ -0,0 +1,42 @@
+# frozen_string_literal: true
+
+module TransactionGuard
+  module Detectors
+    # Detects email delivery inside ActiveRecord transactions.
+    module Mail
+      def deliver_now(...)
+        report_email unless mail_delivery_in_progress?
+
+        with_mail_delivery { super }
+      end
+
+      def deliver_later(...)
+        report_email unless mail_delivery_in_progress?
+
+        with_mail_delivery { super }
+      end
+
+      private
+
+      def report_email
+        return unless TransactionGuard.configuration.enabled?
+        return unless TransactionGuard::Transaction.open?
+
+        TransactionGuard::Reporter.report(operation: "Email delivery")
+      end
+
+      def mail_delivery_in_progress?
+        Thread.current[:transaction_guard_mail_delivery]
+      end
+
+      def with_mail_delivery
+        previous_state = Thread.current[:transaction_guard_mail_delivery]
+        Thread.current[:transaction_guard_mail_delivery] = true
+
+        yield
+      ensure
+        Thread.current[:transaction_guard_mail_delivery] = previous_state
+      end
+    end
+  end
+end

data/lib/transaction_guard/railtie.rb

@@ -0,0 +1,14 @@
+# frozen_string_literal: true
+
+require "rails/railtie"
+
+module TransactionGuard
+  # Loads TransactionGuard in Rails applications and applies sensible defaults.
+  class Railtie < Rails::Railtie
+    initializer "transaction_guard.configure" do
+      TransactionGuard.configure do |config|
+        config.mode = Rails.env.production? ? :off : :warn
+      end
+    end
+  end
+end

data/lib/transaction_guard/reporter.rb

@@ -0,0 +1,45 @@
+# frozen_string_literal: true
+
+module TransactionGuard
+  # Reports detected external side effects.
+  module Reporter
+    module_function
+
+    def report(operation:)
+      message = build_message(operation)
+
+      case TransactionGuard.configuration.mode
+      when :warn
+        warn message
+      when :raise
+        raise TransactionGuard::Error, message
+      when :off
+        nil
+      end
+    end
+
+    def build_message(operation)
+      location = caller_location
+      details = ["Operation: #{operation}"]
+      details << "Location: #{location}" if location
+
+      <<~MESSAGE
+        ⚠ TransactionGuard
+        External side effect detected inside an ActiveRecord transaction.
+        #{details.join("\n")}
+        Risk: The external operation cannot be rolled back automatically if the DB transaction later rolls back.
+        Consider: after_commit, ActiveJob after commit, transactional outbox
+      MESSAGE
+    end
+    private_class_method :build_message
+
+    def caller_location
+      caller_locations(1, 40)&.find do |frame|
+        path = frame.absolute_path || frame.path
+        # Skip gem internals only — not the project path (e.g. .../transaction_guard/spec/...)
+        path && !path.include?("/lib/transaction_guard/")
+      end&.to_s
+    end
+    private_class_method :caller_location
+  end
+end

data/lib/transaction_guard/transaction.rb

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+module TransactionGuard
+  # Provides ActiveRecord transaction state detection.
+  module Transaction
+    module_function
+
+    def open?
+      ActiveRecord::Base.current_transaction.open?
+    end
+  end
+end

data/lib/transaction_guard/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module TransactionGuard
+  VERSION = "0.1.0"
+end

data/lib/transaction_guard.rb

@@ -0,0 +1,47 @@
+# frozen_string_literal: true
+
+require "active_record"
+require "net/http"
+
+begin
+  require "action_mailer"
+rescue LoadError
+  # ActionMailer is optional.
+end
+
+begin
+  require "active_job"
+rescue LoadError
+  # ActiveJob is optional.
+end
+
+require_relative "transaction_guard/configuration"
+require_relative "transaction_guard/version"
+require_relative "transaction_guard/transaction"
+require_relative "transaction_guard/detectors/http"
+require_relative "transaction_guard/reporter"
+require_relative "transaction_guard/detectors/mail"
+require_relative "transaction_guard/detectors/job"
+
+# Detects external side effects performed inside ActiveRecord transactions.
+module TransactionGuard
+  class Error < StandardError; end
+
+  class << self
+    def configuration
+      @configuration ||= Configuration.new
+    end
+
+    def configure
+      yield(configuration)
+    end
+  end
+end
+
+Net::HTTP.prepend(TransactionGuard::Detectors::HTTP)
+
+ActionMailer::MessageDelivery.prepend(TransactionGuard::Detectors::Mail) if defined?(ActionMailer::MessageDelivery)
+
+ActiveJob::Base.singleton_class.prepend(TransactionGuard::Detectors::Job) if defined?(ActiveJob::Base)
+
+require_relative "transaction_guard/railtie" if defined?(Rails::Railtie)

data/sig/transaction_guard.rbs

@@ -0,0 +1,4 @@
+module TransactionGuard
+  VERSION: String
+  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+end

metadata

@@ -0,0 +1,82 @@
+--- !ruby/object:Gem::Specification
+name: transaction_guard
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Yashika
+bindir: exe
+cert_chain: []
+date: 1980-01-02 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: activerecord
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '7.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '7.0'
+description: |
+  Detects external side effects such as HTTP requests, email delivery, and
+  background job enqueuing performed inside ActiveRecord transactions,
+  helping prevent inconsistent state when a database transaction rolls back.
+email:
+- yashikavijay2799@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".rspec"
+- ".rubocop.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
+- LICENSE.txt
+- README.md
+- Rakefile
+- SECURITY.md
+- lib/transaction_guard.rb
+- lib/transaction_guard/configuration.rb
+- lib/transaction_guard/detectors/http.rb
+- lib/transaction_guard/detectors/job.rb
+- lib/transaction_guard/detectors/mail.rb
+- lib/transaction_guard/railtie.rb
+- lib/transaction_guard/reporter.rb
+- lib/transaction_guard/transaction.rb
+- lib/transaction_guard/version.rb
+- sig/transaction_guard.rbs
+homepage: https://github.com/yashika279/transaction_guard
+licenses:
+- MIT
+metadata:
+  allowed_push_host: https://rubygems.org
+  homepage_uri: https://github.com/yashika279/transaction_guard
+  source_code_uri: https://github.com/yashika279/transaction_guard
+  changelog_uri: https://github.com/yashika279/transaction_guard/blob/master/CHANGELOG.md
+  bug_tracker_uri: https://github.com/yashika279/transaction_guard/issues
+  rubygems_mfa_required: 'true'
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 3.1.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.6.9
+specification_version: 4
+summary: Detect external side effects inside ActiveRecord transactions
+test_files: []