| Age | Commit message (Collapse) | Author |
|
By providing a 'changelog_uri' in the metadata of the gemspec
a 'Changelog' link will be shown on https://rubygems.org/gems/timeout
which makes it quick and easy for someone to check on the changes
introduced with a new version.
Details of this functionality can be found on https://guides.rubygems.org/specification-reference/
https://github.com/ruby/timeout/commit/47a6f0313b
|
|
https://github.com/ruby/timeout/commit/301ad4cfdc
|
|
By providing a 'changelog_uri' in the metadata of the gemspec
a 'Changelog' link will be shown on https://rubygems.org/gems/net-protocol
which makes it quick and easy for someone to check on the changes
introduced with a new version.
Details of this functionality can be found on https://guides.rubygems.org/specification-reference/
https://github.com/ruby/net-protocol/commit/46e78a2a0a
|
|
By providing a 'changelog_uri' in the metadata of the gemspec
a 'Changelog' link will be shown on https://rubygems.org/gems/base64
which makes it quick and easy for someone to check on the changes
introduced with a new version.
Details of this functionality can be found on https://guides.rubygems.org/specification-reference/
https://github.com/ruby/base64/commit/7cab043d67
|
|
https://github.com/rubygems/rubygems/commit/73f1609715
|
|
Not wrapping to_lock since access to it is single threaded and
read-only at the time of writing the lockfile.
https://github.com/rubygems/rubygems/commit/3b53aa1b12
|
|
https://github.com/ruby/rdoc/commit/6231b03476
|
|
Constant definitions using these functions have been supported, but
since RDoc::Parser::C#gen_const_table did not consider other than
`rb_define_const` the documents for them have not been found, without
`Document-const` direvtive.
Fixes https://github.com/ruby/rdoc/issues/1067
https://github.com/ruby/rdoc/commit/cdad51a60b
|
|
https://github.com/ruby/optparse/commit/324ff21f04
|
|
|
|
https://github.com/ruby/set/commit/d6cab5bcc8
|
|
https://github.com/ruby/set/commit/c63047c2ce
|
|
https://github.com/ruby/set/commit/32a9689696
|
|
https://github.com/ruby/set/commit/64dad673d8
|
|
When $stderr is redirected, you'll have no way to see why RJIT got
broken. This reference must always be the actual stderr.
|
|
|
|
This is more convenient for accessing those fields.
|
|
|
|
|
|
comptime_key is a Ruby object and the value is not valid in machine code.
This PR also implements `CMP r/m64, imm32 (Mod 01: [reg]+disp8)` that is
now needed for running mail.gem benchmark.
|
|
|
|
|
|
local_idx should not be overwritten.
|
|
|
|
Creating a backtrace can crash if RJIT is triggered by branch_stub_hit.
In that case, it's useful to at least print the error message.
|
|
(https://github.com/ruby/irb/pull/818)
https://github.com/ruby/irb/commit/7421359b92
|
|
(https://github.com/ruby/irb/pull/812)
* Change indexes.rdoc to indexes.md
* Change indexes.rdoc to indexes.md
* Change indexes.rdoc to indexes.md
https://github.com/ruby/irb/commit/b1cd53cbf7
|
|
(https://github.com/ruby/irb/pull/817)
1. Because `IRB.rc_file` always generates an rc file name, even if the
file doesn't exist, we should check the file exists before trying to
load it.
2. If any type of errors occur while loading the rc file, we should
warn the user about it.
https://github.com/ruby/irb/commit/37ffdc6b19
|
|
This significantly reduces retained objects on RJIT.
|
|
|
|
|
|
|
|
https://github.com/ruby/readline/commit/7dbc5bd8d9
|
|
https://github.com/ruby/readline/commit/6e1e5d0eb8
|
|
(https://github.com/ruby/reline/pull/612)
https://github.com/ruby/reline/commit/8937279e0f
|
|
https://github.com/ruby/ipaddr/commit/247459faa5
|
|
https://github.com/ruby/abbrev/commit/b362e8e3b9
|
|
https://github.com/ruby/securerandom/commit/890d659970
|
|
https://github.com/ruby/open3/commit/b890922205
|
|
https://github.com/ruby/rdoc/commit/895f1affc0
|
|
|
|
Refactor vendoring to allow validating vendoring is reproducible
Helps ensure that unsuspecting diffs to the vendored code arent accidentally introduced
|
|
https://github.com/rubygems/rubygems/commit/966daf7d42
|
|
Previous attempt to use a full path when the running version is
different than the one that would be activated by default are different
was not correct.
This is because if this error happens in a `bundle exec` context, the
`Gem.loaded_specs` is cleared because we're in an exec'd process, so
will be always using a full path in these cases.
This alternative approach should do what I was expecting.
https://github.com/rubygems/rubygems/commit/e0bb8bf51b
|
|
https://github.com/rubygems/rubygems/commit/f6258e5679
Co-authored-by: AndrewSwerlick <andrew.swerlick@gmail.com>
|
|
https://github.com/rubygems/rubygems/commit/73f1609715
|
|
Not wrapping to_lock since access to it is single threaded and
read-only at the time of writing the lockfile.
https://github.com/rubygems/rubygems/commit/3b53aa1b12
|
|
https://github.com/rubygems/rubygems/commit/79636dec12
|
|
Small refactor, no functional change
https://github.com/rubygems/rubygems/commit/5edb7a1026
|
|
https://github.com/ruby/rdoc/commit/f7dd147a8c
|