Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump to 2.1.11 #629

Merged
merged 1 commit into from
Dec 1, 2013
Merged

Bump to 2.1.11 #629

merged 1 commit into from
Dec 1, 2013

Conversation

amarshall
Copy link
Contributor

The version on the front page hasn’t matched the release version in nearly 3 months, this corrects that.

The version on the front page hasn’t matched the release version in nearly 3 months, this corrects that.
@skottler
Copy link
Member

skottler commented Dec 1, 2013

cc @drbrain

@drbrain
Copy link
Member

drbrain commented Dec 1, 2013

I ask @evanphx to update this for me since I don't know how to do it. @evanphx said he was making some API I could plug into the rubygems/rubygems rake release task, but I don't know how far he got on it.

@skottler
Copy link
Member

skottler commented Dec 1, 2013

I'm gonna merge this but I'm on my phone so I can't roll it out until later today.

Thanks @amarshall. @drbrain I'll update this in the future, just ping me if I forget 👍

skottler pushed a commit that referenced this pull request Dec 1, 2013
@skottler skottler merged commit 8766206 into rubygems:master Dec 1, 2013
@dwradcliffe
Copy link
Member

There's an old rake task to do this. It looks like it does more than just bump that number. Is that still valid?

desc "update rubygems. run as: rake gemcutter:rubygems:update VERSION=[version number] RAILS_ENV=[staging|production] S3_KEY=[key] S3_SECRET=[secret]"
task :update => :environment do
version = ENV["VERSION"]
app_path = Rails.root.join("config", "application.rb")
old_content = app_path.read
new_content = old_content.gsub(/RUBYGEMS_VERSION = "(.*)"/, %{RUBYGEMS_VERSION = "#{version}"})
app_path.open("w") do |file|
file.write new_content
end
updater = Indexer.new
html = Nokogiri.parse(open("http://rubyforge.org/frs/?group_id=126"))
links = html.css("a[href*='#{version}']").map { |n| n["href"] }
if links.empty?
abort "gem/tgz/zip for RubyGems #{version} hasn't been uploaded yet!"
else
links.each do |link|
url = "http://rubyforge.org#{link}"
puts "Uploading #{url}..."
updater.directory.files.create({
:body => open(url).read,
:key => "rubygems/#{File.basename(url)}",
:public => true
})
end
end
end

@evanphx
Copy link
Member

evanphx commented Dec 2, 2013

No, I don't use the task anymore. I need to still setup that API for Eric,
I'll do that this week.

On Mon, Dec 2, 2013 at 4:22 AM, David Radcliffe notifications@github.comwrote:

There's an old rake task to do this. It looks like it does more than just
bump that number. Is that still valid?

desc "update rubygems. run as: rake gemcutter:rubygems:update VERSION=[version number] RAILS_ENV=[staging|production] S3_KEY=[key] S3_SECRET=[secret]"
task :update => :environment do
version = ENV["VERSION"]
app_path = Rails.root.join("config", "application.rb")
old_content = app_path.read
new_content = old_content.gsub(/RUBYGEMS_VERSION = "(.*)"/, %{RUBYGEMS_VERSION = "#{version}"})
app_path.open("w") do |file|
file.write new_content
end
updater = Indexer.new
html = Nokogiri.parse(open("http://rubyforge.org/frs/?group_id=126"))
links = html.css("a[href*='#{version}']").map { |n| n["href"] }
if links.empty?
abort "gem/tgz/zip for RubyGems #{version} hasn't been uploaded yet!"
else
links.each do |link|
url = "http://rubyforge.org#{link}"
puts "Uploading #{url}..."
updater.directory.files.create({
:body => open(url).read,
:key => "rubygems/#{File.basename(url)}",
:public => true
})
end
end
end


Reply to this email directly or view it on GitHubhttps://github.com//pull/629#issuecomment-29613514
.

skottler pushed a commit that referenced this pull request Jan 29, 2015
dwradcliffe added a commit that referenced this pull request Jan 29, 2015
since we're not using it anymore
(see: #629 (comment))
arthurnn pushed a commit that referenced this pull request Jan 29, 2015
http://rubygems.org/pages/download still shows 2.1.11 as the latest version.

There's some discussion about integrating this into the rubygems/rubygems release task in issue #629.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants