Age | Commit message (Collapse) | Author |
|
https://github.com/rubygems/rubygems/commit/b0983f392f
|
|
This will help centralize wheel platform selection logic eventually
Signed-off-by: Samuel Giddins <[email protected]>
|
|
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
|
|
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
|
|
I have several gem dylibs that have a line matching "(compatibility "
with no file path preceding it.
https://github.com/rubygems/rubygems/commit/de9dc2bdc4
|
|
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.
|
|
https://github.com/rubygems/rubygems/commit/ba5a62fd04
Notes:
Merged: https://github.com/ruby/ruby/pull/12890
|
|
And make it consistent with platform additions.
https://github.com/rubygems/rubygems/commit/64342ae404
Notes:
Merged: https://github.com/ruby/ruby/pull/12804
|
|
aren't writable:
- ### Problem
Running `bundle doctor` warn about files that aren't writable.
This makes the output of `bundle doctor` very verbose for something
I believe isn't really an issue.
### Context
Rubygems keeps the files original permission at the time the gem
is packaged.
Many gem maintainers have decided that the permissions of the files
in their bundled would be 0444, this includes amongst others:
minitest, selenium, brakeman...
Any git gems that had a 0444 permissions at some point in its git
history would also be reported (as bundle doctor look in the
`cache/bundler/git/<gem>/object` path).
While it completely make sense to report when files aren't readable,
maybe it's worth questioning the usefulness of reporting files
that can't be written and what problem this causes to the user
(if any).
### Solution
Removed the check for unwritable file.
### Side note
I also tweaked the "No issues ..." message logic as it was doing
the opposite (reporting an issue when there is none and vice versa).
This wasn't caught in tests because as a stub on `Bundler.ui.info`
was missing.
https://github.com/rubygems/rubygems/commit/9a426b9495
Notes:
Merged: https://github.com/ruby/ruby/pull/12804
|
|
The previous wording was too specific, there may be situations when the
gem has actually never installed (so never deleted either).
https://github.com/rubygems/rubygems/commit/e4a0d71fbe
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12616
|
|
https://github.com/rubygems/rubygems/commit/f9bf58573f
|
|
These gems always define their main namespace and I don't think that
will ever change.
https://github.com/rubygems/rubygems/commit/6663cbed53
|
|
https://github.com/rubygems/rubygems/commit/0909f07f30
|
|
https://github.com/rubygems/rubygems/commit/694d5f444e
|
|
https://github.com/rubygems/rubygems/commit/c982085f86
|
|
https://github.com/rubygems/rubygems/commit/0c3a65871a
|
|
https://github.com/rubygems/rubygems/commit/d8d68cc00e
|
|
Due to a typo in the spec, the issue was not caught initially. If
Bundler does not need to re-resolve, `bundle lock` is a noop so Bundler
does not add checksums.
To fix the issue, we do something similar to what `bundle install` does,
just without actually installation. First set the domain (local or
remote) according to whether a re-resolve is necessary, and then
materialize lazy specifications into real specifications, so that
checksums are actually fetched from each source.
https://github.com/rubygems/rubygems/commit/84b6f4ee96
|
|
All we need is to setup remote or local sources appropriately.
https://github.com/rubygems/rubygems/commit/3ceff46a2a
|
|
There seems to be no reason why the install should be serial for --local.
The packages are still installed in the right dependency order in this case, so that parallel install can be used.
This patch disables parallel install only in case of no_install_needed.
Also remove the `option` argument, which is effectifely not used.
https://github.com/rubygems/rubygems/commit/5da934ddb6
|
|
https://github.com/rubygems/rubygems/commit/506a863b36
|
|
existing lockfile
https://github.com/rubygems/rubygems/commit/0a9c1ce60d
|
|
|
|
This option is similar to the `bundle install --quiet` option
https://github.com/rubygems/rubygems/commit/3bd773d827
|
|
wrong source
https://github.com/rubygems/rubygems/commit/1e5780db0a
Co-authored-by: Taylor Thurlow <[email protected]>
|
|
https://github.com/rubygems/rubygems/commit/55eb6630a8
|
|
3.0 has been EOL since march, drop support for it before the 3.4 release is cut
Signed-off-by: Samuel Giddins <[email protected]>
https://github.com/rubygems/rubygems/commit/fc1f03b06a
|