| Age | Commit message (Collapse) | Author |
|
I don't think these methods are hotspots, and since gem specifications
are sometimes serialized to yaml / marshal, I think we should remove as
many instance variables as possible
https://github.com/rubygems/rubygems/commit/40490d918b
|
|
(https://github.com/ruby/erb/pull/89)
This project's `NEWS.md` file appears to be the closest thing to a
changelog file that I could find. The change here links to the file in
the released version's branch. RubyGems.org will use this metadata to
display a link to this file on the gem's release pages.
https://github.com/ruby/erb/commit/85a4f10332
|
|
https://github.com/rubygems/rubygems/commit/e4f1772d80
|
|
https://github.com/rubygems/rubygems/commit/376e4ec8c7
Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
|
|
https://github.com/rubygems/rubygems/commit/7d910dd94c
Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
|
|
https://github.com/ruby/erb/commit/3dc0bb09bf
|
|
https://github.com/ruby/erb/commit/25fdde41d6
|
|
https://github.com/rubygems/rubygems/commit/631a55be91
|
|
https://github.com/rubygems/rubygems/commit/31d67ecc05
|
|
https://github.com/rubygems/rubygems/commit/bfe15a4712
Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
|
|
https://github.com/rubygems/rubygems/commit/73779331ce
|
|
`Bundler::SpecSet#<<`
https://github.com/rubygems/rubygems/commit/aee50b31db
|
|
https://github.com/rubygems/rubygems/commit/ced8ef3a12
Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
|
|
https://github.com/ruby/prism/commit/7574837b7b
|
|
Bundler::RemovedError
https://github.com/rubygems/rubygems/commit/0d4e77d798
Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
|
|
https://github.com/rubygems/rubygems/commit/a51334ba99
|
|
https://github.com/rubygems/rubygems/commit/5b963fb7d3
|
|
"install_if" git gems:
- Fix https://github.com/rubygems/rubygems/pull/8985
- ### Problem
If you have a Gemfile that contains a `install_if` git gem, it will
be impossible to add other gems in the Gemfile and run
`bundle install`, you'll get a "The git source [...] is not yet
checked out".
### Context
The change that modified this behaviour was in https://github.com/rubygems/rubygems/commit/abbea0cc94dd,
and the issue is about the call to `current_dependencies`.
This call filters out irrelevant dependencies such as the one that
get condtionnally installed. By doing so, we skip over setting
the source based of the lockfile for that dependency
https://github.com/rubygems/rubygems/blob/ade324bdc8ea77b342f203cb7f3929a456d725ed/bundler/lib/bundler/definition.rb#L978
Ultimately, because of this, the dependency source doesn't have
any additional information such as the `revision`. Down the line,
when we end up to converge the spec, Bundler will attempt to get the
revision for that spec but won't be able to because the git source
isn't configured to allow running git operations.
### Solution
Filter out the irrelevant only spec only after we have set its
source.
https://github.com/rubygems/rubygems/commit/d2af439671
|
|
https://github.com/ruby/error_highlight/commit/5f976265ef
|
|
https://github.com/ruby/uri/commit/e5074739c3
|
|
https://github.com/ruby/uri/commit/6c6449e15f
|
|
Fix CVE-2025-27221.
https://hackerone.com/reports/3221142
https://github.com/ruby/uri/commit/5cec76b9e8
|
|
https://github.com/ruby/erb/commit/ddfc1ba57e
|
|
https://github.com/ruby/pp/commit/c1992ce07d
|
|
https://github.com/ruby/pp/commit/fee2d39099
|
|
https://github.com/ruby/pp/commit/0e89466269
|
|
(https://github.com/ruby/pp/pull/43)
Ruby 3.5 will use `Set[1, 2, 3]`. This updates pp to use the same format.
https://github.com/ruby/pp/commit/507eebf711
|
|
https://github.com/ruby/pp/commit/6615b62d7b
|
|
These methods are defined for built-in `Set` class on Ruby 3.5.
https://github.com/ruby/pp/commit/352081dbbf
|
|
* It was showing on require 'pp':
lib/pp.rb:525: warning: constant ::Data is deprecated
* Fixes https://github.com/ruby/pp/issues/51
https://github.com/ruby/pp/commit/4fd8f4e0bb
|
|
This supports the new `instance_variables_to_inspect` method from Ruby
core that was added in ruby/ruby#13555.
If `instance_variables_to_inspect` is defined, then
`pretty_print_instance_variables` will use it.
Additionally, this commit introduces tests for both
`pretty_print_instance_variables` and `instance_variables_to_inspect`.
https://github.com/ruby/pp/commit/9cea466c95
|
|
Newer versions of clang's LSAN uses LSAN_OPTIONS environment variable
instead of ASAN_OPTIONS.
|
|
https://github.com/ruby/ipaddr/commit/7c85bb8dfd
Co-authored-by: Tietew <tietew@gmail.com>
|
|
(https://github.com/ruby/erb/pull/85)
https://github.com/ruby/erb/commit/692597b9a2
|
|
https://github.com/rubygems/rubygems/commit/04574ba59a
|
|
https://github.com/ruby/erb/commit/1512314a3b
|
|
https://github.com/ruby/erb/commit/a082298db7
|
|
https://github.com/ruby/erb/commit/4ca7784f10
|
|
And make it a standard setting.
https://github.com/rubygems/rubygems/commit/17e356fa94
|
|
`normalize_path` is a pretty hot path, it's called many times per file
in each gem. Since the platform isn't going to change from call to call,
we can conditionally define `normalize_path` based on the value of
`Gem.win_platform?`.
https://github.com/rubygems/rubygems/commit/d5e61411f2
|
|
without a value
https://github.com/rubygems/rubygems/commit/9f34bf6854
Co-authored-by: Martin Emde <martinemde@users.noreply.github.com>
|
|
https://github.com/rubygems/rubygems/commit/47c3dc19ee
Co-authored-by: Jonathan Barquero <jonbarlo@hotmail.com>
|
|
https://github.com/rubygems/rubygems/commit/3bbbf4a4e5
|
|
This is where error handling happens in all the other options, so it's
where we'll look when we completely remove error handling for these
removed CLI flags in the next major.
https://github.com/rubygems/rubygems/commit/40d660c607
|
|
an error
https://github.com/rubygems/rubygems/commit/8bfe317e6d
|
|
If using a gem with precompiled versions having different dependencies
than the generic version from a path source, and with a lockfile
including a precompiled version, we would materialize the
generic version, but end up using dependencies for the precompiled
version. That will result in the parallel installer missing the
specifications for the extra dependencies of the generic version,
causing a crash.
If we are materializing for installation, make sure we use the
materialized specification when traversing dependencies.
https://github.com/rubygems/rubygems/commit/5f75d75de7
|
|
https://github.com/ruby/erb/commit/cb4911f5f0
|
|
https://github.com/ruby/erb/commit/5e6fea0417
|
|
https://github.com/ruby/erb/commit/ad8231cd68
|
|
https://github.com/ruby/erb/commit/b0ccb1e317
|