Always update the extensions/analyticsdx-vscode/CHANGELOG.md with high level changes since the last version. Follow the existing formatting. This should be committed and pushed, either before or with the the version changes.
Run ANALYTICSDX_VSCODE_VERSION=<X.Y.Z> npm run publish-all-vsixs. That will do all of the steps listed below.
If you want to update the version of the extensions, run ANALYTICSDX_VSCODE_VERSION=<X.Y.Z> npm run update-versions.
This will update the appropriate files, but won't immediately check them in.
Normally, just run npm run build-all-vsixs.
This will:
git clean -xfe node_modulesto do do a full clean of the repo.npm installto install all the dependencies and to symlink interdependent local modules.NODE_ENV=production npm run compileto compile all the TypeScript files for production.npm run vscode:packagepackages each extension as a .vsix.
At this stage, it is possible to share the .vsix directly for manual installation.
Due to vscode-vsce#191 the .vsix are neither signed nor verified.
For now, we want to update the SHA256.md file in the repository with the checksums. This is done by
running npm run update-sha256, which will update the SHA256.md file from the .vsix files in the extension folders, but
won't immediately check it in.
- Get an access token from your marketplace account.
- Login to the salesforce publisher:
npx vsce login salesforceand enter your access token - Run
npm run vscode:publish
After publishing, you will normally want to commit and push any of the updated files (i.e. SHA256.md, lerna.json,
package.json's) and generate a tag for the version, like git tag vX.Y.Z -m "Release X.Y.Z" && git push origin vX.Y.Z