+ [2013-07-19T16:57:51Z] benbalter I noticed as I was going to upgrade Pages to 1.1.0
+ [2013-07-19T16:58:23Z] jaybe for kicks, you could try to dev and publish to github with 1.1.0 and see if it fails. that would explain a lot real quick. :)
+ [2013-07-19T19:28:18Z] travis-ci [travis-ci] kelvinst/jekyll#62 (deprecator-powerup) The build was fixed. http://travis-ci.org/kelvinst/jekyll/builds/9279833
+ [2013-07-19T19:57:55Z] travis-ci [travis-ci] kelvinst/jekyll#63 (deprecator-powerup) The build passed. http://travis-ci.org/kelvinst/jekyll/builds/9280761
+ [2013-07-19T20:25:22Z] travis-ci [travis-ci] kelvinst/jekyll#64 (deprecator-powerup) The build passed. http://travis-ci.org/kelvinst/jekyll/builds/9281787

message no. 5667

Posted by benbalter in #jekyll at 2013-07-19T16:57:51Z

I noticed as I was going to upgrade Pages to 1.1.0
+ [2013-07-20T02:43:23Z] bret any word as to when jekyll gets updated on pages?
+ [2013-07-20T02:44:59Z] agarie nope
+ [2013-07-20T02:45:32Z] agarie You can ask parker to keep telling mojombo to update them, but I don't know how this would turn out :/
+ [2013-07-20T02:45:58Z] agarie You can compile your site locally and push it to GH pages or you can use Heroku, to name some free alternatives
+ [2013-07-20T03:42:24Z] bret I though heroku cost money