f24a86d83f
util/rubocop -A --only Layout/EmptyLineAfterMagicComment
2023-03-23 17:18:49 +09:00
4dd418f877
util/rubocop -A --only Style/FrozenStringLiteralComment
2023-03-23 17:18:49 +09:00
583fbc627c
[rubygems/rubygems] util/rubocop -A --only Layout/EmptyLinesAroundModuleBody
...
https://github.com/rubygems/rubygems/commit/48c88466b7
2023-03-17 18:50:55 +09:00
3926ad578c
[rubygems/rubygems] Drop to support Psych 3.0 bundled at Ruby 2.5
...
https://github.com/rubygems/rubygems/commit/a6650c2c96
2023-03-09 13:37:06 +00:00
d7ffd3fea4
RubyGems: Enable Style/StringLiterals cop
...
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
2022-07-22 12:07:23 +09:00
d22511fd75
Merge rubygems/rubygems HEAD.
...
Picked at 12aeef6ba9a3be0022be9934c1a3e4c46a03ed3a
2022-01-19 15:01:44 +09:00
88e46cf6b8
[rubygems/rubygems] Remove all `syck` traces from `rubygems`
...
After reading [this blog
post](https://blog.rubygems.org/2011/08/31/shaving-the-yaml-yak.html ),
published almost 10 years ago already, my understanding is that this
problem could come up in two ways:
* Rubygems.org serving corrupted gemspecs". As far as I understand this
was fixed in rubygems.org a lot time ago, since
https://github.com/rubygems/rubygems.org/pull/331 .
* Clients having a ten years old gemspec cache with some of these bad
gemspecs. In this case, there's no easy solution but I think ten years
is enough and rebuilding the cache should do the trick.
So, I think it's time we remove this.
https://github.com/rubygems/rubygems/commit/afcb15d556
2021-07-27 09:25:56 +09:00
ba9dcdab36
[rubygems/rubygems] Enable Style/PercentLiteralDelimiters cop in rubygems
...
So it matches the style used by bundler.
https://github.com/rubygems/rubygems/commit/ab0580fd65
2020-03-30 12:42:10 +09:00
5335ce0e06
Merge master branch from rubygems/rubygems upstream.
...
* Enable Style/MethodDefParentheses in Rubocop
https://github.com/rubygems/rubygems/pull/2478
* Enable Style/MultilineIfThen in Rubocop
https://github.com/rubygems/rubygems/pull/2479
* Fix required_ruby_version with prereleases and improve error message
https://github.com/rubygems/rubygems/pull/2344
* Fix bundler rubygems binstub not properly looking for bundler
https://github.com/rubygems/rubygems/pull/2426
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65904 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-21 10:20:47 +00:00
6268098208
Make rubygems follow the upstream of psych
...
And merge psych again.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65659 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-11 00:20:27 +00:00
615ac35934
Merge rubygems master branch from github.com/rubygems/rubygems.
...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65294 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-22 00:27:02 +00:00
8ea464a9c1
Support keyword arguments with Pysch.safe_load provided by after Psych 3.1.0.pre1.
...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65192 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-20 02:51:09 +00:00
9e475eef86
Merge release version of Rubygems 2.7.0.
...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@60608 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-11-02 04:25:37 +00:00
500f15e507
Merge rubygems-2.6.14 changes.
...
It fixed http://blog.rubygems.org/2017/10/09/unsafe-object-deserialization-vulnerability.html
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@60149 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2017-10-10 08:58:22 +00:00
Hiroshi SHIBATA
Takuya Noguchi
David Rodríguez
hsbt
nobu