From 187b0ef2796c01fb5662ab0e8a37427a1067d0d8 Mon Sep 17 00:00:00 2001
From: Ricardo Vela <97992712+argvniyx-enroute@users.noreply.github.com>
Date: Fri, 22 Mar 2024 10:36:13 -0600
Subject: [PATCH] Point gemspec to rubygems (#9)

This is no longer private and we intend to publish this in rubygems, so
I updated `allowed_push_host` to be `rubygems.org`. I figure then we'll
be able to `bundle exec rake release` and get 2.2.0. lmk if I'm missing
any other steps!
---
 with_transactional_lock.gemspec | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/with_transactional_lock.gemspec b/with_transactional_lock.gemspec
index 0baf9bb..7f63b77 100644
--- a/with_transactional_lock.gemspec
+++ b/with_transactional_lock.gemspec
@@ -15,7 +15,7 @@ Gem::Specification.new do |s|
   s.summary     = "Transactional advisory locks for ActiveRecord"
   s.description = "Advisory locking support for MySQL and Postgresql done right."
   s.license     = "MIT"
-  s.metadata['allowed_push_host'] = 'https://rubygems.pkg.github.com/betterment'
+  s.metadata['allowed_push_host'] = 'https://rubygems.org'
   s.metadata['rubygems_mfa_required'] = 'true' # in case we ever use rubygems
 
   s.files = Dir["lib/**/*", "LICENSE", "Rakefile", "README.md"]