| Age | Commit message (Collapse) | Author |
|
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
|
|
https://github.com/ruby/tsort/commit/bf2e3a8695
|
|
https://github.com/ruby/tsort/commit/ab55dcb7f3
|
|
https://github.com/ruby/tsort/commit/1d1711ad23
|
|
https://github.com/rubygems/rubygems/commit/56b55a198a
|
|
extensions
https://github.com/rubygems/rubygems/commit/265f718be7
|
|
"locally to the installing Ruby installation" felt a bit confusing.
https://github.com/rubygems/rubygems/commit/c950720719
|
|
https://github.com/rubygems/rubygems/commit/4b8570ae15
|
|
I suspect most experienced users won't like the change in defaults, so
document the setting to toggle back the current default.
https://github.com/rubygems/rubygems/commit/93e2e2bef9
|
|
It only affected the `--path` flag which is actually getting removed, so
I don't think it makes sense to make such change. The current behavior
is reasonable and I tried to codify it with a few more specs.
https://github.com/rubygems/rubygems/commit/6f520eb146
|
|
The previous default can already be configured with `bundle config
path.system true`.
https://github.com/rubygems/rubygems/commit/cb483b79db
|
|
There already different ways of toggling off this behavior, like setting
`bundle config clean false`, or configuring Bundler to install to system
gems with `bundle config path.system true`.
https://github.com/rubygems/rubygems/commit/6daa09f60a
|
|
|
|
|
|
retryable errors
Connection errors as well, so useless to retry.
https://github.com/rubygems/rubygems/commit/d2d211651a
|
|
https://github.com/rubygems/rubygems/commit/c241a640fc
|
|
non-retryable
https://github.com/rubygems/rubygems/commit/cd529776d5
|
|
Bundler::Fetcher::DOWNLOADER
And deprecate the old constant.
It's only used in this class, and in Bundler::Fetcher there's already
FAIL_ERRORS, very similar to it. So this makes things less confusing.
https://github.com/rubygems/rubygems/commit/d32ed63d6f
|
|
https://github.com/rubygems/rubygems/commit/4a4e5828db
|
|
commands
https://github.com/rubygems/rubygems/commit/0aa1be946f
|
|
https://github.com/rubygems/rubygems/commit/1497d3f146
|
|
`NameError` during require
Followup to https://github.com/rubygems/rubygems/pull/8436
It fixed showing the template when requiring a non-existant file but
user code can do much more than just trying to require other code.
I encountered this particular case because of load order issues, where a library wasn't able
to properly require itself when loaded before some other library.
https://github.com/rubygems/rubygems/commit/1c910e5afe
|
|
- ### Problem
The man pages for `bundle doctor` which shows up when running
`bundle doctor --help` are no longer in sync with the CLI.
### Context
In #8624, we introduced a change that modifies the structure of
the `bundle doctor` command.
The change added a new subcommand as well a new flag option
`bundle doctor --ssl`
Bundler uses man pages to display help of Thor commands, those man
pages are indepedent from Thor options and need to be kept in sync.
### Solution
Updated the man page for `bundle doctor`. Now that this command is
a subcommand composed of `bundle doctor diagnose` (the default) ,
and `bundle doctor ssl`, I modified the man page to follow
the same markdown structure as other subcommands such as
[bundle plugin](https://github.com/rubygems/rubygems/blob/a902381660f8d17b5c4a93226678c23e046f464f/bundler/lib/bundler/man/bundle-plugin.1.ronn)
https://github.com/rubygems/rubygems/commit/de047f1458
|
|
Tweak version output and verbose mode to be transparent about Bundler
simulating a different version than the real one.
https://github.com/rubygems/rubygems/commit/179354d153
|
|
unnecessary
https://github.com/rubygems/rubygems/commit/bea87eab0b
|
|
We have a quality spec that parses all code for explicit usages of
`Bundler.settings[<something>`, to detect undocumented settings. So
using `Bundler.settings` consistently will help catching these things.
https://github.com/rubygems/rubygems/commit/ce01bb7cc5
|
|
https://github.com/rubygems/rubygems/commit/1ffd83f6c2
|
|
I don't think it makes sense to make this tiny behavior change
configurable. If someone wants to parse version output, and we have a
public setting, they are going to need to accommodate their regexps to
both values of the setting.
In addition to this, I plan to enhance version output with a note about
"simulated version", and in that case, "print_only_version_number" would
no longer hold, since what we print will be more than that anyways.
So, I'd like to remove the setting and change the output in Bundler 4
with no way to opt out.
https://github.com/rubygems/rubygems/commit/d84e9dcf09
|
|
foo.gemspec should be located under the `lib/foo` directory.
|
|
that is outside of lib/optparse directory
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|