Create a new release

[mhdawson]

@guybedford what is the process for suggestion a new release?

I'd like a new release that incorporates being build with the common wasm builder as I'd like to update the Node.js updater script so that it copies everything needed to to do the build into the directory in the deps and builds from the deps directory.

[guybedford]

@mhdawson at the moment the steps are:

• Update the package.json version, and run a full build and test
• Commit and tag the changes, pushing up to main and the tag
• Create the GitHub release
• Run npm publish from a nodejs-foundation account with access

[mhdawson]

@guybedford assume you are ok with me doing that, given that should shared the instructions?

[guybedford]

Absolutely.

[mhdawson]

• Update the package.json version, and run a full build and test
  • npm install
  • npm run build
  • npm run test
• Commit and tag the changes, pushing up to main and the tag
  • git tag -a 1.4.2 -m "1.4.2"
• Create the GitHub release
• Run npm publish from a nodejs-foundation account with access

[mhdawson]

Reopening as it should have been a SemVer major release 2.0.0 as discussed in - #110

Creating release 2.0.0

• Figure out if the release should be semver patch, minor or major based on the changes since
  the last release and determine the new version. - 2.0.0
• Update the package.json version, and run a full build and test
  • npm install
  • npm run build
  • npm run test
• Commit and tag the changes, pushing up to main and the tag
  • For example - git tag -a 1.4.2 -m "1.4.2"
• Create the GitHub release
• Run npm publish from an account with access (asking somebody with access
  the nodejs-foundation account is an option if you don't have access.