Possible mistake on the version number

[mindsers]

After new release was published, I tried to update the package but neither yarn nor npm knows the new version.

I looked for the git tags in github but didn't find it. Then I looked at npm's version list and got this:

• 2.0.1 (2 hours ago)
• 2.1.0 (8 months ago)

As yarn and npm use/understand semver, they don't see 2.0.1 as a new version after 2.1.0. I think the version number should be 2.1.1.

---

@zackify Is there a mistake on the version number?

Originally posted by @mindsers in #10 (comment)

[zackify]

I wasn’t aware that a 2.1.0 was released and yet the package.json on master said 2.0.0. I’ll have to do a new release tomorrow. Sorry about that. As you can tell this isn’t my repo but I got added as a collaborator a while ago haha

[mindsers]

No problem! I just write the problem here to be solved at some point and we don't forget about it. 😃

As a workaround until it's solved, we can (force) install the package at the version 2.0.1 specifically.

yarn add graphql-tag.macro@2.0.1

[mindsers]

@zackify Hi! Is there anything new about this?

[leoasis]

Happy to get a PR that includes this change! Should be an easy one :)

[zackify]

Sorry for not replying sooner. I’ve been on vacation with my laptop out of reach or I would have released it already

[mindsers]

@leoasis a PR for what? It seems the needed code is already on master(#10).

[pdemarino]

Hi - same comment here. Any chance this can be pushed out?