Age | Commit message (Collapse) | Author |
|
This reverts commit https://github.com/ruby/net-http/commit/a7cb30124cf1.
This is causing errors in Ruby's CI, will revert for now and
try again after testing a fix with Ruby's CI.
https://github.com/ruby/net-http/commit/7b852b1feb
|
|
Previously, the content-encoding header was removed and the body
was modified, but the content-length header was not modified,
resulting in the content-length header not matching the body
length.
Fixes [Bug #16672]
https://github.com/ruby/net-http/commit/a7cb30124c
|
|
https://github.com/ruby/net-protocol/commit/9cf40af499
|
|
https://github.com/ruby/ostruct/commit/ce879e56cf
|
|
defined?(yield) bypasses the block_given? method (or any aliases
to it) and always does the right thing.
https://github.com/ruby/ostruct/commit/4c38fe612e
|
|
scope changes
In https://github.com/rubygems/rubygems/pull/4152 `bundle config` was changed
to default to local scope (instead of global) if the command was executed
from inside an application directory.
Updated documentation reflects this change.
https://github.com/rubygems/rubygems/commit/d92d42cae5
|
|
https://github.com/ruby/ostruct/commit/fe19de4644
|
|
https://github.com/ruby/ostruct/commit/14d04ff694
|
|
This is hiding a real bundler issue as a "network error". It's more
helpful to get a proper bug report, with stack trace and so on.
So stop re-raising errors when evaluating unmarshaled responses as
network errors, and only raise Marshal errors when the Marshal format is
invalid, not whenever marshalled gemspecs can't be loaded because that
may hide actual client errors, like missing `YAML` constants.
https://github.com/rubygems/rubygems/commit/05ea907e1c
|
|
https://github.com/ruby/rdoc/commit/f9f90ef2ff
|
|
https://github.com/ruby/rdoc/commit/b7b4cdab6c
|
|
https://github.com/ruby/rdoc/commit/1bb0496c53
|
|
https://github.com/ruby/rdoc/commit/7736d3a89c
|
|
Empty class documents are generated even with `:stopdoc:`.
|
|
https://github.com/ruby/logger/commit/c4a4155ab7
|
|
Enable `-Werror=implicit-function-declaration` by default for
building C extensions for early failures.
|
|
- `www.ruby-lang.org` links to `./www.ruby-lang.org`
- `cgi['field_name']` links to `./'field_name'`
|
|
Properly set the name of `File::Constants`, which is the only name
with a namespace in `RDoc::KNOWN_CLASSES`, and fixes longstanding bug
that `File::Constants` becomes `File::File::Constants`.
When it is generated by `rb_file_const` in dir.c, `name` is set to the
qualified name as same as `full_name`, and generated in the normal way
in file.c later, already set `full_name` is cleared and `name` will be
constructed from the enclosing namespace and the `name`. It will
results in duplicated namespace, `File::File::Constants`.
https://github.com/ruby/rdoc/commit/3a8d6df562
|
|
https://github.com/rubygems/rubygems/commit/3e06a91435
|
|
Other code must not be between the doc and class definition.
https://github.com/rubygems/rubygems/commit/366784aae5
|
|
See
https://docs.github.com/es/actions/learn-github-actions/environment-variables#default-environment-variables.
So that we can show stats about it at https://ecosystem.rubytogether.org
https://github.com/rubygems/rubygems/commit/48d6dc68f8
|
|
If this is at the top level, it stops the documentation of the
entire module, but not only the part in this file.
https://github.com/rubygems/rubygems/commit/34e8c1ee06
|
|
The note
> Raises an ArgumentError if the given +orig+ is immutable, such as Symbol,
> Integer, or Float.
has not been true since #2313 (GH-2313, Feature #16035) when
@casperisfine enabled storing non-finalizable objects in the underlying
`ObjectSpace::WeakMap`.
On Ruby 2.7+, `WeakRef.new(1) + 1` works fine and the result is the
expected 2.
Notes:
Merged: https://github.com/ruby/ruby/pull/5657
|
|
|
|
https://github.com/ruby/rdoc/commit/6bb93001db
|
|
https://github.com/ruby/rdoc/commit/4c7c46fcc4
|
|
If this is at the top level, it stops the documentation of the
entire module, but not only the part in this file.
https://github.com/ruby/forwardable/commit/34cd2ac4a1
|
|
If this is at the top level, it stops the documentation of the
entire module, but not only the part in this file.
https://github.com/ruby/irb/commit/86c41b06ad
|
|
https://github.com/ruby/rdoc/commit/acb91ea74a
|
|
https://github.com/ruby/rdoc/commit/23e61a208e
|
|
|
|
This change makes the sidebar scrollable via `position: sticky` and `overflow: auto`;
See also <https://caniuse.com/?search=sticky>
https://github.com/ruby/rdoc/commit/4d52e24840
|
|
For example, consider the following markup:
C1#m(a, b)
Before this patch, it generated this HTML:
<p><a href=\"C1.html#method-i-m\"><code>C1#m</code></a>(a, b)</p>
Which places the method arguments outside of the link.
Now it generates this HTML:
<a href=\"C1.html#method-i-m\"><code>C1#m(a, b)</code></a>
https://github.com/ruby/rdoc/commit/05a2b2222b
|
|
is missing
When I run bundle install with BUNDLE_DEPLOYMENT=true in the environment
on a different platform than I usually do development, I get the
following output to the console (wrapped exactly as shown):
Your bundle only supports platforms ["x86_64-darwin-19"] but your local platform
is x86_64-linux. Add the current platform to the lockfile with `bundle lock
--add-platform x86_64-linux` and try again.
Because the way the message wraps, its not as simple as copying the
suggested command to the clipboard because it contains a newline:
$ bundle lock
Writing lockfile to [...]/Gemfile.lock
$ --add-platform x86_64-linux
Adding a newline right before the command forces the command in the
error message to be on the same line, which facilitates copy-pasting the
command in the message.
https://github.com/rubygems/rubygems/commit/4cf6989b11
|
|
(https://github.com/ruby/ostruct/pull/39)
This gem exposes no executables.
https://github.com/ruby/ostruct/commit/a1242f7ebe
|
|
https://github.com/ruby/ostruct/commit/322efd0e61
|
|
https://github.com/ruby/ostruct/commit/7258535073
|
|
Reduce the number of steps required to install a gem from two steps to one by using `bundle add`
https://github.com/rubygems/rubygems/commit/2c968420cd
|
|
consistent
Previously they had slightly different behavior when combined with
conservative updating flags.
The correct behavior is the `--update-strict` option, so `--script` now
does that, The `--update-strict` option is left there for now but I will
deprecate it later.
https://github.com/rubygems/rubygems/commit/ab42046229
|
|
https://github.com/ruby/cgi/commit/734dfdf1b4
|
|
https://github.com/ruby/rdoc/commit/135198a31c
|
|
https://github.com/ruby/securerandom/commit/62ca2828f3
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5606
|
|
The existing implementation, given the below .inputrc, erroneously
creates a "C-v" key binding:
set keymap emacs-ctlx
"\C-v": "[C-x C-v was pressed]"
This fixes it to instead create a "C-x C-v" keybinding.
https://github.com/ruby/reline/commit/719f52d231
|
|
RDoc is using only CGI.escape, escapeHTML, and unescape.
We don't have to load the whole source code of cgi gem.
https://github.com/ruby/rdoc/commit/d096222cc2
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5563
|
|
Random.urandom raises a RuntimeError if it is unavailable.
[Bug #13885]
Notes:
Merged: https://github.com/ruby/ruby/pull/5557
|
|
So that the generated `.rdoc_options` file is loadable.
https://github.com/ruby/rdoc/commit/6cf6e1647b
|