Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Rubygems 2.2.2 prints the changelog from 2.2.1 #814

Closed
indirect opened this Issue Feb 6, 2014 · 4 comments

Comments

Projects
None yet
3 participants
Owner

indirect commented Feb 6, 2014

$ gem update --system 2.2.2
Updating rubygems-update
Fetching: rubygems-update-2.2.2.gem (100%)
Successfully installed rubygems-update-2.2.2
Installing RubyGems 2.2.2
RubyGems 2.2.2 installed

=== 2.2.1 / 2014-01-06

Bug fixes:

* Platforms in the Gemfile.lock GEM section are now handled correctly.  Bug
  #767 by Diego Viola.
* RubyGems now displays which gem couldn't be uninstalled from the home
  directory.  Pull request #757 by Michal Papis.
* Removed unused method Gem::Resolver#find_conflict_state.  Pull request #759
  by Smit Shah.
* Fixed installing gems from local files without dependencies.  Issue #760 by
  Arash Mousavi, pull request #764 by Tim Moore.
* Removed TODO about syntax that works in Ruby 1.8.7.  Pull request #765 by
  Benjamin Fleischer.
* Switched Gem.ruby_api_version to use RbConfig::CONFIG['ruby_version'] which
  has the same value but is overridable by packagers through
  --with-ruby-version= when configuring ruby.  Bug #770 by Jeremy Evans.
* RubyGems now prefers the bundler API for `gem install` to reduce HTTP
  requests.  (This change was intended for RubyGems 2.2.0 but was missed.)
  This should address bug #762 by Dan Peterson and bug #766 by mipearson.
* Added Gem::BasicSpecification#source_paths so documentation or analysis
  tools can work properly as require_paths no longer returns extension source
  directories.  Bug #758 Vít Ondruch.
* Gem.read_binary can read read-only files again.  This caused file://
  repositories to stop working.  Bug #761 by John Anderson.
* Fixed specification file sorting for Ruby 1.8.7 compatibility.  Pull
  request #763 by James Mead

Owner

drbrain commented Feb 6, 2014

What version did you upgrade from?

Owner

indirect commented Feb 6, 2014

I think it was 2.2.1, but I'm not positive.

On Thu, Feb 6, 2014 at 8:43 PM, Eric Hodel notifications@github.com
wrote:

What version did you upgrade from?

Reply to this email directly or view it on GitHub:
#814 (comment)

If the tests are to be believed this is desired behaviour.

This test doesn't test for the most recent set of release notes but instead tests for all release notes from the previous version (inclusive) up to but not including the installed version. If you were to add another release between 2.0.2 and Gem::Version it too would be part of the release notes.

Here is where the most recent release is being removed.

I'll gladly submit a PR if the behaviour should be different.

@ghost

ghost commented Feb 12, 2014

I can reproduce this bug:

➜  ~  gem -v
2.2.2
➜  ~  gem update --system 2.2.1
Updating rubygems-update
Successfully installed rubygems-update-2.2.1
Installing RubyGems 2.2.1
RubyGems 2.2.1 installed



------------------------------------------------------------------------------

RubyGems installed the following executables:
        /Users/robert/.rubies/ruby-2.1.0/bin/gem

RubyGems system software updated
➜  ~  gem -v
2.2.1
➜  ~  gem update --system
Updating rubygems-update
Successfully installed rubygems-update-2.2.2
Installing RubyGems 2.2.2
RubyGems 2.2.2 installed

=== 2.2.1 / 2014-01-06

Bug fixes:

* Platforms in the Gemfile.lock GEM section are now handled correctly.  Bug
  #767 by Diego Viola.
… <snip>
RubyGems system software updated
➜  ~  gem -v
2.2.2

@drbrain drbrain added this to the 2.3 milestone Feb 12, 2014

@drbrain drbrain closed this in f235c4a Feb 12, 2014

@zzak zzak added a commit to zzak/rubygems that referenced this issue May 9, 2014

@drbrain @zzak drbrain + zzak Fix "coding:" detection for release notes
The regular expression used would capture the first "=" of the first
history entry which contained the latest release notes.  This has been
corrected to not consume anything beyond the header text.

Fixes #814
b77710e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment