Timezone problem when calling Timecop.freeze at v0.5.8 about timecop HOT 5 CLOSED

Just saw this issue with Timecop.travel:

[1] > Time.now
=> 2013-01-08 21:55:09 -0700
[2] > Timecop.travel(1.hour.ago) { Time.now }
=> 2013-01-08 12:55:46 -0700

I just updated Timecop from 0.5.3 to 0.5.8

from timecop.

This does not occur in 0.5.7:

[1] > Time.now
=> 2013-01-08 21:58:31 -0700
[2] > Timecop.travel(1.hour.ago) { Time.now }
=> 2013-01-08 20:58:32 -0700
[3] > Timecop.freeze(1.hour.ago) { Time.now }
=> 2013-01-08 20:58:44 -0700

from timecop.

Ah! I had seen that problem before and just didn't write a test to cover it at the time. Got a test in there now to cover this now though so to it won't happen again.

Fixed in v0.5.9 which I just released.

from timecop.

Thank you for your very quick fix.

Well, maybe you forgot to upgrade version number at https://github.com/travisjeffery/timecop/blob/master/lib/timecop/version.rb to 0.5.9?
It seems that v0.5.9 does not available on rubygems.org https://rubygems.org/gems/timecop/versions

from timecop.

@kyanny whoops, you're right. It's up there now for sure.

from timecop.