| Age | Commit message (Collapse) | Author |
|
when locked for a specific platform
If they are already in the lockfile as the most specific variant for a
platform, we shouldn't change that unless explicitly unlocking.
https://github.com/rubygems/rubygems/commit/a901660498
|
|
https://github.com/rubygems/rubygems/commit/bcbbff5149
|
|
Instead of having to do a complete pass after resolve.
To do this, we add to the ruby group all the platform specs with the
same dependencies as the ruby specs.
https://github.com/rubygems/rubygems/commit/e50415f2a6
|
|
It's just for debugging and a simple method, so no need.
https://github.com/rubygems/rubygems/commit/3230425a9a
|
|
https://github.com/rubygems/rubygems/commit/e2c1bc1b6c
|
|
It results in more consistent error messages.
https://github.com/rubygems/rubygems/commit/a4b34361cc
|
|
This RubyGems feature is being released as 3.5.15, so we can stop
monkeypatching RubyGems once support for the previous version is
dropped.
https://github.com/rubygems/rubygems/commit/36f146840d
|
|
https://github.com/rubygems/rubygems/commit/b07e46820d
|
|
https://github.com/rubygems/rubygems/commit/14c4c16e96
|
|
options
https://github.com/rubygems/rubygems/commit/d4360c9032
|
|
resolution
If it has been explicitly added by `bundle lock --add-platform`, we
don't want to remove it.
https://github.com/rubygems/rubygems/commit/09cf921dd6
|
|
https://github.com/rubygems/rubygems/commit/1c80c6072f
|
|
|
|
permission bit
https://github.com/rubygems/rubygems/commit/979cd898f9
|
|
RubyGems >= 3.5 no longer raises `Gem::FilePermissionError` explicitly.
https://github.com/rubygems/rubygems/commit/df54b9fd90
|
|
https://github.com/rubygems/rubygems/commit/f58660ffcc
|
|
This commit switches out the full gemspec validation for a partial one
which only performs resolution related checks. This will allow gem
authors to run `bundle` commands immediately after creating a new gem
with Bundler, rather than having to fix metadata validation issues in
the default gemspec.
https://github.com/rubygems/rubygems/commit/d5aa9cae9d
|
|
This method validates only what is required for resolution, skipping any
irrelevant metadata validation. This will be used by Bundler instead of
doing a full validation, allowing gem authors to use `bundle` commands
immediately in newly created gems without first having to fix invalid
metafata fields in the default gemspec.
https://github.com/rubygems/rubygems/commit/da7704cfc0
|
|
https://github.com/rubygems/rubygems/commit/72103ca1e8
|
|
a full unlock
https://github.com/rubygems/rubygems/commit/a8670e43f8
|
|
When locked only to RUBY, and some locked spec does not meet locked
dependencies, Bundler would remove the only locked platform and end up
creating a lockfile with empty sections.
We can't rely on our criteria to remove invalid platforms if locked
specs are not valid in the first place.
https://github.com/rubygems/rubygems/commit/1dba05cf53
|
|
cached! are used
https://github.com/rubygems/rubygems/commit/04b26731cb
|
|
Calling `remote!` or `cached!` on the source was expiring local specs
for now reason. It's unnecessary to override these methods for path
sources since they only deal with local specifications.
https://github.com/rubygems/rubygems/commit/aa93b196a2
|
|
local platform is locked
https://github.com/rubygems/rubygems/commit/36a02c6128
|
|
If RUBY is the only platform in the lockfile, we were skipping adding
the local platform to the list of resolution platforms. This generally
works anyways, because we had some code to still add it if the RUBY
platform is not valid for the set of locked gems.
However, sometimes it can happen that "RUBY" is valid for the current
set of locked gems, but when adding a new dependency, it becomes
invalid. For example, when adding sorbet to a Gemfile, that will
introduce `sorbet-static` as an indirect dependency which does not have
a generic "RUBY" variant. This will cause resolution to take a long time
continuously backtracking trying to find solutions that don't introduce
`sorbet-static` as a dependency and will eventually fail.
Instead, we can always add the local platform to the set of resolution
platforms before resolving, and remove it as necessary after resolution
so that we lock the correct set of platforms.
https://github.com/rubygems/rubygems/commit/6ed1fe6050
|
|
The `force-ruby-platform` settings is properly respected when
materializing since https://github.com/rubygems/rubygems/commit/e17d7e9efb91.
https://github.com/rubygems/rubygems/commit/c4ba54eb96
|
|
* The string search parser was more memory efficient but
in some cases, much slower. Reverting until a better
solution is found.
* Handle the situation where the line might be blank (Artifactory bug)
https://github.com/rubygems/rubygems/commit/222d38737d
|
|
`current_dependencies` doesn't return gems in optional groups, while `specs` would
Closes https://github.com/rubygems/rubygems/pull/7757
https://github.com/rubygems/rubygems/commit/c797e95636
|
|
https://github.com/rubygems/rubygems/commit/07a5faeb89
|
|
https://github.com/rubygems/rubygems/commit/f9fb413a19
|
|
Namely, when a gem has not previously been installed, and Bundler is
using the compact index API, fund metadata was not getting printed
because the proper delegation was not implemented in the specification
class used by the compact index.
https://github.com/rubygems/rubygems/commit/9ef5139f60
|
|
https://github.com/rubygems/rubygems/commit/f4ce3aae71
|
|
https://github.com/rubygems/rubygems/commit/19a0e3730c
|
|
So that those lockfiles still work with older Bundler versions.
https://github.com/rubygems/rubygems/commit/880275bb66
|
|
binstubs
https://github.com/rubygems/rubygems/commit/076aba8b1c
|
|
used in config
https://github.com/rubygems/rubygems/commit/a0af1baa2b
|
|
I don't think we should add more of these.
https://github.com/rubygems/rubygems/commit/9eee9948cc
|
|
https://github.com/rubygems/rubygems/commit/7d1e8be2ce
|
|
https://github.com/rubygems/rubygems/commit/31cb15d03f
|
|
The `normalize_uri` method always gives back a String.
https://github.com/rubygems/rubygems/commit/246953010c
|
|
https://github.com/rubygems/rubygems/commit/e31df2d6ef
|
|
Otherwise Ruby >= 3.2 gives a warning which makes several specs fail,
and truffleruby rejects it at all.
https://github.com/rubygems/rubygems/commit/ae2878484f
|
|
This significantly reduces memory usage.
https://github.com/rubygems/rubygems/commit/8a76506c90
|
|
https://github.com/rubygems/rubygems/commit/ffd3711d00
|
|
Gemfile as "local app"
https://github.com/rubygems/rubygems/commit/6aa2ac337f
|
|
any other gem
For backwards compatibility, make sure default gems are still used as a
last resort when materializing, in case no remote, cached, or installed
specs are found.
https://github.com/rubygems/rubygems/commit/93788f689f
|
|
https://github.com/rubygems/rubygems/commit/0b284fc88c
|
|
https://github.com/rubygems/rubygems/commit/73794a95b9
|
|
https://github.com/rubygems/rubygems/commit/351ff2512f
|
|
https://github.com/rubygems/rubygems/commit/71bcf354f5
|