Age | Commit message (Collapse) | Author |
|
requirements
https://github.com/rubygems/rubygems/commit/b69e1e9374
|
|
https://github.com/rubygems/rubygems/commit/125415593ead9ab69a9f0bb5392c9d7ec61b1f51
|
|
https://github.com/rubygems/rubygems/commit/1fd818743e
|
|
install output
The lockfile is completely ignored in inline mode, yet the previous
output would suggest it wasn't.
https://github.com/rubygems/rubygems/commit/763125a745
|
|
Previously we were removing not installable specs. However, if those are
the only ones, that would result in a bad error message. If we still
choose them as a last resort, Bundler will later check metadata right
before installing a give a proper error.
This is a regression of https://github.com/rubygems/rubygems/commit/565549260be5 and the
fix is to revert that commit.
https://github.com/rubygems/rubygems/commit/bc18912257
|
|
The follow a tweak on the yank message.
https://github.com/rubygems/rubygems/commit/f6817bfe58
|
|
https://github.com/rubygems/rubygems/commit/66eae0ef1d
|
|
https://github.com/rubygems/rubygems/commit/531d6b5fee
|
|
https://github.com/rubygems/rubygems/commit/fabc357e70
|
|
https://github.com/rubygems/rubygems/commit/3f7d0352e84b29d4a2d4cd93b31e5ebdb5f79cc6
Notes:
Merged: https://github.com/ruby/ruby/pull/5669
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5669
|
|
A while ago, we fixed resolution when using old dependency endpoints to
also consider metadata dependencies, by requesting the full gemspec from
the marsahaled index, which includes this information as opposed to
these old APIs. This has made resolution slower, but correct, but also
introduced the issue that some old marshaled gemspecs don't include the
`required_rubygems_version` field because they were created with a
RubyGems version that predates its addition.
Use a default value in this case.
https://github.com/rubygems/rubygems/commit/5dc94afcc0
Co-authored-by: Ilya Dudarenko <i.dudarenko@tinkoff.ru>
|
|
https://github.com/rubygems/rubygems/commit/5462322f8f
|
|
https://github.com/rubygems/rubygems/commit/d9c442e54c
|
|
ruby/ruby.
Consider the case that the latest Bundler version on RubyGems is higher than
the `system_bundler_version` (= `Bundler::VERSION`) in `make test-bundler` on
ruby/ruby.
See <https://bugs.ruby-lang.org/issues/18643>.
https://github.com/rubygems/rubygems/commit/bfa2f72cfa
|
|
is missing
When I run bundle install with BUNDLE_DEPLOYMENT=true in the environment
on a different platform than I usually do development, I get the
following output to the console (wrapped exactly as shown):
Your bundle only supports platforms ["x86_64-darwin-19"] but your local platform
is x86_64-linux. Add the current platform to the lockfile with `bundle lock
--add-platform x86_64-linux` and try again.
Because the way the message wraps, its not as simple as copying the
suggested command to the clipboard because it contains a newline:
$ bundle lock
Writing lockfile to [...]/Gemfile.lock
$ --add-platform x86_64-linux
Adding a newline right before the command forces the command in the
error message to be on the same line, which facilitates copy-pasting the
command in the message.
https://github.com/rubygems/rubygems/commit/4cf6989b11
|
|
consistent
Previously they had slightly different behavior when combined with
conservative updating flags.
The correct behavior is the `--update-strict` option, so `--script` now
does that, The `--update-strict` option is left there for now but I will
deprecate it later.
https://github.com/rubygems/rubygems/commit/ab42046229
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5606
|
|
sources
https://github.com/rubygems/rubygems/commit/9712262d90
|
|
https://github.com/rubygems/rubygems/commit/bc69d19097
|
|
If a Shipment has been delivered, there is no point in notifying the
buyer that the seller shipped. Instead, we should simply notify the
buyer that the shipment was delivered. This is relevant in cases where
the seller is late to mark a Shipment as shipped, so the first EasyPost
Tracker update marks it as delivered, or in cases where the seller
fails to mark as shipped and the buyer marks it as delivered.
This fixes a Shipment event handler so the buyer notification for
shipment is no longer invoked if the Shipment is already delivered.
https://github.com/rubygems/rubygems/commit/09c2cadc86
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5512
|
|
the current specific platform
https://github.com/rubygems/rubygems/commit/9ca371adf8
|
|
In certain places, we want to display the platform name with
`Gem::Platform.local` instead of `RUBY_PLATFORM`.
Fixes https://github.com/rubygems/rubygems/issues/5264
https://github.com/rubygems/rubygems/commit/bdd1848ae8
|
|
And not depend on the state of rack's master branch, in particular, on
their Ruby support range.
https://github.com/rubygems/rubygems/commit/9ea4baffac
|
|
https://github.com/rubygems/rubygems/commit/ef4e5c6169
|
|
* `foo` => `TestFoo`
* `foo_bar` => `TestFooBar`
* `foo-bar` => `Foo::TestBar`
https://github.com/rubygems/rubygems/commit/353cdd61c3
|
|
https://github.com/rubygems/rubygems/commit/5f698fc4a0
|
|
foo => test/test_foo.rb
foo-bar => test/foo/test_bar.rb
foo_bar => test/test_foo_bar.rb
https://github.com/rubygems/rubygems/commit/c795e5d40d
|
|
command
...with dashed gem name
In "bundle gem" command with dashed name gem (e.g. foo-bar) generates
`test/test_foo/bar.rb`, but this file contains undefined class `TestFoo`
and moreover, does not include in "bundle exec rake test" target.
Therefore, intentially the first test after gem created is fail, but in
case of gem name contains dash character is not.
The change doings...
(when "bundle gem foo-bar" called)
* create `test/test_foo_bar.rb`
* define `TestFooBar` class in `test/test_foo_bar.rb`
https://github.com/rubygems/rubygems/commit/5d9a69fc0f
|
|
Picked at 12aeef6ba9a3be0022be9934c1a3e4c46a03ed3a
Notes:
Merged: https://github.com/ruby/ruby/pull/5462
|
|
required_rubygems_version
https://github.com/rubygems/rubygems/commit/91f07a0208
|
|
https://github.com/rubygems/rubygems/commit/bf0f4b98ee
|
|
library presence
https://github.com/rubygems/rubygems/commit/ecd495ce1b
|
|
https://github.com/rubygems/rubygems/commit/2b42630959
|
|
"NUL.*" means the NUL device on Windows, as well as mere "NUL",
and no data is read.
https://github.com/rubygems/rubygems/commit/e2c7d22745
|
|
https://github.com/rubygems/rubygems/commit/48ea2778e9
|
|
Calculate the checksum of the content, not the given pathname at
the build time itself.
https://github.com/rubygems/rubygems/commit/b60ee97ee9
|
|
The current way works, but error messages show duplicate "/" in paths,
which is weird.
https://github.com/rubygems/rubygems/commit/9123deb4fa
|
|
https://github.com/rubygems/rubygems/commit/a053b7e4d4
|
|
To see if we get more information when this fails.
https://github.com/rubygems/rubygems/commit/853d33fdc3
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
https://github.com/rubygems/rubygems/commit/fa8455ef7c
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
https://github.com/rubygems/rubygems/commit/7cf0a8fa8e
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
https://github.com/rubygems/rubygems/commit/a581a1dd50
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
Since we're at it. This generates a bunch of warnings and seems like a
brittle way to test things, so let's get rid of it.
https://github.com/rubygems/rubygems/commit/f5d45520e0
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
These specs were monkeypatching `RUBY_VERSION`, but that obviously
doesn't change the running ruby to behave any different.
The removal of some features, in particular, `String#untaint`, made
these specs fail, because untaint is no longer available under ruby-core
and bundler calls `untaint` when `RUBY_VERSION` is less than "2.7",
which these specs were overwriting it to be.
Rewrite these specs to not overwrite `RUBY_VERSION`, but still test the
same things.
https://github.com/rubygems/rubygems/commit/e8c7b92901
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5342
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5334
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5325
|