Ask HN: Is it time to stop putting the version in package.json?
I made a tool called `hipp` to eliminate 'chore: version bump' commits for npm packages, and I included simple content integrity as a bonus.The idea is to keep the package.json version at 0.0.0, tag your release in git (e.g., v1.2.3), and publish.HIPP rewrites the version on the fly and appends a signed manifest to the README with a disposable key.Is there something I haven't thought of that...