giga-pure-mod 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 2b3b11abe0e10566bddc43f2261334739b0f347c1df2de97b452919a8afc605d
+  data.tar.gz: 76bcfb6a81284c033d9390f86c78998d336f6dacda06e1c08a3f3ff7a6c653f7
+SHA512:
+  metadata.gz: 25671907765653dca6f48e89e4bd10b1b15465ef1bf1acf61d4a42db006c07f54fec5cf56da93372f71426c74e64ddb1a09e2c4a3908d92eb989c487c0dff7d3
+  data.tar.gz: 902eebf2a3e27aa42ade4a34b214fb976863124eda16ceb256f690ad40a97a695a0e2c366fa217306bf78654053cf8ddb28873a5ca47e424c2bd2f1d0b30aee2

data/figaro-1.3.0/CHANGELOG.md

@@ -0,0 +1,129 @@
+## 1.3.0 / 2025-06-25
+
+* [ENHANCEMENT] Drop support for Rubies before 2.5
+* [ENHANCEMENT] Add support for Rubies 3.0, 3.1, 3.2, 3.3, and 3.4
+* [ENHANCEMENT] Add support for Rails 6, 7, and 8
+
+## 1.2.0 / 2020-05-10
+
+* [ENHANCEMENT] Drop support for Rubies 1.9.3, 2.0, 2.1, and 2.2
+* [ENHANCEMENT] Add support for Rubies 2.5, 2.6, and 2.7
+* [ENHANCEMENT] Drop support for Rails 3 and 4
+* [ENHANCEMENT] Add support for Rails 5.2 and 6.0
+* [ENHANCEMENT] Proxy all ENV values via CLI to the "heroku" command
+
+## 1.1.1 / 2015-04-30
+
+* [BUGFIX] Fix crash when environment-specific configuration is `nil`
+
+## 1.1.0 / 2015-01-27
+
+* [FEATURE] Support --remote when setting Heroku configuration
+* [ENHANCEMENT] Test against Rails 4.2 (stable)
+
+## 1.0.0 / 2014-09-17
+
+* [BUGFIX] Make calls to Heroku with a clean Bundler environment
+* [ENHANCEMENT] Remove Rails as a runtime dependency
+* [FEATURE] Replace the Rails generator with the `figaro install` task
+* [ENHANCEMENT] Rename the `Figaro.require` method to `Figaro.require_keys`
+* [ENHANCEMENT] Begin to test against Rails 4.2 (beta)
+
+## 1.0.0.rc1 / 2014-04-17
+
+* [FEATURE] Add bang and boolean methods to `Figaro.env`
+* [ENHANCEMENT] Detach `Figaro.env` from the configuration file hash
+* [FEATURE] Add the ability to swap Figaro's application adapter
+* [FEATURE] Warn when configuration keys or values are not strings
+* [FEATURE] Enable Figaro to load multiple times, overwriting previous values
+* [FEATURE] Load Figaro configuration prior to database configuration
+* [ENHANCEMENT] Test against Ruby 2.1
+* [ENHANCEMENT] Test against Rails 4.1
+* [FEATURE] Replace Rake task with `figaro` executable
+* [BUGFIX] Fix character escaping for `figaro heroku:set` on Windows
+* [FEATURE] Warn when a preexisting configuration key is skipped during load
+* [FEATURE] Add the ability to fail fast in the absence of required keys
+* [FEATURE] Tie into Rails' earliest possible `before_configuration` hook
+
+## 0.7.0 / 2013-06-27
+
+* [FEATURE] Allow configuration values to be overridden on the system level
+* [FEATURE] Enable ERB evaluation of the configuration file
+
+## 0.6.4 / 2013-05-01
+
+* [BUGFIX] Make the configuration file path platform-independent
+* [FEATURE] Make `Figaro.env` proxy method calls case-insensitive
+
+## 0.6.3 / 2013-03-10
+
+* [BUGFIX] Run Heroku commands with a clean Bundler environment
+
+## 0.6.2 / 2013-03-07
+
+* [ENHANCEMENT] Refactor `figaro:heroku` task into a unit-tested class
+* [ENHANCEMENT] Relax development gem dependency version requirements
+* [ENHANCEMENT] Track test coverage
+
+## 0.6.1 / 2013-02-27
+
+* [ENHANCEMENT] Declare development gem dependencies in gemfiles
+* [BUGFIX] Cast boolean configuration values to strings
+* [ENHANCEMENT] Use RSpec `expect` syntax
+
+## 0.6.0 / 2013-02-26
+
+* [ENHANCEMENT] Test against Ruby 2.0.0
+* [ENHANCEMENT] Test against Rails 4.0
+
+## 0.5.4 / 2013-02-22
+
+* [ENHANCEMENT] GitHub Ruby Styleguide conventions
+* [ENHANCEMENT] Remove unnecessary development dependencies
+* [FEATURE] Allow `nil` values in `Figaro.env`
+
+## 0.5.3 / 2013-01-12
+
+* [BUGFIX] Fix `figaro:heroku` to properly capture standard output... again
+
+## 0.5.2 / 2013-01-07
+
+* [BUGFIX] Escape special characters in the `figaro:heroku` task
+
+## 0.5.1 / 2013-01-07
+
+* [BUGFIX] Fix `figaro:heroku` to properly capture standard output
+
+## 0.5.0 / 2012-10-28
+
+* [BUGFIX] Automatically cast configuration keys and values to strings
+* [FEATURE] Allow the `figaro:heroku` task to respect remote Rails environment
+* [FEATURE] Enable `Figaro.env` to act as a proxy to `ENV`
+
+## 0.4.1 / 2012-04-25
+
+* [BUGFIX] Fix `figaro:heroku` Rake task failures
+
+## 0.4.0 / 2012-04-20
+
+* [FEATURE] Allow environment-specific configuration
+
+## 0.3.0 / 2012-04-20
+
+* [ENHANCEMENT] Refactor the loading configuration into `ENV`
+* [FEATURE] Add `figaro:heroku` Rake task
+
+## 0.2.0 / 2012-04-03
+
+* [ENHANCEMENT] Test against multiple Rails versions (3.0, 3.1, 3.2)
+* [FEATURE] Add `figaro:install` Rails generator
+* [BUGFIX] Gracefully parse YAML files containing only comments
+
+## 0.1.1 / 2012-04-02
+
+* [ENHANCEMENT] Remove RSpec development gem dependency
+* [ENHANCEMENT] Introduce Figaro, the mascot
+
+## 0.1.0 / 2012-04-02
+
+* Initial release!

