npm package.json version != github repo version

Hi there,

Is there any chance you could bump the package.json version to 1.7.3 so that it matches what is published to npmjs?

I'm trying to get this package approved for use at work. They're pretty strict about licensing and want to link the package publish date back to some commit in the source repo.

The problem here is that version 1.7.3 is what we are grabbing from npm and the publish date of that matches the last commit in the repository, however the version in package.json in this repo indicates 1.7.2 (as does the repo tag).

Basically since there is a mismatch between the source repository and the package contents it is causing issues :(

Many thanks

Check package.json and the repository's 1.7.2 tag, then compare them with the published npm version 1.7.3. Update the repository version metadata so it matches the published package and verify that the source version, tag, and npm version are consistent.

Written by the indexing model from the issue text.