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

Version scheme in sync? #20

rhuppert opened this issue May 7, 2014 · 1 comment

Version scheme in sync? #20

rhuppert opened this issue May 7, 2014 · 1 comment


Copy link

@rhuppert rhuppert commented May 7, 2014

I was in the process of cleaning up a Rails app and noticed 3 version from 2013 are out of sync with the others on If I run "bundle outdated," it lists tzinfo as outdated even though I'm have the latest version (0.3.39) installed at this time. Bundler shows it as outdated: * tzinfo (1.1.0 > 0.3.39)

Not a big deal, really. I must be embracing my anal side, but was curious.

@rhuppert rhuppert closed this May 8, 2014
@rhuppert rhuppert reopened this May 8, 2014
Copy link

@philr philr commented May 8, 2014

The latest version of TZInfo is currently 1.1.0 (although not the most recent to be released).

There are currently two active branches. Most of the activity is on the master branch. The v1.1.0 release was taken from master.

There is also a '0.3' branch to support users who cannot upgrade to the newer version of TZInfo. This includes users of Ruby on Rails up to 4.0, because version 4.0.5 of activesupport depends on tzinfo ~> 0.3.37. The v0.3.39 release of TZInfo was taken from the 0.3 branch.

If you are using Ruby on Rails 4.1, then you'll be able to use TZInfo v1.1.0. If you are using an earlier version of Ruby on Rails, the latest version of TZInfo that can be used is 0.3.39.

@philr philr added the question label May 8, 2014
@philr philr closed this May 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.