| Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/fileutils/commit/b487f09eed
|
|
https://github.com/ruby/fileutils/commit/c3abf39e7a
|
|
https://github.com/ruby/fileutils/commit/fde0f0713a
|
|
https://github.com/ruby/fileutils/commit/71225b1b46
|
|
https://github.com/ruby/fileutils/commit/f0d7fc817b
|
|
https://github.com/ruby/fileutils/commit/277f7f2ff8
|
|
https://github.com/ruby/fileutils/commit/2836a164ed
|
|
Get rid of failure in rbs.
https://github.com/ruby/fileutils/commit/e44b7b366c
|
|
Several optional positional arguments were incorrectly denoted as
keyword arguments so correct them.
https://github.com/ruby/fileutils/commit/c25f069f96
|
|
In this case, an ArgumentError is now raised rather than ignoring the
option, just as GNU coreutils' `ln` would error on the command line.
Fixes https://github.com/ruby/fileutils/pull/128 as well.
https://github.com/ruby/fileutils/commit/4fc578a75f
|
|
Next version for both will be 4.0.0, however, extra work is necessary to
get CI passing against the new major. So for now, I'm bumping just the
minor version.
|
|
I realized `--redownload` is not a good name, because it does not
necessarily redownloads gems. It only forces reinstallation even if gem
is already installed.
So I believe `--force` is actually a better name and the introduction of
`--force` was a misunderstanding of what the `--force` flag did at the
time.
Let's cancel the deprecation of `--force`.
For now the `--redownload` alias is left around until we decide what to
do with it.
|
|
Rather than crashing when parsing it.
https://github.com/rubygems/rubygems/commit/aa0064e4c7
|
|
deprecation warning
Like others, it's a remembered option which we are deprecating in favor
of configuration.
https://github.com/rubygems/rubygems/commit/801d5dd943
|
|
message
https://github.com/rubygems/rubygems/commit/0af03eea5d
|
|
https://github.com/rubygems/rubygems/commit/d1f8e1c4ac
|
|
https://github.com/rubygems/rubygems/commit/88dd7d2d45
|
|
https://github.com/ruby/erb/commit/e8f3e64581
|
|
[Feature #17473]
|
|
|
|
|
|
https://github.com/ruby/uri/commit/d2a79c6343
|
|
For the references to URI::RFC2396_Parser private methods.
https://github.com/ruby/uri/commit/372fbb455d
|
|
These are instance methods, not class methods. And `URI::Parser` was
moved to URI::RFC2396_Parser at [r46491]
[r46491]: https://github.com/ruby/ruby/commit/bb83f32dc3e0
https://github.com/ruby/uri/commit/452d74390c
|
|
RubyGems
Also fix platform warnings when Bundler's entrypoint is bundler's
binstub.
https://github.com/rubygems/rubygems/commit/4b1df58403
|
|
We were only avoiding them when the RUBYGEMS_GEMDEPS variable is used.
Avoid the warnings in general, whenever the entrypoint to Bundler is
`require`.
https://github.com/rubygems/rubygems/commit/8683faef36
|
|
We'll want to reuse this helper in other situations where we don't want
all Bundler loaded.
https://github.com/rubygems/rubygems/commit/9e7018b0a1
|
|
https://github.com/rubygems/rubygems/commit/e068f0649a
|
|
https://github.com/rubygems/rubygems/commit/346d491a11
|
|
https://github.com/rubygems/rubygems/commit/6ee3a33048
|
|
before 2.6.2
RubyGems generated binstubs still provide support for this ancient
version. This makes no sense since we prevent downgrades to such old
versions.
https://github.com/rubygems/rubygems/commit/089cdc3b77
|
|
This is not currently causing any issues, but I think the most correct
thing to do is that Bundler loads the extensions to RubyGems in the
first place, so that they are available from the beginning.
https://github.com/rubygems/rubygems/commit/88faa5c7bb
|
|
Fix the performance regression at #172 for valid emails.
``` yml
prelude: |
require 'uri/mailto'
n = 1000
re = URI::MailTo::EMAIL_REGEXP
benchmark:
n.t..t.: re.match?("n.t..t.@docomo.ne.jp")
example: re.match?("example@example.info")
```
| |released| 788274b| c5974f0| this|
|:--------|-------:|-------:|-------:|-------:|
|n.t..t. | 3.795M| 4.864M| 4.993M| 8.739M|
| | -| 1.28x| 1.32x| 2.30x|
|example | 3.911M| 3.740M| 2.838M| 3.880M|
| | 1.38x| 1.32x| -| 1.37x|
https://github.com/ruby/uri/commit/7363a134ac
|
|
Pointed out by John Hawthorn.
Fixes [Bug #20686]
https://github.com/ruby/uri/commit/c0cfa04a66
|
|
https://github.com/ruby/uri/commit/32335923bf
|
|
local part instead of a character class
https://github.com/ruby/uri/commit/2d7d2d9988
|
|
contain leading or trailing dots
https://github.com/ruby/uri/commit/618e2bb640
|
|
(https://github.com/ruby/uri/pull/38)
https://github.com/ruby/uri/commit/0c2b6468fa
|
|
Use just `self` instead of `self.class`, in `URI::Generic.build`.
Since this is a class method, `self.class` is always `Class` even in
inherited sub classes, and does not have `#component` method.
https://github.com/ruby/uri/commit/6f44d3d40e
|
|
|
|
https://github.com/rubygems/rubygems/commit/afbbc02763
|
|
* Conditionally set changelog_url if gh username passed
and enabled
* conditionally set homepage, source code uri, homepage uri when gh
username passed in
* update documentation to say username will also be used for gemspec file
https://github.com/rubygems/rubygems/commit/1c1ada593b
|
|
https://github.com/rubygems/rubygems/commit/35fc7f9547
|
|
We sometimes send HEAD requests. The s3_uri_signer.rb code allways assumed GETs.
This lead to consistently getting 403 responses back from S3. Recently, S3
attempted to change the behaviour of how 403s are handled when TCP connections
are reused, which escalated this bug from "just noise" to "breaks gem installs".
They've reverted that behaviour, so the severity of this problem is back to
"just noise". Either way, it's a bug in rubygems and warrants a fix it.
https://github.com/rubygems/rubygems/commit/c38f502b73
|
|
%M is minute of the hour.
%m is month of year.
We want the former, not the latter.
https://github.com/rubygems/rubygems/commit/d7ca3fa279
|
|
To try make output a bit less messy.
https://github.com/rubygems/rubygems/commit/92c8bc6769
|
|
If we use long explanations as prompts, sometimes the prompt gets
printed twice due to a (I think) reline/readline bug.
https://github.com/rubygems/rubygems/commit/987e0dfa90
|
|
Previous wording assumed explanation was displayed after the question,
not before.
https://github.com/rubygems/rubygems/commit/04eb3430ba
|
|
https://github.com/ruby/resolv/commit/a28aaed4cb
|
|
RFC 1035 specifies the 255-octet maximum name length. This change set
checks the limit.
https://github.com/ruby/resolv/commit/4c2f71b5e8
|