summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)Author
2025-10-28[ruby/rubygems] Deprecate --default optionHiroshi SHIBATA
https://github.com/ruby/rubygems/commit/55745ee0f8
2025-10-28[ruby/rubygems] Make more shortly with https://rubyonrails.org/conductHiroshi SHIBATA
https://github.com/ruby/rubygems/commit/62ba34d6c9
2025-10-28[ruby/rubygems] Update new gem CoC and promptdysonreturns
Prompt wording "prefer safe, respectful, productive, and collaborative spaces" is copied verbatim from Ruby Community Conduct Guideline. https://github.com/ruby/rubygems/commit/6cdf5f6d8a
2025-10-28[ruby/erb] Version 5.1.3Takashi Kokubun
https://github.com/ruby/erb/commit/e8d382a83e
2025-10-28[ruby/erb] Version 5.1.2Takashi Kokubun
https://github.com/ruby/erb/commit/daa0e8712f
2025-10-27[ruby/rubygems] bundler_4_mode always return trueHiroshi SHIBATA
https://github.com/ruby/rubygems/commit/b2e1810067
2025-10-27[ruby/rubygems] Drop to support old gitHiroshi SHIBATA
https://github.com/ruby/rubygems/commit/687ffd7265
2025-10-26Mention that `require 'pathname'` is necessary for #find, #rmtree and .mktmpdirBenoit Daloze
* See https://bugs.ruby-lang.org/issues/21640#note-16
2025-10-25Improve performance of UnicodeNormalize.canonical_ordering_onetompng
Use array_of_integer.sort! instead of buble-sort-like algorithm
2025-10-24[ruby/rubygems] Forcely activate irb if that isn't available when running ↵Hiroshi SHIBATA
with bundle console https://github.com/ruby/rubygems/commit/42e22fd367
2025-10-23[ruby/rubygems] Bump up vendored uri to 1.0.4Hiroshi SHIBATA
https://github.com/ruby/rubygems/commit/bc77ec0bf2
2025-10-20[ruby/rubygems] update magnus version in rust extension gem templateMat Sadler
https://github.com/ruby/rubygems/commit/1ba8eb4ab3
2025-10-20[ruby/rubygems] Use ruby/rubygems instead of rubygems/rubygems at document, ↵Hiroshi SHIBATA
tool and configurations https://github.com/ruby/rubygems/commit/749b498822
2025-10-20[ruby/rubygems] Now ruby/rubygems is the canonical repository urlHiroshi SHIBATA
https://github.com/ruby/rubygems/commit/c637007e91
2025-10-19[ruby/English] [DOC] Markup variables in the full list as codeNobuyoshi Nakada
https://github.com/ruby/English/commit/5e60c1068a
2025-10-19[ruby/English] [DOC] Enclose English in quotesNobuyoshi Nakada
https://github.com/ruby/English/commit/70b46b58cc
2025-10-17[rubygems/rubygems] Postpone to remove legacy mingw platformHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/9b3a5a8ae9
2025-10-17[rubygems/rubygems] :Revamp CmakeBuilder to fix the issues described in ↵Charlie Savage
#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
2025-10-17[ruby/ipaddr] Fix InvalidAddressError messageishikawa999
https://github.com/ruby/ipaddr/commit/c96dbadee3
2025-10-16[rubygems/rubygems] Restrict what schemes are acceptable in the remote fetcherAaron Patterson
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
2025-10-16[ruby/prism] Handle RUBY_VERSION being nilKevin Newton
https://github.com/ruby/prism/commit/dda0dc81df
2025-10-16[ruby/prism] Do not rely on Gem being loadedKevin Newton
https://github.com/ruby/prism/commit/2466940e49
2025-10-16[ruby/prism] Bump to v1.6.0Kevin Newton
https://github.com/ruby/prism/commit/b72fcc6183
2025-10-16[ruby/prism] Add support for `Prism.parse(foo, version: "current")`Earlopain
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
2025-10-15[rubygems/rubygems] Add checksum of gems hosted on private servers:Edouard CHIN
- ### 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
2025-10-15[rubygems/rubygems] Removed obsoleted option from bundle-exec manpagesHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/6a3342541a
2025-10-15[rubygems/rubygems] Removed deprecated settings methodsHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/89bcdfc941
2025-10-15[rubygems/rubygems] Fixed wrong option messageHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/15be905c44
2025-10-15[rubygems/rubygems] Replaced Bundler::SharedHelpers.major_deprecation to ↵Hiroshi SHIBATA
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>
2025-10-15[rubygems/rubygems] remove some memoizationAaron Patterson
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
2025-10-14[ruby/erb] Add `changelog_uri` to spec metadataJason Garber
(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
2025-10-14[rubygems/rubygems] Fix typoÉtienne Barrié
https://github.com/rubygems/rubygems/commit/e4f1772d80
2025-10-14[rubygems/rubygems] Removed legacy_check option from SpecSet#forHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/376e4ec8c7 Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
2025-10-14[rubygems/rubygems] Removed deprecated legacy windows platform supportHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/7d910dd94c Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
2025-10-12[ruby/erb] Version 5.1.1Takashi Kokubun
https://github.com/ruby/erb/commit/3dc0bb09bf
2025-10-11[ruby/erb] Version 5.1.0Takashi Kokubun
https://github.com/ruby/erb/commit/25fdde41d6
2025-10-10[rubygems/rubygems] Make update_requires_all_flag to settingsHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/631a55be91
2025-10-10[rubygems/rubygems] Make default_cli_command flag to settingsHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/31d67ecc05
2025-10-10[rubygems/rubygems] Make global_gem_cache flag to settingsHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/bfe15a4712 Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
2025-10-10[rubygems/rubygems] Consolidate removal of `Bundler.rubygems.all_specs`David Rodríguez
https://github.com/rubygems/rubygems/commit/73779331ce
2025-10-10[rubygems/rubygems] Consolidate removal of `Bundler::SpecSet#-` and ↵David Rodríguez
`Bundler::SpecSet#<<` https://github.com/rubygems/rubygems/commit/aee50b31db
2025-10-10[rubygems/rubygems] Replaced Bundler.feature_flag.plugins? to Bundler.settingsHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/ced8ef3a12 Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
2025-10-09[ruby/prism] Bump to vKevin Newton
https://github.com/ruby/prism/commit/7574837b7b
2025-10-09[rubygems/rubygems] Removed Bundler.current_ruby.maglev*? and raise ↵Hiroshi SHIBATA
Bundler::RemovedError https://github.com/rubygems/rubygems/commit/0d4e77d798 Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
2025-10-09[rubygems/rubygems] Bump up to Bundler 4.0.0.dev that is next major versionHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/a51334ba99
2025-10-09[rubygems/rubygems] Bump up to RubyGems 4.0.0.dev that is next major versionHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/5b963fb7d3
2025-10-09[rubygems/rubygems] Fix `bundle install` when the Gemfile contains ↵Edouard CHIN
"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
2025-10-07[ruby/error_highlight] Improve English comments and messagesYusuke Endoh
https://github.com/ruby/error_highlight/commit/5f976265ef
2025-10-07[ruby/uri] Bump up to v1.0.4Hiroshi SHIBATA
https://github.com/ruby/uri/commit/e5074739c3
2025-10-07[ruby/uri] Add authority accessorNobuyoshi Nakada
https://github.com/ruby/uri/commit/6c6449e15f
generated by cgit v1.2.3 (git 2.25.1) at 2026-05-13 23:04:49 +0000