| Age | Commit message (Collapse) | Author |
|---|
|
https://github.com/rubygems/rubygems/commit/ffa395411f
|
|
https://github.com/rubygems/rubygems/commit/9a0e0dfd5b
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8210
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8210
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8210
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8210
|
|
Deprecate Kernel#open and IO support for subprocess creation and
forking. This deprecates subprocess creation and forking in
- Kernel#open
- URI.open
- IO.binread
- IO.foreach
- IO.readlines
- IO.read
- IO.write
This behavior is slated to be removed in Ruby 4.0
[Feature #19630]
Notes:
Merged: https://github.com/ruby/ruby/pull/7915
|
|
|
|
* Follow-up of dbbc3583ba432c279f07b1fa0afb0a8a9ba50c91 which broke this.
|
|
|
|
The dedicated method `File.path` to deal with pathname-like objects
has been provided since ruby 1.9.0.
Also adds a test for rubygems/rubygems#6837.
https://github.com/rubygems/rubygems/commit/258c6eda80
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8127
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8126
|
|
{Nil,True,False}Class#singleton_methods always returns [] indicating
that there are no singleton methods defined, so #singleton_method
should be consistent with that.
Fixes [Bug #11064]
Notes:
Merged: https://github.com/ruby/ruby/pull/7973
|
|
https://github.com/rubygems/rubygems/commit/e8a4184429
|
|
https://github.com/rubygems/rubygems/commit/e30e86aa60
|
|
https://github.com/rubygems/rubygems/commit/9583a7eb82
|
|
https://github.com/rubygems/rubygems/commit/d0c1d97105
|
|
https://github.com/rubygems/rubygems/commit/d61c1362e7
|
|
https://github.com/rubygems/rubygems/commit/d2f2597c31
|
|
https://github.com/rubygems/rubygems/commit/78807add23
|
|
[Feature #19755]
Before (in /tmp/test.rb):
```ruby
Object.class_eval("p __FILE__") # => "(eval)"
```
After:
```ruby
Object.class_eval("p __FILE__") # => "(eval at /tmp/test.rb:1)"
```
This makes it much easier to track down generated code in case
the author forgot to provide a filename argument.
Notes:
Merged: https://github.com/ruby/ruby/pull/8070
|
|
https://github.com/rubygems/rubygems/commit/456fd05d3a
|
|
https://github.com/rubygems/rubygems/commit/9635a2fd74
|
|
Bundler is special since it's not actually locked in the lockfile as a
regular gem (only via `BUNDLED WITH`). So exclude it from that check.
https://github.com/rubygems/rubygems/commit/9f1756ec47
|
|
https://github.com/rubygems/rubygems/commit/258476c38a
|
|
https://github.com/rubygems/rubygems/commit/0f58ef6a32
|
|
https://github.com/rubygems/rubygems/commit/ea2a30ba08
|
|
https://github.com/rubygems/rubygems/commit/6301d3eece
|
|
See https://bugs.ruby-lang.org/issues/19755
In Ruby 3.3, using `eval` without providing a source location
will now default to `"(eval at #{__FILE__}:#{__LINE__})"`.
https://github.com/ruby/syntax_suggest/commit/8e5076472e
|
|
|
|
[Feature #18885]
For now, the optimizations performed are:
- Run a major GC
- Compact the heap
- Promote all surviving objects to oldgen
Other optimizations may follow.
Notes:
Merged: https://github.com/ruby/ruby/pull/7662
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8080
Merged-By: nobu <nobu@ruby-lang.org>
|
|
git sources
Previously, when sorting and comparing git Gemfile vs lockfile sources during
`bundler/setup` to figure out whether we need to re-resolve or not, we
would try to find the default branch if nothing more specific was
specified in the Gemfile.
If the git cache has been deleted thought, that would fail.
The error would still be swallowed (and the branch would simply not be
displayed), but trying to clone would still generate the side effect of
creating the parent folder for the clone.
That could affect non-writable systems that don't expect `bundler/setup`
to write to the filesystem at all.
To fix this, override `Bundler::Source::Git#identifier` to use
exclusively static information, so it does not even try to clone the
repo nor generate any side effects.
https://github.com/rubygems/rubygems/commit/582eb2ef39
|
|
https://github.com/rubygems/rubygems/commit/46cd9be69a
|
|
https://github.com/rubygems/rubygems/commit/57cfe7cf8d
|
|
https://github.com/rubygems/rubygems/commit/c431a1df52
|
|
https://github.com/rubygems/rubygems/commit/802457b0a1
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8035
|
|
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
Notes:
Merged: https://github.com/ruby/ruby/pull/8035
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/8035
|
|
|
|
https://github.com/rubygems/rubygems/commit/4c982684ea
|
|
We have some flags that limit running git commit commands under certain
situations, for example, when running under `--local`. However, those
should only affect remote git operations, not local read-only operations
like `git --version`, or `git rev-parse --abbrev-ref HEAD`.
This commit refactors things to achieve that.
By doing this, the `#to_s` representation of a source is more
consistent, since we don't get any errors when reading the checked out
branch, and we avoid some flip-flop lockfile issues.
https://github.com/rubygems/rubygems/commit/4a529fce81
|
|
lockfile
When dependencies in path sources have changed, we'll be re-resolving,
and we can't really know whether the resolution will be valid or invalid
for the Ruby platform, so skip the removal in that case.
https://github.com/rubygems/rubygems/commit/afc3b0956f
|
|
|
|
|
|
Introduce `Module#set_temporary_name` for setting identifiers for otherwise
anonymous modules/classes.
Notes:
Merged-By: ioquatix <samuel@codeotaku.com>
|
|
Pick from https://github.com/rubygems/rubygems/commit/880dd95996c93adc1e032399816931b243c5fe17
Notes:
Merged: https://github.com/ruby/ruby/pull/7961
|
|
https://github.com/rubygems/rubygems/commit/522b5f1ecd
|
