I’ve been doing that when things break due to things moving around. I’ll tag the plugin’s current state, so older Discourse instances can reference that, and I’ll continue support latest on the master branch.
Saves me the headache of having to figure out how to support both.
I also had time to rework all of my plugins to work with Ember 2.4, I had a few issues I had to work out in them.
One thing I need to work on, is figuring out a way to let the branch identify which version of Discourse it works with. As right now, I couldn’t easily tell you which tags/branches go to which versions of Discourse. 