Fix version file update on publish (#513)

When we publish the JavaScript packages the `version.ts` file in the
JavaScript package wasn't being updated. This was because the
`versionfile` script wasn't run on publish causing the reported version
of the last few releases to be stuck on 1.3.12.

This should work because mono will update the `package.json` before the
build step with the new version. Updating the `version.ts` file after
the build should be fine, could also be done beforehand, it should not
matter.

(The publish step will also call `yarn publish` with the `--new-version
#.#.#` option, and attempt to update the `package.json` with the new
version, but this doesn't do anything as mono already updated the
`package.json` with the new version beforehand.)

Fixes #512

Author: tombruijn

packages/javascript/.changesets/fix-reported-library-version.md

@@ -0,0 +1,5 @@
+---
+bump: "patch"
+---
+
+Fix the reported library version of the JavaScript package. This was stuck on 1.3.12 for the last few releases.

packages/javascript/package.json

@@ -8,6 +8,7 @@
   "license": "MIT",
   "scripts": {
     "build": "yarn build:cjs && yarn build:esm",
+    "postbuild": "yarn versionfile",
     "build:esm": "tsc -p tsconfig.esm.json",
     "build:esm:watch": "tsc -p tsconfig.esm.json -w --preserveWatchOutput",
     "build:cjs": "tsc -p tsconfig.cjs.json",

packages/javascript/src/version.ts

@@ -1,2 +1,2 @@
 // Do not touch this file, auto-generated by scripts/create-version
-export const VERSION = "1.3.12"
+export const VERSION = "1.3.18"