We pushed out a couple of public releases of the Hammer Gem this week (current latest is 5.1.5). I'm very pleased to say that for the most part, it's gone smoothly. Given it was quite a big update in terms of many of the core libraries, I'm pretty happy with how it's gone.
Certainly, being able to use Slim and benefitting from up to date Sass and other libraries are a big plus.
It's also helped me to see just how much many people depend on Hammer in their day jobs and that's really great to see. But, when things aren't quite working as expected (there were some bugs in 5.1.4 and larger sites seem to have some performance issues currently), when they change or when a large amount of work is needed to be done (somewhat unannounced) such as upgrading to comply with stricter sass rules, for example - it can be overwhelming, when you've got work to do. I get that.
Whilst the Hammer product is design to stay up to date, with a pretty smart auto-update system that allows us to push updates to the Hammer compiler remotely without the need for app store approval, it currently doesn't allow you to opt out of receiving these updates.
I'm committed to developing Hammer. It's going to take us a little time to get things in shape, but we'll be pushing on with our roadmap.
So, if worse comes to worse, what do you do?
Roll Forward to Roll Back
We've created a little bash script that will enable you to roll your Hammer Gem version back to 5.1.1 (the last version before recent updates). If you really need to just get on with work and you're facing breaking changes, you can opt out of the current updates by running this script from the terminal.
$ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/RiotHQ/hammer-gem/v2-disable-update/scripts/update.rb)"
Essentially, what will happen is it will actually re-install version 5.1.1 of the gem, but set your Hammer compiler version to 5.1.9. This will mean when Hammer is looking for newer versions automatically, it won't auto-update until at least version 5.2.0 is released publicly.