package-lock.json's version does not match package.json's

[pgcalixto]

It would be ideal to have the version on package-lock.json matching package.json's.
It seems to be missing as a part of the release creation.

• luxon/package.json

  Line 3 in 345b1cd

  "version": "1.25.0",

• luxon/package-lock.json

  Line 3 in 345b1cd

  "version": "1.24.1",

• 345b1cd

[pgcalixto]

I noticed this while working on a different PR: #797 (comment).

Also, @GillesDebunne's comment #794 (comment) made me notice that there is an scripts/ directory containing some scripts I believe are run by the maintainers when creating a new release.

My suggestion is to use npm version command to do it on scripts/tag, since it already generates a new bump commit, creates a git tag and increases the version both on package.json and package-lock.json.

I will be creating a PR now based on this suggestion, for further analysis by the maintainers.

[pgcalixto]

I created https://github.com/moment/luxon/pull/800/files to use it as a reference.

There are some problems involved, such as:

• I believe scripts/release is run after a maintainer pushes a bump commit (such as this: 345b1cd). Since scripts/tag would create the bump commit, its order should be changed and it should be called as the first script.
• npm version creates tags with the vX.Y.Z format, while Luxon uses X.Y.Z (without the v prefix). It would be best to find a solution that maintains the same way it already is (no v prefix). I haven't found a way to do this using npm version.
  Referece: https://docs.npmjs.com/cli/version