Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/weakref/commit/f6bd03ed54
|
|
|
|
`actions/checkout` defaults this value to `true`, causing credentials to
be written to `.git/config`. By setting it to `false`, we lessen the
likelihood of secrets being written to disk.
https://github.com/rubygems/rubygems/commit/a751d36456
|
|
They should only load plugins from gems in the bundle.
https://github.com/rubygems/rubygems/commit/a229507820
|
|
https://github.com/rubygems/rubygems/commit/5ad0737e77
|
|
https://github.com/rubygems/rubygems/commit/d23b3d61ac
|
|
Currently to test Bundler 3 mode we have to actually edit the version
file to simulate we're running a future version. This is inconvenient.
Instead, allow passing an environment variable, `BUNDLER_3_MODE`, to set
the "working mode" Bundler should use.
This can now be set easily by end users to enable them to try out the
changes in the future version and give us feedback.
It's unclear how version auto-switching should work when this
environment variable is set, so the auto-switching feature will be
disabled in that case.
https://github.com/rubygems/rubygems/commit/4e92e9b209
|
|
The "ignore" attribute is a RubyGems thing to mark when a installed gem
should be ignored for activation because its extensions are not properly
compiled.
In the case of gems from path sources, the warning is not accurate
because extensions are compiled into the local lib path, which is not
where RubyGems leaves its sentinel `gem.build_complete` file.
Also, there's a single version of each gem in the path source available
to Bundler, so we always certainly want to consider that for activation
and never makes sense to ignore it.
https://github.com/rubygems/rubygems/commit/ec5d33695e
|
|
ruby/ruby#13636
https://github.com/ruby/tempfile/commit/366d9ccb8f
Co-Authored-By: Tim Smith <[email protected]>
|
|
If a previous copy of a gem is already installed, RubyGems will not
reinstall the gem but only recompile its extensions. This seems like a
good idea, but only if the gem is being installed from the registry.
If we are installing a locally built package, then the package should be
completely reinstalled and extensions compiled from the sources in the
locally built package, not from the sources in the previous
installation.
https://github.com/rubygems/rubygems/commit/1c282d98d5
|
|
with old Bundler
https://github.com/rubygems/rubygems/commit/ce7e8e92ca
|
|
Such is the case if you embed JRuby into an application dynamically (such
as via OSGi). From my test environment:
```
irb(main):006:0> $LOADED_FEATURES.grep(/cli.rb/)
=> ["uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/bundler/cli.rb"]
```
https://github.com/rubygems/rubygems/commit/75ac5d46a7
|
|
By running tool/update_bundled_ca_certificates.rb
Signed-off-by: Samuel Giddins <[email protected]>
https://github.com/rubygems/rubygems/commit/54f5278450
|
|
```
" = note: some arguments are omitted. use `--verbose` to show all linker arguments\n" +
" = note: error: unexpected argument '-W' found\n" +
" \n" +
" tip: to pass '-W' as a value, use '-- -W'\n" +
" \n" +
" Usage: sccache [OPTIONS] <--dist-auth|--debug-preprocessor-cache|--dist-status|--show-stats|--show-adv-stats|--start-server|--stop-server|--zero-stats|--package-toolchain <EXE> <OUT>|CMD>\n" +
" \n" +
" For more information, try '--help'.\n" +
" \n" +
```
https://github.com/rubygems/rubygems/commit/45e688ae62
|
|
https://github.com/rubygems/rubygems/commit/9f1d07685f
|
|
incorrectly
https://github.com/rubygems/rubygems/commit/19739ba71c
|
|
https://github.com/rubygems/rubygems/commit/3e4687616a
|
|
Instead, prefer `scan_byte` over `get_byte` since that already returns the byte as an integer, sidestepping conversion issues.
Fixes https://github.com/ruby/prism/issues/3582
https://github.com/ruby/prism/commit/7f3008b2b5
|
|
https://github.com/ruby/net-http/commit/bfc60454f6
|
|
Fixes https://github.com/ruby/net-http/issues/205
https://github.com/ruby/net-http/commit/002441da1e
|
|
If `gem pristine foo` is run, and there's a default copy of foo, only
executables for it are reset. However, that was causing other copies of
`foo` to only reset executables, which is unexpected.
We should not modify `options[:only_executables]`, but respect its value
for every gem, and make sure special handling for default gems does not
leak to other gems.
https://github.com/rubygems/rubygems/commit/2c3039f1b0
|
|
in gem install
Instead of picking essentially a random matching platform
Signed-off-by: Samuel Giddins <[email protected]>
https://github.com/rubygems/rubygems/commit/3727096297
|
|
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
|
|
And adapt release scripts and configuration to the new structure.
https://github.com/rubygems/rubygems/commit/3deb1aedae
|
|
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
|