And now we get into a discussion about what constitutes public vs private API. I completely accept that the naked variable thing wasn't intended behaviour of Co

And now we get into a discussion about what constitutes public vs private API. I completely accept that the naked variable thing wasn't intended behaviour of Coffeescript. Nevertheless, it was a thing that worked and was widely enough used for it to be mentioned in the changelog. So, thanks for mentioning it the changelog! It's great that you're aware not only of how your code is intended to be used, but how it is being used in the wild. That's a really good thing and worthy of praise. The bit that annoyed me was that you knew this, but still chose not to bump the major. I read your stance on semver the last time we all did this collective dance. Most of it makes perfect sense. It is a valid argument, and I would be very happy for us, as a community, to work towards something better than semver. That has to happen in a holistic way, though. Our package manager uses semver. Publishing your package on that package manager is an implicit acceptance of that convention. The fact that someone can `npm install coffee-script` leads them to believe that it will at least attempt to follow the rules and conventions of that ecosystem. (Incidentally, I only found out about the recent underscore-semver-round-2 1.8.0 thing _after_ publishing this post. This isn't a guy trying to stir up larger drama. This is just a guy who had to spend his Friday evening fixing a preventable bug in production and it made him grumpy.)