Make an NPM release via GitHub

[PurpShell]

PR Details

Description

Related Issue

Motivation and Context

How Has This Been Tested

Types of changes

• Dependency change
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• I have updated the documentation accordingly (index.d.ts).

[pedroslopez]

Thanks!

From what I remember, I believe the GitHub release should respect the prerelease flag marked in the output here to make the release correctly

[pedroslopez]

Ah! I forgot something - another thing that happens as part of the mainline release process is docs generation.

There's a script that does this, npm run generate-docs

This should happen only for main releases, after the version bump (so the docs contain the right version) but before the version is tagged

[pedroslopez]

this still won't be included as part of the commit.

npm version creates a commit and tag:

If run in a git repo, it will also create a version commit and tag. This behavior is controlled by git-tag-version (see below), and can be disabled on the command line by running npm --no-git-tag-version version. It will fail if the working directory is not clean, unless the -f or --force flag is set.

So the docs generation is outside of the bump commit.

To keep this simple, we might be able to just do the docs generation after the git push, and commit/push that separately. It won't be included as part of the tag, but at least we can move forward with this PR and unlock the functionality.