data/figaro-1.3.0/CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Contributing to Figaro
+
+Figaro is open source and contributions from the community are encouraged! No
+ contribution is too small.
+
+Please consider:
+
+* Adding a feature
+* Squashing a bug
+* Writing documentation
+* Fixing a typo
+* Correcting [style](https://github.com/styleguide/ruby)
+
+## How do I contribute?
+
+For the best chance of having your changes merged, please:
+
+1. [Fork](https://github.com/laserlemon/figaro/fork) the project.
+2. [Write](http://en.wikipedia.org/wiki/Test-driven_development) a failing test.
+3. [Commit](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) changes that fix the tests.
+4. [Submit](https://github.com/laserlemon/figaro/pulls) a pull request with *at least* one animated GIF.
+5. Be patient.
+
+If your proposed changes only affect documentation, include the following on a
+new line in each of your commit messages:
+
+```
+[ci skip]
+```
+
+This will signal [Travis](https://travis-ci.org) that running the test suite is
+not necessary for these changes.
+
+## Bug Reports
+
+If you are experiencing unexpected behavior and, after having read Figaro's
+documentation, are convinced this behavior is a bug, please:
+
+1. [Search](https://github.com/laserlemon/figaro/issues) existing issues.
+2. Collect enough information to reproduce the issue:
+  * Figaro version
+  * Ruby version
+  * Rails version
+  * Specific setup conditions
+  * Description of expected behavior
+  * Description of actual behavior
+3. [Submit](https://github.com/laserlemon/figaro/issues/new) an issue.
+4. Be patient.

data/figaro-1.3.0/Gemfile

@@ -0,0 +1,12 @@
+source "https://rubygems.org"
+
+gemspec
+
+gem "rails", ">= 5.2.0", "< 9"
+
+group :test do
+  gem "aruba", "~> 2.1"
+  gem "ostruct"
+  gem "rspec", "~> 3.13"
+  gem "sqlite3"
+end

data/figaro-1.3.0/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2012 Steve Richert
+
+MIT License
+
+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/figaro-1.3.0/README.md

@@ -0,0 +1,351 @@
+> [!IMPORTANT]
+> Figaro [v2](https://github.com/laserlemon/figaro/tree/v2) development is underway but _stalled_. I need your help! Please consider [sponsoring Figaro's development](https://github.com/sponsors/laserlemon).
+>
+> With the constraints of a family and a full-time job, even the _emotional_ support that sponsorship provides is extremely valuable in re-energizing Figaro development. Thank you! 💛
+
+<h1>
+  <picture>
+    <source media="(prefers-color-scheme: light)" srcset="https://github.com/user-attachments/assets/5fc9ba97-8288-4228-ba4d-03b2bdcdf0f4">
+    <source media="(prefers-color-scheme: dark)" srcset="https://github.com/user-attachments/assets/1cd8ae2e-afd4-4930-bdc9-147b787ea3fe">
+    <img alt="Figaro" src="https://github.com/user-attachments/assets/5fc9ba97-8288-4228-ba4d-03b2bdcdf0f4" style="height:2em">
+  </picture>
+</h1>
+
+Simple, Heroku-friendly Rails app configuration using `ENV` and a single YAML file
+
+[![Made by laserlemon](https://img.shields.io/badge/laser-lemon-fc0?style=flat-square)](https://github.com/laserlemon)
+[![Gem Version](https://img.shields.io/gem/v/figaro?style=flat-square)](https://rubygems.org/gems/figaro)
+[![Build status](https://img.shields.io/github/checks-status/laserlemon/figaro/main?style=flat-square)](https://github.com/laserlemon/figaro/actions)
+
+**NOTE:** If you're using Figaro 0.7 or prior, please refer to the
+[appropriate documentation](https://github.com/laserlemon/figaro/tree/0-stable#readme)
+or [upgrade](#how-do-i-upgrade-to-figaro-10) to Figaro 1.0.
+
+## Why does Figaro exist?
+
+Figaro was written to make it easy to securely configure Rails applications.
+
+Configuration values often include sensitive information. Figaro strives to be
+secure by default by encouraging a convention that keeps configuration out of
+Git.
+
+## How does Figaro work?
+
+Figaro is inspired by the [Twelve-Factor App](http://12factor.net) methodology,
+which states:
+
+> The twelve-factor app stores config in environment variables (often shortened to env vars or env). Env vars are easy to change between deploys without changing any code; unlike config files, there is little chance of them being checked into the code repo accidentally; and unlike custom config files, or other config mechanisms such as Java System Properties, they are a language- and OS-agnostic standard.
+
+This is straightforward in production environments but local development
+environments are often shared between multiple applications, requiring multiple
+configurations.
+
+Figaro parses a Git-ignored YAML file in your application and loads its values
+into `ENV`.
+
+### Getting Started
+
+Add Figaro to your Gemfile and `bundle install`:
+
+```ruby
+gem "figaro"
+```
+
+Figaro installation is easy:
+
+
+```bash
+$ bundle exec figaro install
+```
+
+This creates a commented `config/application.yml` file and adds it to your
+`.gitignore`. Add your own configuration to this file and you're done!
+
+### Example
+
+Given the following configuration file:
+
+```yaml
+# config/application.yml
+
+pusher_app_id: "2954"
+pusher_key: "7381a978f7dd7f9a1117"
+pusher_secret: "abdc3b896a0ffb85d373"
+```
+
+You can configure [Pusher](http://pusher.com) in an initializer:
+
+```ruby
+# config/initializers/pusher.rb
+
+Pusher.app_id = ENV["pusher_app_id"]
+Pusher.key    = ENV["pusher_key"]
+Pusher.secret = ENV["pusher_secret"]
+```
+
+**Please note:** `ENV` is a simple key/value store. All values will be converted
+to strings. Deeply nested configuration structures are not possible.
+
+### Environment-Specific Configuration
+
+Oftentimes, local configuration values change depending on Rails environment. In
+such cases, you can add environment-specific values to your configuration file:
+
+```yaml
+# config/application.yml
+
+pusher_app_id: "2954"
+pusher_key: "7381a978f7dd7f9a1117"
+pusher_secret: "abdc3b896a0ffb85d373"
+
+test:
+  pusher_app_id: "5112"
+  pusher_key: "ad69caf9a44dcac1fb28"
+  pusher_secret: "83ca7aa160fedaf3b350"
+```
+
+You can also nullify configuration values for a specific environment:
+
+```yaml
+# config/application.yml
+
+google_analytics_key: "UA-35722661-5"
+
+test:
+  google_analytics_key: ~
+```
+
+### Using `Figaro.env`
+
+`Figaro.env` is a convenience that acts as a proxy to `ENV`.
+
+In testing, it is sometimes more convenient to stub and unstub `Figaro.env` than
+to set and reset `ENV`. Whether your application uses `ENV` or `Figaro.env` is
+entirely a matter of personal preference.
+
+```yaml
+# config/application.yml
+
+stripe_api_key: "sk_live_dSqzdUq80sw9GWmuoI0qJ9rL"
+```
+
+```ruby
+ENV["stripe_api_key"] # => "sk_live_dSqzdUq80sw9GWmuoI0qJ9rL"
+ENV.key?("stripe_api_key") # => true
+ENV["google_analytics_key"] # => nil
+ENV.key?("google_analytics_key") # => false
+
+Figaro.env.stripe_api_key # => "sk_live_dSqzdUq80sw9GWmuoI0qJ9rL"
+Figaro.env.stripe_api_key? # => true
+Figaro.env.google_analytics_key # => nil
+Figaro.env.google_analytics_key? # => false
+```
+
+### Required Keys
+
+If a particular configuration value is required but not set, it's appropriate to
+raise an error. With Figaro, you can either raise these errors proactively or
+lazily.
+
+To proactively require configuration keys:
+
+```ruby
+# config/initializers/figaro.rb
+
+Figaro.require_keys("pusher_app_id", "pusher_key", "pusher_secret")
+```
+
+If any of the configuration keys above are not set, your application will raise
+an error during initialization. This method is preferred because it prevents
+runtime errors in a production application due to improper configuration.
+
+To require configuration keys lazily, reference the variables via "bang" methods
+on `Figaro.env`:
+
+```ruby
+# config/initializers/pusher.rb
+
+Pusher.app_id = Figaro.env.pusher_app_id!
+Pusher.key    = Figaro.env.pusher_key!
+Pusher.secret = Figaro.env.pusher_secret!
+```
+
+### Deployment
+
+Figaro is written with deployment in mind. In fact, [Heroku](https://www.heroku.com)'s
+use of `ENV` for application configuration was the original inspiration for
+Figaro.
+
+#### Heroku
+
+Heroku already makes setting application configuration easy:
+
+```bash
+$ heroku config:set google_analytics_key=UA-35722661-5
+```
+
+Using the `figaro` command, you can set values from your configuration file all
+at once:
+
+```bash
+$ figaro heroku:set -e production
+```
+
+For more information:
+
+```bash
+$ figaro help heroku:set
+```
+
+#### Other Hosts
+
+If you're not deploying to Heroku, you have two options:
+
+* Generate a remote configuration file
+* Set `ENV` variables directly
+
+Generating a remote configuration file is preferred because of:
+
+* familiarity – Management of `config/application.yml` is like that of `config/database.yml`.
+* isolation – Multiple applications on the same server will not produce configuration key collisions.
+
+## Is Figaro like [dotenv](https://github.com/bkeepers/dotenv)?
+
+Yes. Kind of.
+
+Figaro and dotenv were written around the same time to solve similar problems.
+
+### Similarities
+
+* Both libraries are useful for Ruby application configuration.
+* Both are popular and well maintained.
+* Both are inspired by Twelve-Factor App's concept of proper [configuration](http://12factor.net/config).
+* Both store configuration values in `ENV`.
+
+### Differences
+
+* Configuration File
+  * Figaro expects a single file.
+  * Dotenv supports separate files for each environment.
+* Configuration File Format
+  * Figaro expects YAML containing key/value pairs.
+  * Dotenv convention is a collection of `KEY=VALUE` pairs.
+* Security vs. Convenience
+  * Figaro convention is to never commit configuration files.
+  * Dotenv encourages committing configuration files containing development values.
+* Framework Focus
+  * Figaro was written with a focus on Rails development and conventions.
+  * Dotenv was written to accommodate any type of Ruby application.
+
+Either library may suit your configuration needs. It often boils down to
+personal preference.
+
+## Is application.yml like [secrets.yml](https://github.com/rails/rails/blob/v4.1.0/railties/lib/rails/generators/rails/app/templates/config/secrets.yml)?
+
+Yes. Kind of.
+
+Rails 4.1 introduced the `secrets.yml` convention for Rails application
+configuration. Figaro predated the Rails 4.1 release by two years.
+
+### Similarities
+
+* Both are useful for Rails application configuration.
+* Both are popular and well maintained.
+* Both expect a single YAML file.
+
+### Differences
+
+* Configuration Access
+  * Figaro stores configuration values in `ENV`.
+  * Rails stores configuration values in `Rails.application.secrets`.
+* Configuration File Structure
+  * Figaro expects YAML containing key/value string pairs.
+  * Secrets may contain nested structures with rich objects.
+* Security vs. Convenience
+  * Figaro convention is to never commit configuration files.
+  * Secrets are committed by default.
+* Consistency
+  * Figaro uses `ENV` for configuration in every environment.
+  * Secrets encourage using `ENV` for production only.
+* Approach
+  * Figaro is inspired by Twelve-Factor App's concept of proper [configuration](http://12factor.net/config).
+  * Secrets are… not.
+
+The emergence of a configuration convention for Rails is an important step, but
+as long as the last three differences above exist, Figaro will continue to be
+developed as a more secure, more consistent, and more standards-compliant
+alternative to `secrets.yml`.
+
+For more information, read the original [The Marriage of Figaro… and Rails](http://www.collectiveidea.com/blog/archives/2013/12/18/the-marriage-of-figaro-and-rails/) blog post.
+
+## How do I upgrade to Figaro 1.0?
+
+In most cases, upgrading from Figaro 0.7 to 1.0 is painless. The format
+expectations for `application.yml` are the same in 1.0 and values from
+`application.yml` are loaded into `ENV` as they were in 0.7.
+
+However, there are breaking changes:
+
+### `Figaro.env`
+
+In Figaro 0.7, calling a method on the `Figaro.env` proxy would raise an error
+if a corresponding key were not set in `ENV`.
+
+In Figaro 1.0, calling a method on `Figaro.env` corresponding to an unset key
+will return `nil`. To emulate the behavior of Figaro 0.7, use "bang" methods as
+described in the [Required Keys](#required-keys) section.
+
+**NOTE:** In Figaro 0.7, `Figaro.env` inherited from `Hash` but in Figaro 1.0,
+hash access has been removed.
+
+### Heroku Configuration
+
+In Figaro 0.7, a Rake task existed to set remote Heroku configuration according
+to values in `application.yml`.
+
+In Figaro 1.0, the Rake task was replaced by a command for the `figaro`
+executable:
+
+```bash
+$ figaro heroku:set -e production
+```
+
+For more information:
+
+```bash
+$ figaro help heroku:set
+```
+
+**NOTE:** The environment option is required for the `heroku:set` command. The
+Rake task in Figaro 0.7 used the default of "development" if unspecified.
+
+### Spring Configuration
+
+If you're using Spring, either [stop](http://collectiveidea.com/blog/archives/2015/02/04/spring-is-dead-to-me)
+or add `config/application.yml` to the watch list:
+
+```rb
+# config/spring.rb
+
+%w(
+  ...
+  config/application.yml
+).each { |path| Spring.watch(path) }
+```
+
+## Who wrote Figaro?
+
+My name is Steve Richert and I wrote Figaro in March, 2012 with overwhelming
+encouragement from my employer, [Collective Idea](http://www.collectiveidea.com).
+Figaro has improved very much since then, thanks entirely to [inspiration](https://github.com/laserlemon/figaro/issues)
+and [contribution](https://github.com/laserlemon/figaro/graphs/contributors)
+from developers everywhere.
+
+**Thank you!**
+
+## How can I help?
+
+Figaro is open source and contributions from the community are encouraged! No
+contribution is too small.
+
+See Figaro's [contribution guidelines](CONTRIBUTING.md) for more information.

data/figaro-1.3.0/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: :spec

data/figaro-1.3.0/bin/figaro

@@ -0,0 +1,5 @@
+#!/usr/bin/env ruby
+
+require "figaro/cli"
+
+Figaro::CLI.start

data/figaro-1.3.0/figaro.gemspec

@@ -0,0 +1,25 @@
+# encoding: utf-8
+
+Gem::Specification.new do |gem|
+  gem.name    = "figaro"
+  gem.version = "1.3.0"
+
+  gem.author      = "Steve Richert"
+  gem.email       = "steve.richert@hey.com"
+  gem.summary     = "Simple Rails app configuration"
+  gem.description = "Simple, Heroku-friendly Rails app configuration using ENV and a single YAML file"
+  gem.homepage    = "https://github.com/laserlemon/figaro"
+  gem.license     = "MIT"
+
+  gem.required_ruby_version = ">= 2.5.0"
+
+  gem.add_dependency "thor", ">= 0.14.0", "< 2"
+
+  gem.add_development_dependency "bundler", ">= 1.7.0", "< 3"
+  gem.add_development_dependency "rake", ">= 10.4.0", "< 14"
+
+  gem.files      = `git ls-files`.split($\)
+  gem.test_files = gem.files.grep(/^spec/)
+
+  gem.executables << "figaro"
+end

data/figaro-1.3.0/gemfiles/rails52.gemfile

@@ -0,0 +1,11 @@
+source "https://rubygems.org"
+
+gemspec path: ".."
+
+gem "rails", "~> 5.2.0"
+
+group :test do
+  gem "aruba", "~> 2.1"
+  gem "rspec", "~> 3.13"
+  gem "sqlite3", "~> 1.4"
+end

data/figaro-1.3.0/gemfiles/rails60.gemfile

@@ -0,0 +1,14 @@
+source "https://rubygems.org"
+
+gemspec path: ".."
+
+gem "rails", "~> 6.0.0"
+
+# See: https://github.com/rails/rails/issues/54263
+gem "concurrent-ruby", "< 1.3.5"
+
+group :test do
+  gem "aruba", "~> 2.1"
+  gem "rspec", "~> 3.13"
+  gem "sqlite3", "~> 1.4"
+end

data/figaro-1.3.0/gemfiles/rails61.gemfile

@@ -0,0 +1,14 @@
+source "https://rubygems.org"
+
+gemspec path: ".."
+
+gem "rails", "~> 6.1.0"
+
+# See: https://github.com/rails/rails/issues/54263
+gem "concurrent-ruby", "< 1.3.5"
+
+group :test do
+  gem "aruba", "~> 2.1"
+  gem "rspec", "~> 3.13"
+  gem "sqlite3", "~> 1.4"
+end

data/figaro-1.3.0/gemfiles/rails70.gemfile

@@ -0,0 +1,14 @@
+source "https://rubygems.org"
+
+gemspec path: ".."
+
+gem "rails", "~> 7.0.0"
+
+# See: https://github.com/rails/rails/issues/54263
+gem "concurrent-ruby", "< 1.3.5"
+
+group :test do
+  gem "aruba", "~> 2.1"
+  gem "rspec", "~> 3.13"
+  gem "sqlite3", "~> 1.4"
+end

data/figaro-1.3.0/gemfiles/rails71.gemfile

@@ -0,0 +1,11 @@
+source "https://rubygems.org"
+
+gemspec path: ".."
+
+gem "rails", "~> 7.1.0"
+
+group :test do
+  gem "aruba", "~> 2.1"
+  gem "rspec", "~> 3.13"
+  gem "sqlite3"
+end