| Age | Commit message (Collapse) | Author |
|
|
|
(https://github.com/ruby/erb/pull/91)
https://github.com/ruby/erb/commit/6bceee7d6e
|
|
|
|
https://github.com/ruby/resolv/commit/31a393e96c
|
|
v0.8.0 is mistake of release workflow. This version is same as v0.7.0
https://github.com/ruby/optparse/commit/9a467d10d4
|
|
https://github.com/ruby/optparse/commit/a394ca4878
|
|
https://github.com/ruby/optparse/commit/94de48b47e
|
|
https://github.com/ruby/net-http/commit/ec9c70a6fb
|
|
https://github.com/ruby/uri/commit/c41903b3e4
|
|
https://github.com/ruby/uri/commit/1c6e81b721
|
|
Currently, some methods' behavior(e.g. `URI.parse`) don't change
when switching a parser. This is because some methods use
`DEFAULT_PARSER`, but `parser=` doesn't change `DEFAULT_PARSER`.
This PR introduces a constant to keep a parser's instance and
change it when switching a parser. Also, change to use it in
methods.
https://github.com/ruby/uri/commit/aded210709
|
|
URI::RFC2396_PARSER.escape
https://github.com/ruby/uri/commit/72e7d6b364
|
|
from that
https://github.com/ruby/uri/commit/1fc4f0496a
|
|
https://github.com/ruby/English/commit/c921886aaf
|
|
In the case of attribute writes, there are use cases where you want
to know the location of the = sign. (Internally we actually need
this for translation to the writequark AST.)
https://github.com/ruby/prism/commit/bfc798a7ec
|
|
wrong kwargs
This commit fixes the case when there are multiple missing or incorrect
keywords provided to a method. Without this fix, ErrorHighlight itself
will raise an exception
https://github.com/ruby/error_highlight/commit/8bde92b36e
|
|
https://github.com/ruby/fileutils/commit/29de582f68
|
|
https://github.com/ruby/timeout/commit/f42b47d383
|
|
https://github.com/ruby/rubygems/commit/e9bd59699c
|
|
https://github.com/ruby/rubygems/commit/6fbbde48e2
|
|
https://github.com/ruby/rubygems/commit/15e46a3a68
|
|
https://github.com/ruby/rubygems/commit/55745ee0f8
|
|
https://github.com/ruby/rubygems/commit/62ba34d6c9
|
|
Prompt wording "prefer safe, respectful, productive, and collaborative spaces" is copied verbatim from Ruby Community Conduct Guideline.
https://github.com/ruby/rubygems/commit/6cdf5f6d8a
|
|
https://github.com/ruby/erb/commit/e8d382a83e
|
|
https://github.com/ruby/erb/commit/daa0e8712f
|
|
https://github.com/ruby/rubygems/commit/b2e1810067
|
|
https://github.com/ruby/rubygems/commit/687ffd7265
|
|
* See https://bugs.ruby-lang.org/issues/21640#note-16
|
|
Use array_of_integer.sort! instead of buble-sort-like algorithm
|
|
with bundle console
https://github.com/ruby/rubygems/commit/42e22fd367
|
|
https://github.com/ruby/rubygems/commit/bc77ec0bf2
|
|
https://github.com/ruby/rubygems/commit/1ba8eb4ab3
|
|
tool and configurations
https://github.com/ruby/rubygems/commit/749b498822
|
|
https://github.com/ruby/rubygems/commit/c637007e91
|
|
https://github.com/ruby/English/commit/5e60c1068a
|
|
https://github.com/ruby/English/commit/70b46b58cc
|
|
https://github.com/rubygems/rubygems/commit/9b3a5a8ae9
|
|
#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
|
|
https://github.com/ruby/ipaddr/commit/c96dbadee3
|
|
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
|
|
https://github.com/ruby/prism/commit/dda0dc81df
|
|
https://github.com/ruby/prism/commit/2466940e49
|
|
https://github.com/ruby/prism/commit/b72fcc6183
|
|
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
|
|
- ### 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
|
|
https://github.com/rubygems/rubygems/commit/6a3342541a
|
|
https://github.com/rubygems/rubygems/commit/89bcdfc941
|
|
https://github.com/rubygems/rubygems/commit/15be905c44
|
|
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>
|