summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2025-04-18Revert "* remove trailing spaces. [ci skip]"v3_5_0_preview1Takashi Kokubun
This reverts commit 6062c904ae2c4d6a9fafb1a0e22841da85892eea. tompng said animation becomes weird if you remove trailing spaces. We fixed auto-style instead https://github.com/ruby/git.ruby-lang.org/commit/a8635a4cd93c8adc2e1b48b6ae8fa3fcd3bb4b34.
2025-04-17Only test on known good platforms. (#13123)Samuel Williams
Notes: Merged-By: ioquatix <samuel@codeotaku.com>
2025-04-17Prefer `th->ec` for stack base/size. (#13101)Samuel Williams
Notes: Merged-By: ioquatix <samuel@codeotaku.com>
2025-04-17* remove trailing spaces. [ci skip]git
2025-04-17Temporarily stop the trailing-space check in CIYusuke Endoh
I will restore the check after the preview release Notes: Merged: https://github.com/ruby/ruby/pull/13122
2025-04-17sample/trick2025/: adds the top-five entries of TRICK 2025Yusuke Endoh
See https://github.com/tric/trick2025 for TRICK 2025. Notes: Merged: https://github.com/ruby/ruby/pull/13122
2025-04-17Don't use admin grantHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13121
2025-04-17Use uutils-coreutilsHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13121
2025-04-17Use coreutils instead of msys2 because msys2 is not provided windows-11-armHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13121
2025-04-16[ruby/openssl] ssl: fix SSLSocket#syswrite with String-convertible objectsKazuki Yamaguchi
Correctly pass the new object assigned by StringValue() to ossl_ssl_write_internal_safe(). This is a follow-up to commit https://github.com/ruby/openssl/commit/0d8c17aa855d (Reduce OpenSSL::Buffering#do_write overhead, 2024-12-21). https://github.com/ruby/openssl/commit/3ff096196a
2025-04-16Add description about edge cases of Enumerable#sizeNARUSE, Yui
[Bug #21152]
2025-04-16Introduce `enum rb_io_mode`. (#7894)Samuel Williams
Notes: Merged-By: ioquatix <samuel@codeotaku.com>
2025-04-16rbinstall.rb: Note about `no_write` [ci skip]Nobuyoshi Nakada
Since RubyGems 3.0.0 `dir_mode` option is supported, but using `File` method to apply it, not `FileUtils`. To reduce overwriting existing methods (especially built-in class), and to record making directories, keep using `no_write` method.
2025-04-16[rubygems/rubygems] Fixed rubocop issue: Layout/SpaceInsideBlockBracesHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/77a52b011a
2025-04-16Revert advanced-security/filter-sarif update for v1.0.1Hiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13119
2025-04-16Bump up to msys2/setup-msys2 to v2.27.0Hiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13119
2025-04-16Bump up to the latest versions of actionsHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13119
2025-04-16Run the proper version of `rake`Nobuyoshi Nakada
2025-04-15[ruby/stringio] Support for `rb_io_mode_t`Samuel Williams
(https://github.com/ruby/stringio/pull/129) Companion PR to <https://github.com/ruby/ruby/pull/7894>. https://github.com/ruby/stringio/commit/2d3988e12f
2025-04-15Bump crossbeam-channel from 0.5.13 to 0.5.15 in /gc/mmtkdependabot[bot]
Bumps [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam) from 0.5.13 to 0.5.15. - [Release notes](https://github.com/crossbeam-rs/crossbeam/releases) - [Changelog](https://github.com/crossbeam-rs/crossbeam/blob/master/CHANGELOG.md) - [Commits](https://github.com/crossbeam-rs/crossbeam/compare/crossbeam-channel-0.5.13...crossbeam-channel-0.5.15) --- updated-dependencies: - dependency-name: crossbeam-channel dependency-version: 0.5.15 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Notes: Merged: https://github.com/ruby/ruby/pull/13097
2025-04-15[ruby/json] Cleanup Kernel#JSONJean Boussier
https://github.com/ruby/json/commit/573ebdca89
2025-04-15[ruby/json] Deprecate Kernel#j and Kernel#jjJean Boussier
https://github.com/ruby/json/commit/27155b6500
2025-04-15[ruby/json] Get rid of JSONError.wrapJean Boussier
https://github.com/ruby/json/commit/3e7e661ef5
2025-04-15[ruby/json] Don't create custom NaN and Infinity objects.Jean Boussier
https://github.com/ruby/json/commit/ff8e18392d
2025-04-15[rubygems/rubygems] Let `bundle lock --normalize-platforms` remove invalid ↵David Rodríguez
platforms https://github.com/rubygems/rubygems/commit/c39d2f84fd
2025-04-15[rubygems/rubygems] Raise an error if `bundle lock` target platform is ↵David Rodríguez
incompatible https://github.com/rubygems/rubygems/commit/282e4a8593
2025-04-15[rubygems/rubygems] Rename `resolution_packages` to `resolution_base`David Rodríguez
It handles resolution packages but also other stuff. https://github.com/rubygems/rubygems/commit/4baec92c20
2025-04-15[rubygems/rubygems] Extract some logic to a method and expand commentDavid Rodríguez
https://github.com/rubygems/rubygems/commit/ed31e888fd
2025-04-15[rubygems/rubygems] Clarify commentDavid Rodríguez
https://github.com/rubygems/rubygems/commit/42534e746b
2025-04-15[rubygems/rubygems] Comparing platforms is only needed for dependency validationDavid Rodríguez
If we materialized to a different platform, then the dependencies may actually be different so the validation does not really make sense. https://github.com/rubygems/rubygems/commit/68fad98e6f
2025-04-15[rubygems/rubygems] Only platforms are relevant hereDavid Rodríguez
https://github.com/rubygems/rubygems/commit/4b6f07f634
2025-04-15[rubygems/rubygems] Fix false positive warning about insecurely materialized gemDavid Rodríguez
In frozen mode, the previous logic would not set the platform locked originally in the materialized specification, and that would trigger the warning about insecure materialization incorrectly. https://github.com/rubygems/rubygems/commit/a18001e10c
2025-04-15Add a test for moving composite object partsLuke Gruber
2025-04-15`IO.select` accepts +Float::INFINITY+ as a timeout argument.Tanaka Akira
matz accepted at the developper meeting 2024-07-11.
2025-04-15Always look for the top-level RBasic in LLDB scriptsÉtienne Barrié
`rp` and other commands were broken for me because they always showed the object as a T_NONE. The reason was that instead of returning the type `struct RBasic`, FindFirstType("struct RBasic") was returning `yjit::cruby::autogened::RBasic`. Explicitly asking for the top-level RBasic by prefixing it with `::` is enough to fix those commands. Notes: Merged: https://github.com/ruby/ruby/pull/13096
2025-04-15Fix LLDB heap_page commandÉtienne Barrié
Move _append_command_output and _append_expression to LLDBInterface, and use it from HeapPageCommand after setting result. Notes: Merged: https://github.com/ruby/ruby/pull/13096
2025-04-15Lazily create `objspace->id_to_obj_tbl`Jean Boussier
This inverse table is only useful if `ObjectSpace._id2ref` is used, which is extremely rare. The only notable exception is the `drb` gem and even then it has an option not to rely on `_id2ref`. So if we assume this table will never be looked up, we can just not maintain it, and if it turns out `_id2ref` is called, we can lock the VM and re-build it. ``` compare-ruby: ruby 3.5.0dev (2025-04-10T09:44:40Z master 684cfa42d7) +YJIT +PRISM [arm64-darwin24] built-ruby: ruby 3.5.0dev (2025-04-10T10:13:43Z lazy-id-to-obj d3aa9626cc) +YJIT +PRISM [arm64-darwin24] warming up.. | |compare-ruby|built-ruby| |:----------|-----------:|---------:| |baseline | 26.364M| 25.974M| | | 1.01x| -| |object_id | 10.293M| 14.202M| | | -| 1.38x| ``` Notes: Merged: https://github.com/ruby/ruby/pull/13115
2025-04-15Rename `f_optarg` to `f_opt_arg` for consistency in parser rulesydah
Notes: Merged: https://github.com/ruby/ruby/pull/13114
2025-04-14Use call_op2 instead of call_op and tCOLON2ydah
Notes: Merged: https://github.com/ruby/ruby/pull/13113
2025-04-14Assert the GVL is held when performing various `rb_` functions.Samuel Williams
[Feature #20877] Notes: Merged: https://github.com/ruby/ruby/pull/11975
2025-04-14Expose `ruby_thread_has_gvl_p`.Samuel Williams
Notes: Merged: https://github.com/ruby/ruby/pull/11975
2025-04-14Add `RUBY_VERSION_IS_3_5`.Samuel Williams
Notes: Merged: https://github.com/ruby/ruby/pull/11975
2025-04-14Update default gems list at ad8cb532d52692fe72dea68a0aeaf4 [ci skip]git
2025-04-14[ruby/strscan] Bump versionSutou Kouhei
https://github.com/ruby/strscan/commit/7b1eb1e4ed
2025-04-14[ruby/strscan] Allow parsing strings larger than 2GiBJean byroot Boussier
(https://github.com/ruby/strscan/pull/147) For a reason unknown, even though `pos` is stored as a `long`, the `#pos` and `#pos=` treat it as an `int`, which prevent seeking into strings larger than 2GiB. https://github.com/ruby/strscan/commit/b76368416e Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
2025-04-14[rubygems/rubygems] Refine `bundle update --verbose` logsDavid Rodríguez
Don't mention "Found changes from the lockfile" because that's not really true in general. https://github.com/rubygems/rubygems/commit/0181c278e8
2025-04-14[rubygems/rubygems] Fix edge case making `bundle update` behave incorrectlyDavid Rodríguez
If both a native and a generic version are locked, but the native version is incompatible with the running Ruby, Bundler will still keep the native version in the lockfile, since it could be potentially useful when using other rubies. However, when `bundle update` is run, this was not the case because the locked native gems were not using the right source when materializing. They were using the lockfile source instead of the Gemfile source, and that meant they could not be found when materializing, because the lockfile source always uses local mode so does not see them. The effect of this was normally that they were incorrectly removed from the lockfile and a strange "this spec has been possibly yanked" was printed in verbose mode. However, in certain situations (i.e., when the generic gem would bring extra dependencies), it could also make `bundle update` crash. The solution is, when adding this extra locked specs to the result after resolving, maybe sure they inherit the source from the resolved specs, so they can be found when materializing. `bundle install` did not have the issue because it passes locked specs to the resolver, and assigns the right source to them in `Definition#converge_locked_specs`. https://github.com/rubygems/rubygems/commit/91ce881fda
2025-04-14[rubygems/rubygems] Materialize specs just once in installerDavid Rodríguez
`Definition#specs` does the same thing but memoizes the result. https://github.com/rubygems/rubygems/commit/b62bf9fe41
2025-04-14[rubygems/rubygems] Fix `bundle lock --normalize-platforms` regressionDavid Rodríguez
https://github.com/rubygems/rubygems/commit/458fa5dc4c
2025-04-14Update bundled gems list at f65aad61f7c2b5ff15d10be9264d3b [ci skip]git
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-21 07:31:45 +0000