why reset the version?

why reset the version?

Semantic release takes care of updating the version just before publishing to NPM. There is no need to have it versioned in source code. Thanks to semantic-release, the version will already appear as the latest release:

This is also how it's done in drei and explained in more details here: https://semantic-release.gitbook.io/semantic-release/support/faq#why-is-the-package.jsons-version-not-updated-in-my-repository

I think I'm done.

We could safely merge it into master: it won't trigger a release since only chore: commit messages in this PR (only feat: or fix: will).

Once merged, we could check the new Build and Release to npm pipeline just succeeds (without publishing any new version)

thanks @abernier !

🎉 This PR is included in version 2.9.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