git tags missing / inconsistent naming about ember-cli-eslint

[BrianSipple]

Tags for 1.2.0 and 1.2.1 should now be in place.

[rwjblue]

Agreed

[Turbo87]

@rwjblue are there actually projects where you're not a "Collaborator"... 😂

[just4fun]

@Turbo87 That issue seems like not the same.
@BrianSipple Could you take a look at npm about this package?

[Turbo87]

@just4fun I think it is related because the 1.2.1 tag seems to be attached to the wrong commit. I think d7e0c32 is probably the right target for that tag.

@BrianSipple we currently seem to have a mix of tag names, some with a v prefix and some without. it would probably be a good idea to adjust those to stay consistent.

[BrianSipple]

@Turbo87 👍 on the consistent tag names. I renamed tags without a v to make sure that they do have the prefix.

Also, having npm find the right tag for 1.2.1 would definitely fix #52. My only confusion is around whether or not that's possible. Updating the current tag for 1.2.1 to point to d7e032 didn't seem to change the version that future npm installs were finding.

Another short-term solution would be publishing 1.3.0 -- which I'm planning to do after updating broccoli-lint-eslint. (Getting 2.2.0 was the last blocker). It doesn't help anyone using 1.2.1, though, which, even though there's no reason not to jump to 1.3.0, still kind of miffs me .