Publish Steps

Update CHANGELOG.md with new version number, publish date, and all changes.
Update package.json, specifically the version field.
Copy the new version number to server/package.json.
Run npm install, npm update to get the latest versions of dependencies.
Git commit the results of these edits and package-lock changes.
Open the project and run task watch to recompile if needed.
In PowerShell, run vsce package.
- Compare the new package size to previous, to see if any new large files got added via npm.
- Test the release package by installing it manually in {user}/.vscode/extensions.
In PowerShell, run vsce publish to actually publish to the marketplace.
Add a git tag for the release. For example: git tag -a 2.5.0 -m "Release version 2.5.0"
Push the branch & tag. git push --tags

NOTE: It is best to run vsce in PowerShell, not Git Bash, due to TTY differences.

Credentials

Login to [username].visualstudio.com
From user account pull-down menu, select "Security" -> Personal Access Tokens
Click button to add a new token.
Modify the "accounts" drop-down of the proposed new token to change your username to "All accessible accounts." NOTE that this setting cannot be viewed or edited after a token is created, it is only available during creation.
In PowerShell, if you haven't already installed vsce, install it with npm install -g @vscode/vsce.
Run vsce login cesium
Paste the key created in step 4.
Now you are ready to run the publish steps above.