brew/Library/Homebrew/Gemfile.lock

243 lines
5.6 KiB
Plaintext
Raw Normal View History

GEM
remote: https://rubygems.org/
specs:
activesupport (6.1.6)
concurrent-ruby (~> 1.0, >= 1.0.2)
i18n (>= 1.6, < 2)
minitest (>= 5.1)
tzinfo (~> 2.0)
zeitwerk (~> 2.3)
addressable (2.8.0)
public_suffix (>= 2.0.2, < 5.0)
ast (2.4.2)
bindata (2.4.10)
bootsnap (1.11.1)
msgpack (~> 1.2)
2020-05-18 16:28:43 +05:30
byebug (11.1.3)
2020-08-09 02:40:01 +05:30
coderay (1.1.3)
commander (4.6.0)
2020-08-09 02:40:01 +05:30
highline (~> 2.0.0)
concurrent-ruby (1.1.10)
connection_pool (2.2.5)
did_you_mean (1.6.1)
diff-lcs (1.5.0)
docile (1.4.0)
domain_name (0.5.20190701)
unf (>= 0.0.5, < 1.0.0)
ecma-re-validator (0.4.0)
regexp_parser (~> 2.2)
elftools (1.1.3)
2020-07-19 19:03:17 +05:30
bindata (~> 2)
2021-09-10 03:08:21 +01:00
hana (1.3.7)
2020-08-09 02:40:01 +05:30
highline (2.0.3)
2018-09-19 03:34:20 +02:00
hpricot (0.8.6)
http-cookie (1.0.4)
domain_name (~> 0.5)
i18n (1.10.0)
concurrent-ruby (~> 1.0)
json_schemer (0.2.21)
2021-09-10 03:08:21 +01:00
ecma-re-validator (~> 0.3)
hana (~> 1.3)
regexp_parser (~> 2.0)
uri_template (~> 0.7)
mechanize (2.8.4)
addressable (~> 2.8)
domain_name (~> 0.5, >= 0.5.20190701)
http-cookie (~> 1.0, >= 1.0.3)
mime-types (~> 3.0)
net-http-digest_auth (~> 1.4, >= 1.4.1)
net-http-persistent (>= 2.5.2, < 5.0.dev)
nokogiri (~> 1.11, >= 1.11.2)
rubyntlm (~> 0.6, >= 0.6.3)
webrick (~> 1.7)
webrobots (~> 0.1.2)
2020-08-09 02:40:01 +05:30
method_source (1.0.0)
mime-types (3.4.1)
mime-types-data (~> 3.2015)
mime-types-data (3.2022.0105)
mini_portile2 (2.8.0)
minitest (5.15.0)
msgpack (1.4.5)
mustache (1.1.1)
net-http-digest_auth (1.4.1)
net-http-persistent (4.0.1)
connection_pool (~> 2.2)
nokogiri (1.13.6)
mini_portile2 (~> 2.8.0)
racc (~> 1.4)
parallel (1.22.1)
parallel_tests (3.8.1)
parallel
parlour (8.0.0)
2020-08-09 02:40:01 +05:30
commander (~> 4.5)
parser
rainbow (~> 3.0)
sorbet-runtime (>= 0.5)
parser (3.1.2.0)
ast (~> 2.4.1)
patchelf (1.3.0)
elftools (>= 1.1.3)
plist (3.6.0)
pry (0.14.1)
2020-08-09 02:40:01 +05:30
coderay (~> 1.1)
method_source (~> 1.0)
public_suffix (4.0.7)
racc (1.6.0)
rack (2.2.3)
rainbow (3.1.1)
rbi (0.0.14)
ast
parser (>= 2.6.4.0)
sorbet-runtime (>= 0.5.9204)
unparser
rdiscount (2.2.0.2)
regexp_parser (2.4.0)
rexml (3.2.5)
2018-09-19 03:34:20 +02:00
ronn (0.7.3)
hpricot (>= 0.8.2)
mustache (>= 0.7.0)
rdiscount (>= 1.5.8)
rspec (3.11.0)
rspec-core (~> 3.11.0)
rspec-expectations (~> 3.11.0)
rspec-mocks (~> 3.11.0)
rspec-core (3.11.0)
rspec-support (~> 3.11.0)
rspec-expectations (3.11.0)
diff-lcs (>= 1.2.0, < 2.0)
rspec-support (~> 3.11.0)
rspec-github (2.3.1)
rspec-core (~> 3.0)
rspec-its (1.3.0)
rspec-core (>= 3.0.0)
rspec-expectations (>= 3.0.0)
rspec-mocks (3.11.1)
diff-lcs (>= 1.2.0, < 2.0)
rspec-support (~> 3.11.0)
rspec-retry (0.6.2)
rspec-core (> 3.3)
rspec-sorbet (1.8.3)
2020-11-17 04:49:54 +01:00
sorbet-runtime
rspec-support (3.11.0)
rspec-wait (0.0.9)
rspec (>= 3, < 4)
rspec_junit_formatter (0.5.1)
Enhance test suite to emit JUnit XML test reports In preparation for detecting flaky tests with BuildPulse, this commit sets up the rspec_junit_formatter gem to output JUnit XML reports of the test suite, which is the format used by BuildPulse and various other tooling that interprets test results. Because the test suite uses the parallel_tests gem, this commit incorporates some related changes to make all the parallel_tests gem and the rspec_junit_formatter gem to cooperate with each other. rspec_junit_formatter writes everything to a single XML file. That works fine when there's only one process writing to the file. By default, whatever process finishes last will write to the file and clobber the output of all the other processes that wrote to the file. 🙈 To prevent this issue, the parallel_tests wiki recommends adding a `.rspec_parallel` file to specify its RSpec options (https://github.com/grosser/parallel_tests/wiki#with-rspec_junit_formatter----by-jgarber), then the project can specify different files for each process to write to like so: --format RspecJunitFormatter --out tmp/rspec<%= ENV['TEST_ENV_NUMBER'] %>.xml However, prior to this commit, the Homebrew/brew test suite specified its RSpec options via the command line. Unfortunately though, there's no way (AFAICT) to set the equivalent of these options via the command line: --format RspecJunitFormatter --out tmp/rspec<%= ENV['TEST_ENV_NUMBER'] %>.xml So, we need to use a `.rspec_parallel` file to specify these options ☝️. However, it appears that RSpec allows you to specify formatters _either_ in an options file (like `.rspec_parallel`) _or_ via command-line args. But if you specify any formatters via command-line args, then all formatters in the options file are ignored. (I suspect that's somehow related to this bit of code in rspec-core: https://github.com/rspec/rspec-core/blob/v3.10.0/lib/rspec/core/configuration_options.rb#L64.) With that in mind, in order to have the RspecJunitFormatter configured in `.rspec_parallel`, we need to move the other formatters into `.rpsec_parallel` as well, instead of passing them as command-line args. Therefore, this commit moves all the formatters into a `.rspec_parallel` file.
2021-06-21 12:58:09 -04:00
rspec-core (>= 2, < 4, != 2.12.0)
rubocop (1.27.0)
parallel (~> 1.10)
parser (>= 3.1.0.0)
2018-01-07 15:40:42 +00:00
rainbow (>= 2.2.2, < 4.0)
regexp_parser (>= 1.8, < 3.0)
rexml
rubocop-ast (>= 1.16.0, < 2.0)
ruby-progressbar (~> 1.7)
unicode-display_width (>= 1.4.0, < 3.0)
rubocop-ast (1.18.0)
parser (>= 3.1.1.0)
rubocop-performance (1.13.3)
rubocop (>= 1.7.0, < 2.0)
2020-09-20 03:18:58 +02:00
rubocop-ast (>= 0.4.0)
rubocop-rails (2.14.2)
activesupport (>= 4.2.0)
rack (>= 1.1)
rubocop (>= 1.7.0, < 2.0)
rubocop-rspec (2.10.0)
rubocop (~> 1.19)
rubocop-sorbet (0.6.8)
rubocop (>= 0.90.0)
ruby-macho (3.0.0)
ruby-progressbar (1.11.0)
rubyntlm (0.6.3)
simplecov (0.21.2)
docile (~> 1.1)
2020-07-02 10:22:54 +01:00
simplecov-html (~> 0.11)
simplecov_json_formatter (~> 0.1)
simplecov-cobertura (2.1.0)
rexml
simplecov (~> 0.19)
2020-10-09 10:12:07 +02:00
simplecov-html (0.12.3)
simplecov_json_formatter (0.1.4)
sorbet (0.5.10012)
sorbet-static (= 0.5.10012)
sorbet-runtime (0.5.10012)
2020-10-09 11:52:48 +02:00
sorbet-runtime-stub (0.2.0)
sorbet-static (0.5.10012-universal-darwin-14)
sorbet-static-and-runtime (0.5.10012)
sorbet (= 0.5.10012)
sorbet-runtime (= 0.5.10012)
spoom (1.1.11)
sorbet (>= 0.5.9204)
sorbet-runtime (>= 0.5.9204)
thor (>= 0.19.2)
tapioca (0.7.2)
bundler (>= 1.17.3)
2020-08-09 02:40:01 +05:30
pry (>= 0.12.2)
rbi (~> 0.0.0, >= 0.0.14)
sorbet-runtime (>= 0.5.9204)
sorbet-static (>= 0.5.9204)
spoom (~> 1.1.0, >= 1.1.11)
thor (>= 1.2.0)
yard-sorbet
thor (1.2.1)
tzinfo (2.0.4)
concurrent-ruby (~> 1.0)
unf (0.1.4)
unf_ext
unf_ext (0.0.8.1)
unicode-display_width (2.1.0)
unparser (0.6.4)
diff-lcs (~> 1.3)
parser (>= 3.1.0)
2021-09-10 03:08:21 +01:00
uri_template (0.7.0)
warning (1.2.1)
webrick (1.7.0)
webrobots (0.1.2)
yard (0.9.27)
webrick (~> 1.7.0)
yard-sorbet (0.6.1)
sorbet-runtime (>= 0.5)
yard (>= 0.9)
zeitwerk (2.5.4)
PLATFORMS
ruby
DEPENDENCIES
activesupport (< 7)
Livecheck: Use Homebrew curl based on root domain At the moment, `#use_homebrew_curl?` can only be true for a `homepage` or `stable`/cask `url` with `using: :homebrew_curl`. If the checked URL differs from these URLs, livecheck won't use brewed curl. This limitation prevents livecheck from using brewed curl for a `livecheck` block URL that's a string literal (not a symbol for a `#checkable_url` like `:stable`, `:head`, `:url`). `libzip` was the original formula referenced in the related brew issue and it meets this criterion, so it doesn't appear to be handled by the existing `#use_homebrew_curl?` implementation. Additionally, the existing behavior can cause livecheck to unnecessarily use brewed curl for a completely different website (e.g., `cubelib`, `otf2`). For example, if the `stable` URL has `using: :homebrew_curl` and the `livecheck` block has `url :homepage`, livecheck will use brewed curl when checking the `homepage`. If these are completely different domains/servers, it's unlikely that we would need to use brewed curl when checking the `homepage`, so this particular behavior may not be beneficial. This commit reimplements `use_homebrew_curl?` to apply brewed curl when the checked URL's root domain is the same as the root domain of an aforementioned formula/cask URL with `using: :homebrew_curl`. For example, this looser approach would allow a `livecheck` block checking `https://www.example.com/downloads/` to use brewed curl if the `stable` URL was `https://downloads.example.com/example.zip` with `using: :homebrew_curl`. These could be different servers but, based on related formulae, this looseness is necessary for the moment. This approach aims to resolve both issues, allowing brewed curl to be applied to a slightly broader range of URLs (i.e., not limited to just the `#checkable_urls`) while also helping to avoid unnecessarily applying brewed curl when it's less likely to be useful (completely different domains). Neither approach is perfect but this one may be more useful in the interim time. Depending on how this looser approach works in practice, we may want to consider returning to a stricter approach once we have something like `using: :homebrew_curl` in `livecheck` blocks (this is forthcoming). Being explicit in a `livecheck` block is the most reliable approach (i.e., only use brewed curl when needed), so we could favor that and pare down the automated approach to only what's needed to support implicit checks (i.e., with no `livecheck` block). Of course, it's also possible to drop the automated approach entirely and simply require a `livecheck` block in this scenario but we can decide on how to handle this when the time comes.
2022-05-17 00:34:32 -04:00
addressable
bootsnap
2020-05-18 16:28:43 +05:30
byebug
concurrent-ruby
2021-06-22 12:30:20 +01:00
did_you_mean
2021-09-10 03:08:21 +01:00
json_schemer
mechanize
minitest
parallel_tests
parlour
2020-07-19 19:03:17 +05:30
patchelf
plist
2018-09-19 03:34:20 +02:00
ronn
rspec
rspec-github
rspec-its
rspec-retry
2020-11-17 04:49:54 +01:00
rspec-sorbet
rspec-wait
Enhance test suite to emit JUnit XML test reports In preparation for detecting flaky tests with BuildPulse, this commit sets up the rspec_junit_formatter gem to output JUnit XML reports of the test suite, which is the format used by BuildPulse and various other tooling that interprets test results. Because the test suite uses the parallel_tests gem, this commit incorporates some related changes to make all the parallel_tests gem and the rspec_junit_formatter gem to cooperate with each other. rspec_junit_formatter writes everything to a single XML file. That works fine when there's only one process writing to the file. By default, whatever process finishes last will write to the file and clobber the output of all the other processes that wrote to the file. 🙈 To prevent this issue, the parallel_tests wiki recommends adding a `.rspec_parallel` file to specify its RSpec options (https://github.com/grosser/parallel_tests/wiki#with-rspec_junit_formatter----by-jgarber), then the project can specify different files for each process to write to like so: --format RspecJunitFormatter --out tmp/rspec<%= ENV['TEST_ENV_NUMBER'] %>.xml However, prior to this commit, the Homebrew/brew test suite specified its RSpec options via the command line. Unfortunately though, there's no way (AFAICT) to set the equivalent of these options via the command line: --format RspecJunitFormatter --out tmp/rspec<%= ENV['TEST_ENV_NUMBER'] %>.xml So, we need to use a `.rspec_parallel` file to specify these options ☝️. However, it appears that RSpec allows you to specify formatters _either_ in an options file (like `.rspec_parallel`) _or_ via command-line args. But if you specify any formatters via command-line args, then all formatters in the options file are ignored. (I suspect that's somehow related to this bit of code in rspec-core: https://github.com/rspec/rspec-core/blob/v3.10.0/lib/rspec/core/configuration_options.rb#L64.) With that in mind, in order to have the RspecJunitFormatter configured in `.rspec_parallel`, we need to move the other formatters into `.rpsec_parallel` as well, instead of passing them as command-line args. Therefore, this commit moves all the formatters into a `.rspec_parallel` file.
2021-06-21 12:58:09 -04:00
rspec_junit_formatter
2018-11-07 15:41:46 +00:00
rubocop
rubocop-ast
2019-04-30 08:44:10 +01:00
rubocop-performance
rubocop-rails
rubocop-rspec
2020-09-20 05:45:30 +02:00
rubocop-sorbet
ruby-macho
simplecov
2021-04-02 10:41:57 -04:00
simplecov-cobertura
2020-10-09 11:52:48 +02:00
sorbet-runtime-stub
2022-05-17 00:09:10 +01:00
sorbet-static-and-runtime
2020-08-09 02:40:01 +05:30
tapioca
2021-02-09 18:59:29 -05:00
warning
BUNDLED WITH
2020-09-20 03:18:58 +02:00
1.17.3