| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
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
|
| |
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/fa8455ef7c
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/7cf0a8fa8e
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a581a1dd50
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
rubygems + ruby combinations
https://github.com/rubygems/rubygems/commit/d6df0b7de0
Co-authored-by: André Arko <andre@arko.net>
|
|
|
|
|
|
|
|
| |
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/23178f7d7b
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/f481e8f41a
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/e4a1a9663d
|
|
|
|
|
|
|
|
|
|
| |
current platform
If we are resolving a dependency against a particular platform, and
there are no platform specific variants of the candidates that match
that platform, we should not consider those candidates.
https://github.com/rubygems/rubygems/commit/f6077fe27d
|
|
|
|
|
|
| |
Use a more standard naming for gems.
https://github.com/rubygems/rubygems/commit/75121e83f1
|
|
|
|
| |
Merge from https://github.com/rubygems/rubygems/commit/793ad95ecb40e84a1dcb4cb60f2686843ed90de5
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/c3e54acab0
|
|
|
|
|
|
| |
Only needed if there can be no explicit global source (bundler < 3).
https://github.com/rubygems/rubygems/commit/73923f4af5
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/99cd6e0627
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
optional args
To make sure git uri's specified in Gemfile are never misinterpreted as
optional arguments, potentially allowing for local code execution.
https://github.com/rubygems/rubygems/commit/90b1ed8b9f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`$LOAD_PATH`
This way, if some default gem has been required before bundler, and
rubygems has enhanced the `$LOAD_PATH` to use the latest version in the
system, further requires of that default gem after bundler has been
activated will use the same version and don't cause redefinition
warnings or worse problems derived from the fact of mixing up two
different versions. That, unless the gem is a `Gemfile` dependency. In
that case, we'll get a mismatch error anyways as we do now.
This fix doesn't mean that all default gems internally used by
bundler/rubygems are now supported inside `Gemfile`'s. That should be
handled case by case, but it will now bite people only when they try to
add the gem to their `Gemfile`, not before.
https://github.com/rubygems/rubygems/commit/7325530547
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Very often github source is used to temporarily use a modified gem
while a PR upstream is being reviewed.
So for instance https://github.com/ruby/bigdecimal/pull/211 will look like:
```ruby
gem "bigdecimal", github: "casperisfine/bigdecimal", branch: "git-gem" # https://github.com/ruby/bigdecimal/pull/200
```
It's annoying because you have to fiddle with the branch name, which is copied as `casperisfine:git-gem`, etc etc.
If I could simply use the PR URL like this:
```
gem "bigdecimal", github: "https://github.com/ruby/bigdecimal/pull/211"
```
It would make a very common task for me so much simpler.
https://github.com/rubygems/rubygems/commit/517c527751
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/7d9fdd908d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This block of code already wraps file operations with
`SharedHelpers.filesystem_access`, which rescues and re-raises more
friendly errors. Also, I'm not fully sure creating a temporary directory
can end up raising an `Errno::EACCES` error from reading `tmpdir`
sources. Finally, this rescue block apparently leads to some false
positives when firewall is blocking the ruby executable on Windows, or
at least that's what we've got reported.
In any case, I think it's best to let the original error be raised.
https://github.com/rubygems/rubygems/commit/f7dbe54404
|
|
|
|
|
|
|
|
|
|
| |
Since we no longer have multiple global sources, each top level dependency is
always pinned to a single source, so it makes little sense to talk about
adding or removing a source. Instead, source changes always mean to
change the source one or more dependencies are pinned to. This logic can
now be much simpler.
https://github.com/rubygems/rubygems/commit/f1d33fa0df
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We have two representations of a source. Once used for sorting, which
should not depend on the source's state, but solely on its static
information, like remotes. Another one used for error and informational
messages, which should properly inform about the exact state of the
source when the message is printed.
This commit makes the latter be the default implementation of `to_s`, so
that error and informational messages are more accurate by default.
https://github.com/rubygems/rubygems/commit/b5f2b88957
|
|
|
|
|
|
| |
Otherwise we hide some useful message about dependency source changes.
https://github.com/rubygems/rubygems/commit/c926673c5b
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/6f1b5f68de
|
|
|
|
|
|
|
|
|
| |
0.0.0.SNAPSHOT
The default prerelease requirement in rubygems doesn't actually match
things like "0.0.0.SNAPSHOT".
https://github.com/rubygems/rubygems/commit/711498b342
|
|
|
|
|
|
|
|
|
|
| |
Since the default requirement in rubygems is ">= 0", it was failing to
match 0 prereleases. Changing the default globally to be ">= 0.a"
instead is a major refactoring that's quite tricky to make backwards
compatible, so I'm special casing this where needed for now to fix the
regression.
https://github.com/rubygems/rubygems/commit/68fe37937c
|
| |
|
| |
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/3ede1435ea
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/0396e899db
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
successful runs
https://github.com/rubygems/rubygems/commit/4807bd19a5
|