summaryrefslogtreecommitdiff
path: root/include/ruby/assert.h
diff options
context:
space:
mode:
authorDavid Rodríguez <deivid.rodriguez@riseup.net>2020-02-03 18:48:44 +0100
committerHiroshi SHIBATA <hsbt@ruby-lang.org>2020-02-06 21:57:17 +0900
commit054d99d95bc9d3c9481be3ea97dd16b39a4ba5bd (patch)
tree38b20cc1678baf26151a0783bc160f55c0002d2f /include/ruby/assert.h
parente323f50a9c71da2804f66ba6345ef071def60e1e (diff)
[rubygems/rubygems] Allow releasing with a rubygems pre version
This condition is too restrictive in my opinion. If a user has a pre version of rubygems installed, she should be fully responsible for it, and we shouldn't restrict any functionality. Also, why is a new prerelease disallowed but an old prelease allowed, or why is 2.0.0.rc2 explictly whitelisted? I believe this kind of exceptions are one more reason to actually permit this. https://github.com/rubygems/rubygems/commit/7f77a77620
Diffstat (limited to 'include/ruby/assert.h')
0 files changed, 0 insertions, 0 deletions