summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)Author
2024-11-08[ruby/ostruct] Update license files same as ruby/rubyHiroshi SHIBATA
https://github.com/ruby/ostruct/commit/85a773bb41
2024-11-07[ruby/irb] Correct ja/help-message for --context-mode and --promptKouhei Yanagita
(https://github.com/ruby/irb/pull/1029) https://github.com/ruby/irb/commit/b21432daf7
2024-11-07[rubygems/rubygems] Undeprecate Gemfiles without a global sourceDavid Rodríguez
After having a second look at this deprecation, the explanation that we're giving does not make a lot of sense. When working only with local gems, Bundler will indeed generate a different lockfile depending on the latest installed version of each gem is at `bundle install` time. That's the same situation that happens with remote sources: Bundler will generate a different lockfile depending on the latest version of each gem available remotely. So, I don't think "a consistent lockfile not getting generated" is a good motivation for deprecating this. Also, this deprecation brings additional challenges, since for example, it should arguably not get printed when using `bundle install --local`? The original problem when this deprecation was introduced was an incorrect message about a missing gem having been yanked. So, I think a better solution is to, as long as we give proper error messages when things go wrong, let users do what's best for them and undo the deprecation. https://github.com/rubygems/rubygems/commit/17499cb83f
2024-11-07[ruby/uri] Bump up v1.0.0Hiroshi SHIBATA
https://github.com/ruby/uri/commit/af8d9d6bb1
2024-11-07[ruby/net-http] Bump up v0.5.0Hiroshi SHIBATA
https://github.com/ruby/net-http/commit/28a4bf9295
2024-11-07[ruby/delegate] Bump up v0.4.0Hiroshi SHIBATA
https://github.com/ruby/delegate/commit/713059a5e9
2024-11-07[ruby/delegate] Bump up required ruby version to 3.0Hiroshi SHIBATA
https://github.com/ruby/delegate/commit/6daeb4248f
2024-11-07[ruby/logger] Enable subclasses to configure level isolationHartley McGuire
(https://github.com/ruby/logger/pull/103) `Logger#with_level` was recently added to enable configuring a `Logger`'s level for the duration of a block. However, the configured level is always tied to the currently running `Fiber`, which is not always ideal in applications that mix `Thread`s and `Fiber`s. For example, Active Support has provided a similar feature (`ActiveSupport::Logger#log_at`) which, depending on configuration, can be isolated to either `Thread`s or `Fiber`s. This commit enables subclasses of `Logger` to customize the level isolation. Ideally, it will enable replacing most of Active Support's `#log_at`, since both methods end up serving the same purpose. https://github.com/ruby/logger/commit/dae2b832cd
2024-11-06[rubygems/rubygems] Add naive infinite loop detection when fixing lockfile ↵David Rodríguez
dependencies https://github.com/rubygems/rubygems/commit/5e933968a2
2024-11-06[rubygems/rubygems] Note about why we don't fix lockfile dependencies backed ↵David Rodríguez
by installed specs https://github.com/rubygems/rubygems/commit/6fa94b5d72
2024-11-06[rubygems/rubygems] This is not about the lockfile anymoreDavid Rodríguez
https://github.com/rubygems/rubygems/commit/f2e0a72291
2024-11-06[rubygems/rubygems] Automatically fix lockfile when the API reveals missing depsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/92196ccfdb
2024-11-06[rubygems/rubygems] Check for `EndpointSpecification` exactlyDavid Rodríguez
https://github.com/rubygems/rubygems/commit/8fac200ded
2024-11-06[rubygems/rubygems] Simplify code structureDavid Rodríguez
https://github.com/rubygems/rubygems/commit/a4dd06f095
2024-11-06[rubygems/rubygems] Fix manifest in gem package using incorrect platform ↵David Rodríguez
sometimes If a gem package is built from a specification whose platform has been modified, it will include metadata using the old platform. This change should fix the problem by making sure `original_platform` is always properly set. https://github.com/rubygems/rubygems/commit/ecd5cd4547
2024-11-06[rubygems/rubygems] Fix some JRuby warnings when using `bundler/setup` with ↵David Rodríguez
Ruby's -w flag When using the `bundler/setup` entrypoint, Bundler prints the following warnings in JRuby in `-w` is passed to Ruby. ``` /path/to/bundler/shared_helpers.rb:10: warning: constant Bundler::WINDOWS is deprecated /path/to/bundler/shared_helpers.rb:11: warning: constant Bundler::FREEBSD is deprecated /path/to/bundler/lib/bundler/shared_helpers.rb:12: warning: constant Bundler::NULL is deprecated ``` This does not happen in CRuby. This seems like a JRuby bug but we can skip it by autoloading the constants. https://github.com/rubygems/rubygems/commit/761ca29fa2
2024-11-06[ruby/shellwords] Bump up v0.2.1Hiroshi SHIBATA
https://github.com/ruby/shellwords/commit/ee08b981ac
2024-11-06[ruby/open-uri] Bump up v0.5.0Hiroshi SHIBATA
https://github.com/ruby/open-uri/commit/8f5a4ef6f9
2024-11-06[ruby/timeout] Bump up v0.4.2Hiroshi SHIBATA
https://github.com/ruby/timeout/commit/2f52522994
2024-11-06[ruby/tmpdir] Bump up v0.3.0Hiroshi SHIBATA
https://github.com/ruby/tmpdir/commit/ef9ca591cf
2024-11-06[ruby/tempfile] Bump up v0.3.0Hiroshi SHIBATA
https://github.com/ruby/tempfile/commit/2ff9b3ccef
2024-11-06[ruby/yaml] Bump up v0.4.0Hiroshi SHIBATA
https://github.com/ruby/yaml/commit/5e9bfff132
2024-11-05[ruby/json] ResyncJean Boussier
Notes: Merged: https://github.com/ruby/ruby/pull/12003
2024-11-05[ruby/irb] windows does not support Process.kill("TERM", pid)YO4
(https://github.com/ruby/irb/pull/1026) https://github.com/ruby/irb/commit/7bbb885163
2024-11-04[ruby/rdoc] Display class ancestors in the sidebar #1183Alexis Bernard
https://github.com/ruby/rdoc/commit/50dda13426
2024-11-04Validate user input encodingDavid Rodríguez
If the user has the encoding of her system messed up, she may end up sending us incorrectly encoding input, causing "invalid byte sequence in UTF-8" errors at random places. These errors can be forced on a system without encoding issues with something like: ``` $ gem install$(echo -e "\xFF") foo /Users/deivid/.asdf/installs/ruby/3.2.1/lib/ruby/site_ruby/3.2.0/rubygems/config_file.rb:534:in `block in set_config_file_name': invalid byte sequence in UTF-8 (ArgumentError) from /Users/deivid/.asdf/installs/ruby/3.2.1/lib/ruby/site_ruby/3.2.0/rubygems/config_file.rb:530:in `each' from /Users/deivid/.asdf/installs/ruby/3.2.1/lib/ruby/site_ruby/3.2.0/rubygems/config_file.rb:530:in `set_config_file_name' from /Users/deivid/.asdf/installs/ruby/3.2.1/lib/ruby/site_ruby/3.2.0/rubygems/config_file.rb:177:in `initialize' from /Users/deivid/.asdf/installs/ruby/3.2.1/lib/ruby/site_ruby/3.2.0/rubygems/gem_runner.rb:71:in `new' from /Users/deivid/.asdf/installs/ruby/3.2.1/lib/ruby/site_ruby/3.2.0/rubygems/gem_runner.rb:71:in `do_configuration' from /Users/deivid/.asdf/installs/ruby/3.2.1/lib/ruby/site_ruby/3.2.0/rubygems/gem_runner.rb:33:in `run' from /Users/deivid/.asdf/installs/ruby/3.2.1/bin/gem:10:in `<main>' ``` This commit makes RubyGems print a better error in this case: ``` $ ruby -Ilib bin/gem install$(echo -e "\xFF") foo /Users/deivid/Code/rubygems/rubygems/lib/rubygems/gem_runner.rb:75:in `validate_encoding': invalid argument: 'install�' has invalid encoding (Gem::OptionParser::InvalidArgument) from /Users/deivid/Code/rubygems/rubygems/lib/rubygems/gem_runner.rb:31:in `run' from bin/gem:10:in `<main>' ```
2024-11-04[rubygems/rubygems] Fix commands with 2 MFA requests when webauthn is enabledDavid Rodríguez
If a command requires two MFA authenticated requests, and webauthn is enabled, then first one will succeed but the second one will fail because it tries to reuse the OTP code from the first request and that does not work. This happens when you have not yet logged in to rubygems.org, or when you have an API key with invalid scopes for the current operation. In that case, we need: * An API request to get a token or change scopes for the one that you have. * Another API request to perform the actual operation. Instead of trying to reuse the token, make sure it's cleared so we are asked to authenticate again. We only do this when webauthn is enabled because reusing TOPT tokens otherwise is allowed and I don't want to break that. https://github.com/rubygems/rubygems/commit/669e343935
2024-11-04[rubygems/rubygems] OTP is already added by `rubygems_api_request`David Rodríguez
https://github.com/rubygems/rubygems/commit/15930fe126
2024-11-04[rubygems/rubygems] Fix incompatible encodings errorDavid Rodríguez
https://github.com/rubygems/rubygems/commit/d478ec403f
2024-11-01[ruby/fileutils] Bump up v1.7.3Hiroshi SHIBATA
https://github.com/ruby/fileutils/commit/c138e67613
2024-11-01[ruby/json] Move State#configure back into CJean Boussier
While less nice, this open the door to eluding the State object allocation when possible. https://github.com/ruby/json/commit/5c0d428d4c
2024-10-31[rubygems/rubygems] Add useful error message for plugin loadSarah Sehr
If a plugin has previously been installed, but the path is no longer valid, `rake setup` will fail with an unexpected error due to the file not existing. Instead, we want to present the user with what the issue is and how to resolve the problem. https://github.com/rubygems/rubygems/commit/0c6ad3ecbb
2024-10-31[ruby/rdoc] Use thicker fonts with high contrast to improveStan Lo
readability (https://github.com/ruby/rdoc/pull/1197) https://github.com/ruby/rdoc/commit/7fb0e509ec
2024-10-30[rubygems/rubygems] Update `--ext=rust` to support compiling the native ↵Guilherme Carreiro
extension from source https://github.com/rubygems/rubygems/commit/9b0ec807c7
2024-10-30[rubygems/rubygems] Rely on PATH if Ruby is not installed in the same ↵David Rodríguez
directory as the binstub https://github.com/rubygems/rubygems/commit/ab7d65cc18 Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
2024-10-30[rubygems/rubygems] Simplify enable-load-relative prolog script creationDavid Rodríguez
https://github.com/rubygems/rubygems/commit/f2ed507afe
2024-10-30[rubygems/rubygems] Fix `gem update --system` leaving old default bundler ↵David Rodríguez
executables around https://github.com/rubygems/rubygems/commit/4b81add54c
2024-10-30[rubygems/rubygems] Remove confusing documentationDavid Rodríguez
The first paragraph is misleading because command line flags that set configuration are deprecated. The second one is unnecessary because configuration precedence is explained before the different configurations. https://github.com/rubygems/rubygems/commit/6cc64964ff
2024-10-30[rubygems/rubygems] Indent github workflow steps for generated gemsJerome Dalbert
https://github.com/rubygems/rubygems/commit/a1784e2efa
2024-10-29Handle all formatting configs potentially being `nil`.Jean Boussier
Fix: https://github.com/ruby/json/issues/653 I don't think this was really fully supported in the past, but it kinda worked with some of the implementations.
2024-10-26Normalize lockfile platformsDavid Rodríguez
2024-10-25[ruby/rdoc] Remove details markers in HTML documentsNobuyoshi Nakada
`summary {list-style: none;}` still does not work in Safari 18. https://github.com/ruby/rdoc/commit/c6a0a6a0d5
2024-10-24[ruby/reline] nonprinting_start and nonprinting_end should betomoya ishida
removed (https://github.com/ruby/reline/pull/771) https://github.com/ruby/reline/commit/e36441652a
2024-10-24append completion_append_character only when continous completion is … (#764)Wu
* append completion_append_character only when continous completion is not possible * refactoring * remove debug puts
2024-10-24[rubygems/rubygems] [SpecFetcher] Change < to <= like it should be.Ellen Marie Dash
https://github.com/rubygems/rubygems/commit/3d5135e69b
2024-10-24[ruby/error_highlight] Rename the `ErrorHighlight::DefaultFormatter` setting ↵Guilherme Carreiro
to `max_snippet_width` for clarity https://github.com/ruby/error_highlight/commit/e13cbd4335
2024-10-23[ruby/rdoc] Red-based darkfish color schemeStan Lo
(https://github.com/ruby/rdoc/pull/1191) * Cleanup rdoc.css * Use red as the highlight color * Use the same red as ruby-lang.org * Make main section links stand out more * Remove scrollbar styling https://github.com/ruby/rdoc/commit/f69dc470ac
2024-10-23[rubygems/rubygems] [SpecFetcher] Avoid unneeded string allocation.Ellen Marie Dash
https://github.com/rubygems/rubygems/commit/1024505d8e
2024-10-23[rubygems/rubygems] [SpecFetcher] Bail before calling available_specs()Ellen Marie Dash
https://github.com/rubygems/rubygems/commit/0719921af4
2024-10-23[rubygems/rubygems] Replace .map{...}.compact with .filter_map {...}Ellen Marie Dash
https://github.com/rubygems/rubygems/commit/18c4ea7d00
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-18 02:43:13 +0000