| Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/English/commit/5e60c1068a
|
|
https://github.com/ruby/English/commit/70b46b58cc
|
|
https://github.com/rubygems/rubygems/commit/9b3a5a8ae9
|
|
#8572. Specifically:
* Correctly pass command line arguments to CMake
* Call CMake twice - once to configure a project and a second time to build (which is the standard way to use CMake). This fixes the previously incorrect assumption that CMake generates a Make file.
* Update the tests to specify a CMake minimum version of 3.26 (which is already two years old). 3.26 is a bit arbritary but it aligns with Rice, and updates from the ancient 3.5 version being used (which CMake generates a warning message saying stop using it!)
* Update the CMake call to use CMAKE_RUNTIME_OUTPUT_DIRECTORY and CMAKE_LIBRARY_OUTPUT_DIRECTORY to tell CMake to copy compiled binaries to the a Gem's lib directory.
Note the updated builder took inspiration from the Cargo Builder, meaning you first create an instance of CmakeBuilder versus just calling class methods.
https://github.com/rubygems/rubygems/commit/9e248d4679
|
|
https://github.com/ruby/ipaddr/commit/c96dbadee3
|
|
The remote fetcher only works with certain schemes (`http`, `https`,
`s3`, and `file`). It's possible for other schemes to show up in this
code and it can cause bugs.
Before this patch, doing `gem install path:///hello` would result in an
infinite loop because this function would do `send "fetch_path"`,
calling itself forever. Now we see an exception.
I think we should validate gem names earlier, but it's really best
practice to restrict the possible strings passed to `send`.
https://github.com/rubygems/rubygems/commit/54e2781b73
|
|
https://github.com/ruby/prism/commit/dda0dc81df
|
|
https://github.com/ruby/prism/commit/2466940e49
|
|
https://github.com/ruby/prism/commit/b72fcc6183
|
|
The docs currently say to use `Prism.parse(foo, version: RUBY_VERSION)` for this.
By specifying "current" instead, we can have prism raise a more specifc error.
Note: Does not use `ruby_version` from `ruby/version.h` because writing a test for that is not really possible.
`RUBY_VERSION` is nicely stubbable for both the c-ext and FFI backend.
https://github.com/ruby/prism/commit/9c5cd205cf
|
|
- ### Problem
Running `bundle lock --add-checksums` doesn't add the checksum of
gems hosted on server that don't implement the compact index API.
This result in a lockfile which is unusable in production as
some checksums will be missing and Bundler raising an error.
Users can work around this problem by running:
`BUNDLE_LOCKFILE_CHECKSUMS=true bundle install --force`
But this means redownloading and installing all gems which isn't
great and slow on large apps.
### Context
Bundler uses the Compact Index API to get the checksum of gems,
but most private gem servers don't implement the compact index API
(such as cloudsmith or packagecloud). This results in a soft failure
on bundler side, and bundler leaving out blank checksum for those
gems.
### Solution
For gems that are hosted on private servers that don't send back
the checksum of the gem, I'd like to fallback to the
`bundle install` mechanism, which don't rely on an external API but
instead compute the checksum of the package installed on disk.
This patch goes through the spec that didn't return a checksum,
and compute one if the package exists on disk.
This solution makes the `bundle lock --add-checksums` command
actually usable in real world scenarios while keeping the
`bundle lock` command fast enough.
https://github.com/rubygems/rubygems/commit/8e9abb5472
|
|
https://github.com/rubygems/rubygems/commit/6a3342541a
|
|
https://github.com/rubygems/rubygems/commit/89bcdfc941
|
|
https://github.com/rubygems/rubygems/commit/15be905c44
|
|
feature_removed! or feature_deprecated!
https://github.com/rubygems/rubygems/commit/b1b963b34a
Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
|
|
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
|