| Age | Commit message (Collapse) | Author |
|
We can skip most stuff in `Gem::RemoteFetcher#download`, and use
`Gem::RemoteFetcher#update_cache_path` directly.
This has the benefit of allowing us to remove some workarounds to
support several rubygems versions, but also allows us to pass the target
folder where the gem should be downloaded directly and skip the logic
inside `Gem::RemoteFetcher#download` to infer the cache path. This will
be useful later to fix some issues with the `global_gem_cache` feature
flag.
https://github.com/rubygems/rubygems/commit/8fe74a77e4
|
|
https://github.com/rubygems/rubygems/commit/3c93b9fd21
|
|
These methods rescue a constant defined by `rubygems/remote_fetcher`,
so they should technically require it.
The require is provided by `gem_remote_fetcher` anyways but I was
running a unit spec that stubs that method, so I was getting an
undefined constant error hiding another error.
https://github.com/rubygems/rubygems/commit/8bedae4034
|
|
https://github.com/rubygems/rubygems/commit/13b933f49a
|
|
https://github.com/rubygems/rubygems/commit/8319305d58
|
|
Extract final cache path to a variable and pass that to `download_gem`.
It actually fits better the parameters documentation since it's the
final directory where the downloaded gem will be placed.
https://github.com/rubygems/rubygems/commit/1429db6a04
|
|
This allows `Source::Git` to no longer load the `digest` gem as it is causing
issues on Ruby 3.1.
https://github.com/rubygems/rubygems/pull/4989/commits/c19a9f2ff7
|
|
When `install_with_build_args` was added in
https://github.com/rubygems/rubygems/commit/be96283985cb49c023112117b2ac2dea0d9becf1,
there were two versions of the method: the default version in the base class that still
used the locking `with_build_args`, and an override in the `Future`
class (for Rubygems 2.0 and up) that yielded without calling
`with_build_args`.
The `with_build_args` version of the method was removed in
https://github.com/rubygems/rubygems/commit/8a5b71e3e8072c64a0f3cab838ba330f5e87e37a
while removing a bunch of the old Rubygems compatibility code.
This commit removes `with_build_args`, since it no longer appears to be
used (the build args are passed as a keyword argument to
`spec.source.install` instead, since
https://github.com/rubygems/rubygems/commit/be96283985cb49c023112117b2ac2dea0d9becf1).
The commit also removes `install_with_build_args` and the conditional
around it, since the method wasn't doing anything different than
`install`, and it had a comment that was no longer accurate.
https://github.com/rubygems/rubygems/commit/ba543a60eb
|
|
https://github.com/ruby/csv/commit/a802690e11
Notes:
Merged: https://github.com/ruby/ruby/pull/5010
|
|
https://github.com/ruby/csv/commit/9c4add0d31
Notes:
Merged: https://github.com/ruby/ruby/pull/5010
|
|
The implementation of the `CSV` shortcut method is broken in Ruby 3
for calls that look like this:
```ruby
CSV(write_stream, col_sep: "|", headers: headers, write_headers: true) do |csv|
...
end
```
The above will result in the following error when the `CSV` method attempts to pass
on arguments to `CSV#instance`:
```
ArgumentError: wrong number of arguments (given 2, expected 0..1)
```
The issue is due to the changes in Ruby 3 relating to positional & keyword arguments.
This commit updates the `CSV()` shortcut implementation to work with Ruby 3, and also
updates the documentation for the shortcut method.
https://github.com/ruby/csv/commit/310dee45fa
Notes:
Merged: https://github.com/ruby/ruby/pull/5010
|
|
https://github.com/ruby/csv/commit/5ff3b95018
Notes:
Merged: https://github.com/ruby/ruby/pull/5010
|
|
https://github.com/ruby/csv/commit/1f9cbc170e
Notes:
Merged: https://github.com/ruby/ruby/pull/5010
|
|
a single entry when row is faulty (https://github.com/ruby/csv/pull/220)
https://github.com/ruby/csv/commit/29cef9ea9d
Notes:
Merged: https://github.com/ruby/ruby/pull/5010
|
|
It's for Ractor. If you want to use the built-in converters, you
should call Ractor.make_shareable(CSV::Converters) and/or
Ractor.make_shareable(CSV::HeaderConverters).
https://github.com/ruby/csv/commit/b0b1325d6b
Notes:
Merged: https://github.com/ruby/ruby/pull/5010
|
|
(https://github.com/ruby/csv/pull/217)
https://github.com/ruby/csv/commit/744e41130c
Notes:
Merged: https://github.com/ruby/ruby/pull/5010
|
|
https://github.com/ruby/csv/commit/3025070cea
Notes:
Merged: https://github.com/ruby/ruby/pull/5010
|
|
|
|
|
|
This reverts commit e22d293e06966733e71a7fd9725eee06c03d0177.
|
|
|
|
https://github.com/ruby/mutex_m/commit/a839e29d04
|
|
(https://github.com/ruby/uri/pull/30)
https://github.com/ruby/uri/commit/bf13946c32
Co-authored-by: Samuel Williams <samuel.williams@oriontransfer.co.nz>
|
|
https://github.com/ruby/delegate/commit/81a3c32140
|
|
I am not sure why this flag was turned off (it wasn't explained in my commit message in 0365dc852767ae589376a7aad1fb129738e408b0 or in my PR in #4411).
Whatever the reason, without `default_ignores` turned on, most default CI configurations will immediately fail, as they most likely vendor and cache their dependencies under `vendor`, which will cause standard to run against all the vendored gems and (most likely) fail. I think we should remove this before this feature is released.
https://github.com/rubygems/rubygems/commit/677f74be48
|
|
https://github.com/ruby/prettyprint/commit/0e8eee5f5f
|
|
https://github.com/ruby/pp/commit/06b839b9ca
|
|
https://github.com/ruby/securerandom/commit/5f9d3d1dfa
|
|
https://github.com/ruby/rinda/commit/d394ba107e
|
|
https://github.com/ruby/optparse/commit/1226b670e6
|
|
https://github.com/ruby/net-http/commit/f3e65e2a31
|
|
https://github.com/ruby/net-protocol/commit/088e52609a
|
|
https://github.com/ruby/uri/commit/1619f713e6
|
|
https://github.com/ruby/ostruct/commit/c535a406f8
|
|
https://github.com/ruby/fileutils/commit/918d19e4f2
|
|
https://github.com/ruby/racc/commit/0c5fe2637c
|
|
https://github.com/ruby/logger/commit/82a59c8d3f
|
|
https://github.com/ruby/tempfile/commit/e5ec902256
|
|
This change fixes alias call-seq to return nil if the method's
call-seq does not specify the alias.
Previously, the alias's call-seq would be an empty string in this case
which broke darkfish rendering.
This change also backfills test coverage for 0ead786 which moved
call-seq deduplication into AnyMethod.
https://github.com/ruby/rdoc/commit/5ce2789b6f
|
|
See related commits:
- ebc66662 for #===
- 4943d208 for #[], #[]=, #<<, and #>>
https://github.com/ruby/rdoc/commit/8e47f7840a
|
|
https://github.com/ruby/rdoc/commit/45c92005fe
|
|
Previously, Parser::C comments all defaulted to "rdoc" format, even
when the user had set a different default with the `--markup=<choice>`
option.
https://github.com/ruby/rdoc/commit/4643b08a26
|
|
This is a prefactor for fixing comment format handling.
https://github.com/ruby/rdoc/commit/a3d366feed
|
|
|
|
Bundler::Fetcher::CertificateFailureError
https://github.com/rubygems/rubygems/commit/11b5d479cb
|
|
https://github.com/ruby/drb/commit/e4b7b68d67
|
|
https://github.com/ruby/drb/commit/7edf67654c
|
|
https://github.com/ruby/time/commit/b9dd593b23
|
|
https://github.com/ruby/open-uri/commit/ec4275a1eb
|
|
https://github.com/ruby/base64/commit/b9e23b27f9
|