Skip to content

Commit 0c4b0ae

Browse files
authored
Remove date field from rake.gemspec
Hi there 👋 I noticed that in [this commit](6258ad5) you bumped the version but did not change the `date` field in the `rake.gemspec`. This means that on rubygems.org, Rake 12.2.1 and Rake 12.3.0 were seemingly released on the same day, but the commits show a different history. (The last released date was [this commit](e7ea2d1) but it has since been bumped on master with [this commit](0c4aab8). May I suggest removing the `date` field from the `gemspec`? This way, RubyGems.org will automatically assign the current date to the package's release _and_ it means that you as a maintainer will have to do one less thing every time you release a new version. We do not have a `date` field in the [`i18n` gem's `gemspec`](https://github.com/svenfuchs/i18n/blob/master/i18n.gemspec) and it works just fine. What do you think?
1 parent 109dd0e commit 0c4b0ae

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

rake.gemspec

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ require 'rake/version'
55
Gem::Specification.new do |s|
66
s.name = "rake".freeze
77
s.version = Rake::VERSION
8-
s.date = "2017-11-15"
98
s.authors = ["Hiroshi SHIBATA".freeze, "Eric Hodel".freeze, "Jim Weirich".freeze]
109
s.email = ["hsbt@ruby-lang.org".freeze, "drbrain@segment7.net".freeze, "".freeze]
1110

0 commit comments

Comments
 (0)