Closed ilg-ul closed 7 months ago
FYI, the easiest way to keep everything in sync is to use npm version
, it updates the package.json and adds the tag for the release.
In your case, in an up to date repository, all you have to do is npm version patch
, then push everything.
Thanks for pointing this out. Yeah I will need to adapt or improve my release workflow, otherwise this mistake is prone to happen again. I hope everything is working now?
I hope everything is working now?
I updated my projects and they seem ok.
... improve my release workflow
yeah, the best way to go is to start publishing the project on npmjs.com, this will ensure the released versions are different.
at the minimum, you should add nom version
to your release checklist.
You just released 2.3.0, but the
package.json
version still reads 2.2.1, and so the package cannot be installed via npm/xpm.Please be sure you update the version in package.json for new releases!
In this case you'll probably need to make a 2.3.1 release.