Age | Commit message (Collapse) | Author |
|
|
|
[rubygems/rubygems] Relax matching pattern for rake version
https://github.com/rubygems/rubygems/commit/a89f74c27e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[rubygems/rubygems] Fix a test for `bin/bundle update --bundler` to
pass on 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
---
spec/bundler/commands/binstubs_spec.rb | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
|
|
|
|
Merge RubyGems 3.3.x and Bundler 2.3.x
|
|
We stay to the stable version for releasing Ruby 3.1.0.
Revert commits:
b86a7ba49252e00e19c22bbcdc821b5acc31ff92
ef973aa7aa65143a4f05d623c016d459426770d0
|
|
different platforms
https://github.com/rubygems/rubygems/commit/83bc87ca98
|
|
https://github.com/rubygems/rubygems/commit/04b1ac72b9
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5317
|
|
The `BUNDLE_` prefix should be reserved to first class settings that
should be listed when running `bundle config`. This one is just a hacky
environment variable that has not corresponding documented setting.
https://github.com/rubygems/rubygems/commit/7e255c5058
|
|
https://github.com/rubygems/rubygems/commit/f481e8f41a
|
|
Use a more standard naming for gems.
https://github.com/rubygems/rubygems/commit/75121e83f1
|
|
Merge from https://github.com/rubygems/rubygems/commit/793ad95ecb40e84a1dcb4cb60f2686843ed90de5
Notes:
Merged: https://github.com/ruby/ruby/pull/5265
|
|
https://github.com/rubygems/rubygems/commit/c3e54acab0
|
|
Test and ensure "false" is handled
Don't use yield_self to operate on autorequire
Remove duplicate autorequire
Add banner to require option
Don't use json to break down require params
Pass linter
https://github.com/rubygems/rubygems/commit/a4f2f8ac17
|
|
https://github.com/rubygems/rubygems/commit/7d9fdd908d
|
|
|
|
https://github.com/rubygems/rubygems/commit/3ede1435ea
|
|
been deleted
https://github.com/rubygems/rubygems/commit/fe1a31db31
|
|
Recent changes made a warning while running specs show up for some
reason, and it revealed this error.
https://github.com/rubygems/rubygems/commit/bbf55de38e
|
|
Gemfile
https://github.com/rubygems/rubygems/commit/6a19cca7e5
|
|
Picked from https://github.com/rubygems/rubygems/commit/4b498709a015a94e14a3852a1841a7a3e669133d
|
|
https://github.com/rubygems/rubygems/commit/79f3c00caa
|
|
It doesn't add anything.
https://github.com/rubygems/rubygems/commit/ece3c864df
|
|
can't be deleted
Instead of showing the bug report template with an error at a random
place.
https://github.com/rubygems/rubygems/commit/882ad3ab57
|
|
Instead of showing the bug report place with an error at a randome
place.
https://github.com/rubygems/rubygems/commit/241854ce73
|
|
incomplete resolve
In case we have a corrupted lockfile that claims to support a platform, but
it's missing platform specific gems for it, bundler has a check that
detects the situation and forces a re-resolve. The result of this check
is kept under the `@locked_specs_incomplete_for_platformn` instance
variable in `Definition`.
The installer, however, calls `Definition#nothing_changed?` before this
instance variable has been filled, so the result of it is actually
incorrect here since it will claim that nothing has changed, but
something has changed (locked specs are incomplete for the current
platform).
The consequence of this incorrect result is that the installer thinks it
can go on without re-resolving, resulting in the incomplete resolution
from the lockfile being used, and in a crash being triggered due to
that.
The solution is to make sure the `@locked_specs_incomplete_for_platform`
instance variable is filled before `nothing_changed?` gets called.
Moving it to `initialize` makes the most sense, not because it's the
best place for it (we can refactor this later), but because all of the
other "outdated definition" checks are already set there.
https://github.com/rubygems/rubygems/commit/708afdd789
|
|
https://github.com/rubygems/rubygems/commit/8950631f02
|
|
All supported rubygems versions implement this.
https://github.com/rubygems/rubygems/commit/2130782ef6
|
|
https://github.com/rubygems/rubygems/commit/ff86cd7dd2
|
|
If a non exact name (matched as a regexp) is passed to `bundle info`,
these strings might not match.
https://github.com/rubygems/rubygems/commit/831edf1edf
|
|
https://github.com/rubygems/rubygems/commit/80158e9d75
|
|
In 2021, Ruby 2.5 and older are EOL.
We can set the default required Ruby version to 2.6.0 to
encourage people to use newer Ruby.
If the command is executed with old Ruby, it falls back to 2.3.0.
It's still possible to create a gem for older Ruby just by changing
two lines of code (one in gemspec and another is in rubocop.yml).
|
|
We want to update the original repo, not a fresh one.
This went undetected because the `git commit` command inside the
`update_git` method ignores failures, and in this case it was failing
because all files are untracked in the new repo.
I will fix that later but for now fix the typo.
https://github.com/rubygems/rubygems/commit/c889f1d715
|
|
example.com is the canonical stand in for domain examples and will never have a backing website.
via https://www.rfc-editor.org/rfc/rfc2606.html
https://github.com/rubygems/rubygems/commit/26622c81c2
|
|
Closes https://github.com/rubygems/rubygems/issues/4889
https://github.com/rubygems/rubygems/commit/2b1754479c
|
|
https://github.com/rubygems/rubygems/commit/290b6ab078
Notes:
Merged: https://github.com/ruby/ruby/pull/4789
|