Skip to content

Commit

Permalink
Revert to 0.8.2 (bumping the version to 7.1.1 happened in error, conf…
Browse files Browse the repository at this point in the history 
…using the JS and Ruby versions)
  • Loading branch information
@dhh
dhh committed Nov 5, 2021
1 parent a0f14b9 commit 31e19cb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion lib/turbo/version.rb
View file
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
module Turbo
VERSION = "7.1.1"
VERSION = "0.8.2"
end

4 comments on commit 31e19cb

@ghiculescu
Copy link
Contributor

@ghiculescu ghiculescu commented on 31e19cb Nov 5, 2021 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yanking this gem broke ours (and maybe many others) build pipelines :(

is it possible to un-yank? is it a good idea? i suppose that would make the versioning on https://rubygems.org/gems/turbo-rails pretty weird, but it is a bit of a nuisance either way.

@dhh
Copy link
Member Author

@dhh dhh commented on 31e19cb Nov 5, 2021 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately not. If we had left the bad versioned gems live, we could never have released versions with lower version numbers and have them picked up.

@marcelolx
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why the npm package stays on v7.0.1 and the gem on v0.8.2?

@dhh
Copy link
Member Author

@dhh dhh commented on 31e19cb Nov 9, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The npm package has always tracked the turbo release, so that's as it should be.

Please sign in to comment.