[BUG] `asc --version` now returns 0.0.0

[willemneal]

As the title says since the new semantic publishing was set up the version returned is 0.0.0.

[dcodeIO]

The SDK had a similar issue that I was able to solve by building it upon postversion. Ideally there'd be a way to determine and update the version prior to publishing using semantic-release, but not sure if they support that.

[MaxGraey]

How about add custom script (or npm hook) which will trigger after semantic-release publish and write ver string to some version.json file for example? Or is there an easier way?

[dcodeIO]

We can'd modify the package anymore after it has been published, unfortunately. Also, dist files can't load a separate file via require or similar but must bundle everything for browser usage. Best integration point I found so far is postversion, which executes exactly in between determining the version and publishing the package during execution of semantic-release.

[dcodeIO]

Their docs for reference: How can I use a npm build script that requires the package.json’s version ?

[github-actions]

🎉 This issue has been resolved in version 0.14.5 🎉

The release is available on:

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

Your semantic-release bot 📦🚀