# coding: UTF-8
1.8.11 / 2011-10-03
- Bug fix:
- Deprecate was moved to Gem::Deprecate to stop polluting
the top-level namespace.
1.8.10 / 2011-08-25
RubyGems 1.8.10 contains a security fix that prevents malicious gems from
executing code when their specification is loaded. See github.com/rubygems/rubygems/pull/165
for details.
- 5 bug fixes:
- RubyGems escapes strings in ruby-format specs using dump instead of to_s
and %q to prevent code injection. Issue 165 by Postmodern
- RubyGems attempt to activate the psych gem now to obtain bugfixes from
psych.
- Gem.dir has been restored to the
front of Gem.path. Fixes
remaining problem with Issue 115
- Fixed Syck DefaultKey infecting ruby-format specifications.
- `gem uninstall a b` no longer stops if gem "a" is not installed.
1.8.9 / 2011-08-23
- Bug fixes:
- Fixed uninstalling multiple gems using `gem uninstall`
- Gem.use_paths splatted to take
multiple paths! Issue 148
1.8.8 / 2011-08-11
- Bug fix:
- The encoding of a gem‘s YAML spec is now UTF-8. Issue 149
1.8.7 / 2011-08-04
- Bug fixes:
- Added missing require for `gem uninstall —format-executable`
- The correct name of the executable being uninstalled is now displayed with
—format-executable
- Fixed `gem unpack uninstalled_gem` default version picker
- RubyGems no longer claims a nonexistent gem can be uninstalled
- `gem which` no longer claims directories are requirable files
- `gem cleanup` continues cleaning up gems if one can‘t be uninstalled
due to permissions. Issue 82
- Gem repository directories are no longer
created world-writable. Patch by Sakuro OZAWA. Ruby Bug 4930
1.8.6 / 2011-07-25
- 1 minor enhancement:
- Add autorequires and delay startup of RubyGems until require is called. See
Ruby bug 4962
- 9 bug fixes:
- Restore behavior of Gem::Specification#loaded? Ruby Bug 5032
- Clean up SourceIndex.add_specs to not be so damn noisy. (tadman)
- Added missing APPLE_GEM_HOME in paths.
- Extend YAML::Syck::DefaultKey fixing to `marshal_dump` as well.
- Fix 29216: check correct bin_dir in check_that_user_bin_dir_is_in_path.
- Revert Gem.latest_load_paths to
working order (PathSupport revert).
- Restore normalization of GEM_HOME.
- Handle the Syck DefaultKey problem once and for all.
- Fix SystemStackError occurring with "gem list -r -a" on 1.9.
1.8.5 / 2011-05-31
- 2 minor enhancement:
- The -u option to ‘update local source cache’ is official
deprecated.
- Remove has_rdoc deprecations from Specification.
- 2 bug fixes:
- Handle bad specs more gracefully.
- Reset any Gem paths changed in the
installer.
1.8.4 / 2011-05-25
- 1 minor enhancement:
- Removed default_executable deprecations from Specification.
1.8.3 / 2011-05-19
- 4 bug fixes:
- Fix independent testing of test_gem_package_tar_output. Ruby Bug 4686 by
Shota Fukumori
- Fix test failures for systems with separate ruby versions. Ruby Bug 3808 by
Jeremy Evans
- Fixed some bad calls left behind after rolling out some refactorings.
- Syck has a parse error on (good) times output from Psych. (dazuma, et al)
1.8.2 / 2011-05-11
- 2 minor enhancements:
- Moved outdated from OutdatedCommand to Specification (for Isolate).
- Print out a warning about missing executables.
- 3 bug fixes:
- Added missing requires to fix various upgrade issues.
- `gem pristine` respects multiple gem repositories.
- setup.rb now execs with —disable-gems when possible
1.8.1 / 2011-05-05
- 1 minor enhancement:
- Added Gem::Requirement#specific? and Gem::Dependency#specific?
- 4 bug fixes:
- Typo on Indexer rendered it useless on Windows
- gem dep can fetch remote dependencies for non-latest gems again.
- gem uninstall with multiple versions no longer crashes with ArgumentError
- Always use binary mode for File.open to keep Windows happy
1.8.0 / 2011-04-34
This release focused on properly encapsulating functionality. Most of this
work focused on moving functionality out of Gem::SourceIndex and Gem::GemPathSearcher into Gem::Specification where it
belongs.
After installing RubyGems 1.8.0 you will see deprecations when loading your
exsting gems. Run `gem pristine —all —no-extensions` to
regenerate your gem specifications safely.
Currently RubyGems does not save the build arguments used to build gems
with extensions. You will need to run `gem pristine gem_with_extension
—