| Age | Commit message (Collapse) | Author |
|
And also so that it matches the method used by main PubGrub sample
resolver class.
https://github.com/rubygems/rubygems/commit/0e612361b8
|
|
https://github.com/rubygems/rubygems/commit/0ddf25e5aa
|
|
Also bring the man page up to date.
https://github.com/rubygems/rubygems/commit/a849bd6947
|
|
Ensure only one source type is specified, and ensure options that
are only relevant to git sources are only specified with git.
https://github.com/rubygems/rubygems/commit/58b043215e
|
|
https://github.com/rubygems/rubygems/commit/146de56353
|
|
It's the exact same implementation as --git
https://github.com/rubygems/rubygems/commit/18eb2418c6
|
|
https://github.com/rubygems/rubygems/commit/c4a8d2a930
|
|
- Redirect stderr `git ls-files` to null without shelling out.
- When building by `gem`, `__FILE__` is the path name given in the
command line, or the gemspec file name in the current directory. In
that case, comparison it and expanded path never equal. Compare
listed file names with the base name of `__FILE__` instead.
https://github.com/rubygems/rubygems/commit/5583433dbb
|
|
https://github.com/rubygems/rubygems/commit/d004e36c44
|
|
https://github.com/rubygems/rubygems/commit/d198ec36f2
|
|
https://github.com/rubygems/rubygems/commit/e0ef515732
|
|
https://github.com/rubygems/rubygems/commit/bcbe6f7b7a
|
|
https://github.com/rubygems/rubygems/commit/a3f60240bf
|
|
This new shorthand, similar to the existing `github:` shorthand, adds
support for Gitlab repositories with a notable difference. Gitlab
projects may be organized into projects and subprojects. An example
Ruby gem exists at:
https://gitlab.com/gitlab-org/analytics-section/product-analytics/gl-application-sdk-rb
With the new shorthand, a user may install this gem from its repository
by adding:
```ruby
gem "gitlab-sdk", gitlab: "gitlab-org/analytics-section/product-analytics/gl-application-sdk-rb"
```
As with the `github:` shorthand, a supplied string with no `/` will be
interpreted as `example/example`.
Also in keeping with the utility of the `github:` shorthand, the new
`gitlab:` shorthand also supports Merge Request URLs.
```ruby
gem "gitlab-sdk", gitlab: "https://gitlab.com/gitlab-org/analytics-section/product-analytics/gl-application-sdk-rb/-/merge_requests/27"
```
The `gitlab:` gem source shortcut is modeled on the existing `github:`
shortcut, so the new specs mimic the existing examples.
https://github.com/rubygems/rubygems/commit/f4399018c0
|
|
so that __dir__ and __FILE__ will work properly from within that gemfile
fragment, if eval_gemfile is given a relative path
https://github.com/rubygems/rubygems/commit/d521bf9790
|
|
https://github.com/rubygems/rubygems/commit/c38a96ceae
|
|
https://github.com/rubygems/rubygems/commit/2361527c45
|
|
https://github.com/rubygems/rubygems/commit/d1963bf1a6
|
|
https://github.com/rubygems/rubygems/commit/6a0c03c77f
|
|
https://github.com/rubygems/rubygems/commit/085eda7147
|
|
https://github.com/rubygems/rubygems/commit/235f7b4266
|
|
`travis_removal_info` is added by https://github.com/rubygems/rubygems/pull/6150. According to the comment, it's supposed to be removed at bundler v2.5.0 but it hasn't.
https://github.com/rubygems/rubygems/commit/e18797d43f
|
|
https://github.com/rubygems/rubygems/commit/d05b9e659b
Co-authored-by: Samuel Giddins <segiddins@segiddins.me>
|
|
https://github.com/rubygems/rubygems/commit/e0d68a8688
|
|
https://github.com/rubygems/rubygems/commit/5d6a8f2fb4
|
|
https://github.com/rubygems/rubygems/commit/62bc261042
|
|
since 2.6 and 2.7 are EOL and bundler dropped their support by https://github.com/rubygems/rubygems/pull/7116.
https://github.com/rubygems/rubygems/commit/b562d9a822
|
|
https://github.com/rubygems/rubygems/commit/54b67fb251
|
|
https://github.com/rubygems/rubygems/commit/e6a9148ba2
|
|
by two gemspecs
https://github.com/rubygems/rubygems/commit/adc05bf1c3
|
|
If two platform specific variants have different dependencies, then
resolution may fallback to the non platform specific variant. However,
the platform specific variants that have the same dependencies as the
non specific one can still be kept.
Do a pass to complete those after resolution.
|
|
https://github.com/rubygems/rubygems/commit/a8b547c6b1
|
|
https://github.com/rubygems/rubygems/commit/880a4eae7f
|
|
https://github.com/rubygems/rubygems/commit/1d15d8a8ff
|
|
https://github.com/rubygems/rubygems/commit/de9dc90026
|
|
https://github.com/rubygems/rubygems/commit/41f9b4d940
|
|
https://github.com/rubygems/rubygems/commit/e75cca9496
|
|
https://github.com/rubygems/rubygems/commit/39be5cd236
|
|
https://github.com/rubygems/rubygems/commit/7cc647c8f3
|
|
I'm running into a case in my plugin where matches_current_metadata? is
getting called on a lazy specification, and adding this fixes it
https://github.com/rubygems/rubygems/commit/24f962cb42
|
|
https://github.com/rubygems/rubygems/commit/aa3ae5d245
|
|
request
https://github.com/rubygems/rubygems/commit/d26bcd7551
|
|
|
|
https://github.com/rubygems/rubygems/commit/73f1609715
|
|
Not wrapping to_lock since access to it is single threaded and
read-only at the time of writing the lockfile.
https://github.com/rubygems/rubygems/commit/3b53aa1b12
|
|
|
|
|
|
|
|
Refactor vendoring to allow validating vendoring is reproducible
Helps ensure that unsuspecting diffs to the vendored code arent accidentally introduced
|
|
Previous attempt to use a full path when the running version is
different than the one that would be activated by default are different
was not correct.
This is because if this error happens in a `bundle exec` context, the
`Gem.loaded_specs` is cleared because we're in an exec'd process, so
will be always using a full path in these cases.
This alternative approach should do what I was expecting.
https://github.com/rubygems/rubygems/commit/e0bb8bf51b
|