Age | Commit message (Collapse) | Author |
|
https://github.com/rubygems/rubygems/commit/9f1d07685f
|
|
incorrectly
https://github.com/rubygems/rubygems/commit/19739ba71c
|
|
https://github.com/rubygems/rubygems/commit/3e4687616a
|
|
https://github.com/rubygems/rubygems/commit/b0983f392f
|
|
dependencies
Currently ruby-dev installs an incorrect gemspec for rdoc, that does not
declare its dependency on psych.
This seems like a ruby-core bug, but it seems best for Bundler to ignore
it, go with the remote specification instead, and print a warning.
https://github.com/rubygems/rubygems/commit/227cafd657
|
|
This will help centralize wheel platform selection logic eventually
Signed-off-by: Samuel Giddins <[email protected]>
|
|
If the `ref` option is a specific commit SHA, we can check to see if
it's already fetched locally. If it is, then we don't need to re-fetch
it from the remote.
The `ref` option might not be a commit SHA, so we're using the `#commit`
method which returns the full SHA if it's a commit ref, or the locked
revision, or nil.
This is a small improvement that will make `bundle update` slightly
faster in cases for git-sourced gems pinned to a specific commit.
https://github.com/rubygems/rubygems/commit/f434c2e66c
|
|
https://github.com/rubygems/rubygems/commit/22f0a07377
|
|
Rails
If you have
```
gem "rails", git: "https://github.com/rails/rails"
```
and then explicitly pin to an older ref, like
```
gem "rails", git: "https://github.com/rails/rails", ref: "https://github.com/rubygems/rubygems/commit/99bacb5aa8e5"
```
Then `bundle install` fails, because locked sources fail to be updated
to use the new source.
This commit fixes the problem by making sure get their source properly
replaced.
https://github.com/rubygems/rubygems/commit/5de8c2e0cf
|
|
There's no reason why we should not update bundler as requested, even if
restarts are disabled.
https://github.com/rubygems/rubygems/commit/e59acd2a0d
|
|
version is installed
https://github.com/rubygems/rubygems/commit/1ce0882e6f
|
|
https://github.com/rubygems/rubygems/commit/a9d80a7dcb
|
|
https://github.com/rubygems/rubygems/commit/0574c62fc0
|
|
of x64-mingw-ucrt
https://github.com/rubygems/rubygems/commit/71c969be44
|
|
https://github.com/rubygems/rubygems/commit/aec5a7887d
|
|
`init_gems_rb` preference
https://github.com/rubygems/rubygems/commit/88aeb66f41
|
|
https://github.com/rubygems/rubygems/commit/4f96e12ff3
|
|
https://github.com/rubygems/rubygems/commit/c07e3a88aa
|
|
`spec.files` default ignore list
https://github.com/rubygems/rubygems/commit/6390ed7a2b
|
|
https://github.com/rubygems/rubygems/commit/77ba4192a7
|
|
or `test-unit`
https://github.com/rubygems/rubygems/commit/c464f2036a
|
|
`.gemspec` template
https://github.com/rubygems/rubygems/commit/e48c6beaf6
|
|
`.gemspec` template
https://github.com/rubygems/rubygems/commit/edf13f7e60
|
|
template only when using RSpec
https://github.com/rubygems/rubygems/commit/a42387b8be
|
|
template
https://github.com/rubygems/rubygems/commit/331901941d
|
|
`spec.files` in the `.gemspec` template
https://github.com/rubygems/rubygems/commit/9d937d4f7f
|
|
https://github.com/rubygems/rubygems/commit/2f2046c97b
|
|
https://github.com/rubygems/rubygems/commit/c11539f325
|
|
CONFIGURATION KEYS
Since the remembering options are discouraged, the preferred method should be explained first.
Slight tweak to wording
Fix documentation spec test as per suggested patch
https://github.com/rubygems/rubygems/commit/9f082ccf31
|
|
BUNDLE_PATH are connected
https://github.com/rubygems/rubygems/commit/9ed20bddab
|
|
Signed-off-by: Samuel Giddins <[email protected]>
https://github.com/rubygems/rubygems/commit/24c8073b24
|
|
Signed-off-by: Samuel Giddins <[email protected]>
https://github.com/rubygems/rubygems/commit/9336d3811c
|
|
Signed-off-by: Samuel Giddins <[email protected]>
https://github.com/rubygems/rubygems/commit/f8baf13ab0
|
|
Ruby 3.1 was EOL March 2025
Signed-off-by: Samuel Giddins <[email protected]>
https://github.com/rubygems/rubygems/commit/29c21b1e78
|
|
|
|
provided snce Ruby 2.3
Notes:
Merged: https://github.com/ruby/ruby/pull/13311
|
|
I have several gem dylibs that have a line matching "(compatibility "
with no file path preceding it.
https://github.com/rubygems/rubygems/commit/de9dc2bdc4
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13275
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13275
|
|
|
|
|
|
https://github.com/rubygems/rubygems/commit/e4f70a3e4f
|
|
https://github.com/rubygems/rubygems/commit/40cf54d256
|
|
https://github.com/rubygems/rubygems/commit/38a0bdc123
|
|
https://github.com/rubygems/rubygems/commit/bf63859e1e
|
|
https://github.com/rubygems/rubygems/commit/0aae094c89
|
|
https://github.com/rubygems/rubygems/commit/e6aa8aabcd
|
|
- The command can either be run using:
1. `bundle doctor --ssl`
2. `bundle doctor ssl`
The later is most useful when you need to specify
custom ssl options (such as the verify mode or the
TLS version when running the diagnostic).
The implementation will follow in the next commits.
https://github.com/rubygems/rubygems/commit/993d12874c
|
|
- See explanation in previous commit https://github.com/rubygems/rubygems/commit/170890befb4c
https://github.com/rubygems/rubygems/commit/8f1b5a4479
|
|
- Adding a new `ssl` option to bundle doctor will make the `Doctor`
command quite bloated. The "diagnose ssl" option will also have
children option to allow passing which host or which tls version
you want to diagnose and I feel these options don't belong in the
doctor command.
So my intention in this commit is to prepare to have a new `Doctor`
subcommand and allow for better organisation of the code:
The command will be:
`bundle doctor` -> Run exactly the same as before.
`bundle doctor --ssl` -> Run the doctor command and diagnose SSL
with default options (rubygems.org as the host and verify peer as
the verify mode)
`bundle doctor ssl --host github.com` -> Run the ssl subcommand and
pass a specific host.
This commit just renames a file in order to avoid big diff chunks.
|