feat: updating cargo.toml and package.json before version commit

[tegefaulkes]

Description

This PR adds a version script that updates the cargo.toml version to match the new package.json version when a npm version is run.

It also rolls the postVersion script into the version script. The changes from the postVersion script were not included in the tagged version commit.

• Related Automatically bump cargo.toml version to match package.json. #28

Issues Fixed

• Fixes Automatically bump cargo.toml version to match package.json. #28

Tasks

• 1. Ensure that automatic changes to the version numbers in the package.json dependencies and cargo.toml file are updated with the new version from the npm version command. ensure that these changes are included in the tagged version commit.
• 2. Ensure that there are no un-staged or un-commited changes that should be included in the commit.
• 3. Verify this all works with a pre-release version.

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[ghost]

👇 Click on the image for a new way to code review

Legend

[tegefaulkes]

Do we want to add anything else while we're here? Such as some checks in the preVersion stage? Such as a lint, build and test check?

[tegefaulkes]

Ah, the cargo lock file isn't being updated, we want to commit changes to that as well.

[tegefaulkes]

That should fix it. Running npm install and npm run build shouldn't result in updates to any lock files. Except for the optional dependencies, these will change based off of platform and availability.

[tegefaulkes]

I think the only thing left is to merge and run a test job to see if it publishes.

[CMCDragonkai]

Is this going to be merged?