Release pushed without code/changelog?

[viraptor]

There's a new release available at https://rubygems.org/gems/domain_name/versions/0.5.20190701
but the code for it doesn't seem to exist in the repo (and there's no changelog update)

Please check if this is a valid published version. (and update the repo if it is)

[rwojnarowski]

If you download gem from rubygems, there is new changelog for this version:

## [v0.5.20190701](https://github.com/knu/ruby-domain_name/tree/v0.5.20190701) (2019-07-05)
[Full Changelog](https://github.com/knu/ruby-domain_name/compare/v0.5.20180417...v0.5.20190701)

- Update the eTLD database to 2019-07-01 18:45:50 UTC

Changed files:

M       ./.document
M       ./.gitignore
M       ./.travis.yml
M       ./CHANGELOG.md
M       ./Gemfile
M       ./LICENSE.txt
M       ./README.md
M       ./Rakefile
M       ./data/public_suffix_list.dat
D       ./diff
M       ./domain_name.gemspec
M       ./lib/domain_name/etld_data.rb
M       ./lib/domain_name/etld_data.rb.erb
M       ./lib/domain_name/punycode.rb
M       ./lib/domain_name/version.rb
M       ./lib/domain_name.rb
M       ./test/helper.rb
M       ./test/test_domain_name-punycode.rb
M       ./test/test_domain_name.rb

it's seems like github repo is not up to date with rubygems pushed version

[baburdick]

Given what just happened with strong_password, this should be considered a bad practice. In fact, rubygems probably shouldn't allow pushing a new gem version without the public repo having a matching tag with the same hash.

[zbelzer]

I see the tags have been pushed now. Thanks!