diff options
| author | nagachika <nagachika@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2019-02-05 12:15:47 +0000 |
|---|---|---|
| committer | nagachika <nagachika@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2019-02-05 12:15:47 +0000 |
| commit | 9b80483fc832267ed733b1e239d5be1869414b08 (patch) | |
| tree | bd55db0282999aadfbd91467cc9c36f5eb357d4a /version.h | |
| parent | 63d9ab33fe419167382fc03be2c00413a78c05cb (diff) | |
merge revision(s) 66867: [Backport #15500]
Revert r58345 and r58371.
These changes break the behavior of default gems. Bug #13428 says
r58345 is reasonable because gemspec file is installed by `to_ruby_for_cache`
method. But I revert `to_ruby_for_cache` in rbinstall.rb at r58403.
There is no reason that we apply r58345 now.
But I'm not sure about gemspec of default gems affects standalone gems.
I'm going to investigate it on rubygems/rubygems.
[Bug #15500][ruby-core:90867]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_5@67013 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'version.h')
| -rw-r--r-- | version.h | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -1,10 +1,10 @@ #define RUBY_VERSION "2.5.4" -#define RUBY_RELEASE_DATE "2019-01-23" -#define RUBY_PATCHLEVEL 138 +#define RUBY_RELEASE_DATE "2019-02-05" +#define RUBY_PATCHLEVEL 139 #define RUBY_RELEASE_YEAR 2019 -#define RUBY_RELEASE_MONTH 1 -#define RUBY_RELEASE_DAY 23 +#define RUBY_RELEASE_MONTH 2 +#define RUBY_RELEASE_DAY 5 #include "ruby/version.h" |