4 ms·
Then the 0.3.6 version was released, and we could update because the license isn't much of a problem in this case. Alternatively we could have continuee to dep
by byroot 6y ago
Then the 0.3.6 version was released, and we could update because the license isn't much of a problem in this case.
Alternatively we could have continuee to deploy for a few more days until Rails core shipped a new version of Active Storage without that dependency.
It's effectively the same as vendoring, except we're not blowing up our repositories with 10 years of dependencies.
- ro_ro 6y agoI should clarify... Vendoring is a terrible solution. Caching is a general good practice but not a solution. All in all, this kind of thing happens once in a blue moon...
- byroot 6y agoI don't claim it's a long term solution, and that you should run of your cache for years. But having that cache means you have the time to get a clean solution rather than having to rush something because nobody can work anymore can you can't deploy fixes to production either. These yanking issues are really problematic, but if they interrupted your workflow, then there's something wrong with your build pipeline.