Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Nov 17, 2014
  1. @hsbt

    Merge pull request #1035 from hsbt/remove-useless-variables

    hsbt authored
    Removed useless assignment variables
  2. @hsbt

    Merge pull request #1061 from rubygems/backport-r48265

    hsbt authored
    backport r48265 without to using refinements
Commits on Nov 14, 2014
  1. @hsbt
Commits on Nov 12, 2014
  1. @drbrain

    Set release date and version

    drbrain authored
  2. @drbrain

    Add staging to CA certificate checker

    drbrain authored
    Also show which certificate each URL needs
    Also warn when overwriting an existing certificate (even though git
Commits on Nov 11, 2014
  1. @luislavena

    Update History.txt with recent changes

    luislavena authored
    Missed include details in past commits. I'm getting rusty at OSS...
  2. @luislavena

    Update Manifest.txt

    luislavena authored
    Reflect latest changes in certs.
  3. @luislavena

    Add Root CA with SHA1 signature

    luislavena authored
    This is required for some versions of OpenSSL having trouble
    to establish and verify the new certificates for
    SHA-1-based signatures for trusted root certificates are not a
    problem because TLS clients trust them by their identity, rather
    than by the signature of their hash.
  4. @luislavena

    Remove COMODO intermediate certificates

    luislavena authored
    Root certificates are the ones that matters in this scenario.
  5. @hsbt
  6. @hsbt
  7. @drbrain

    Update Manifest

    drbrain authored
  8. @drbrain
  9. @drbrain

    Add CA roots for upcoming cert change

    drbrain authored
    We need to deploy a new server certificate as Google Chrome no longer
    trusting SHA-1-signed certificates:
    In order to avoid interruption of service users will need the updated
    root certificates to verify the new server certificate.  Users may be
    able to install these certificates by hand into their OpenSSL
    certificates pem as well.
Commits on Nov 4, 2014
  1. @hsbt
  2. @hsbt

    Add #1044 to History

    hsbt authored
  3. @hsbt

    Merge pull request #1044 from akr/fix-mirror

    hsbt authored
    Don't define MirrorCommand if already defined.
  4. @hsbt
Commits on Oct 15, 2014
  1. @zzak
  2. @zzak

    Merge pull request #1048 from jasonrclark/fix_platform_typo

    zzak authored
    Fix typo in platform= documentation [ci skip]
Commits on Oct 14, 2014
  1. @jasonrclark
Commits on Oct 10, 2014
  1. @akr
Commits on Oct 8, 2014
  1. @luislavena
Commits on Oct 5, 2014
  1. @hsbt
Commits on Oct 1, 2014
  1. @drbrain
  2. @drbrain
  3. @drbrain

    Set release version

    drbrain authored
  4. @drbrain
  5. @drbrain

    Set issue type properly

    drbrain authored
  6. @drbrain

    Raise immediately if a git revision is missing

    drbrain authored
    Previously RubyGems would continue to try to determine the git hash for
    a reference even if it did not exist.  This would cause RubyGems to
    spew git errors on the console but continue to install and create a bad
    Now RubyGems raises immediately if it cannot find a hash for a
    Fixes #1031
  7. @drbrain

    Fix failed History.txt update

    drbrain authored
  8. @drbrain

    Gem update can update to prereleases again

    drbrain authored
    Previously this worked (I think) by updating to the next prerelease
    automatically.  This broke with the recent changes for prereleases.
    Now RubyGems checks for a prerelease version to update to (as
    indicated by the requirement given to update_gems) and creates a new
    installer with the option enabled.
    This allows RubyGems to properly resolve the dependencies necessary to
    update the gem.
    The test for this change is poor as I can't see how to reproduce the
    failure indicated in #1028 as it is complex.  Instead I just check to
    see if the flag is correct as I trust the resolver.  A test duplicating
    the failure in #1028 seems like it would result in a functional test
    anyhow, so this is probably OK.
    Fixes #1028
  9. @hsbt
Commits on Sep 25, 2014
  1. @drbrain

    Add gemspec and deps to lockfile DEPENDENCIES list

    drbrain authored
    Previously the dependencies for the gemspec itself and its dependencies
    were not added to the lockfile.  This may have caused an
    incompatibility, but it is unknown if it would be automatically fixed
    by bundler or not, nor if it caused any real damage.
    Fixes #1020
Commits on Sep 24, 2014
  1. @drbrain

    Maintain self-dependency for gemspec

    drbrain authored
    If the gemspec doesn't create a dependency for itself it won't be
    included in the lockfile and won't be installed on the next go-around.
    Part of #1020
Something went wrong with that request. Please try again.