chore: add new publish pipeline

[rzhao271]

Also fixes up the existing pipeline to become a CI-only pipeline.
One issue with the new pipeline is that it uses the package.json version. I'm not sure how to let it auto-generate a new beta version.

[Tyriar]

One issue with the new pipeline is that it uses the package.json version. I'm not sure how to let it auto-generate a new beta version.

It would be a shame to lose that, would it instead publish whenever the package.json changes in main?

[rzhao271]

Afaik, the maintainer must manually set the package.json version, run a pipeline build, and get it approved, ref https://dev.azure.com/monacotools/Monaco/_build/results?buildId=297071&view=results

Edit: Adding Lad to the PR to confirm.

[rzhao271]

I have changed the publish script to only increment the package.json version, and the YAML should now run that script to set the correct version before publishing the package. There is no verification build because the pipeline needs to be on the main branch for me to create a new pipeline in ADO for it.

[lszomoru]

You should look at vsce as it implements the desired pattern to automatically update the package version based on the nextVersion pipeline input parameter - https://github.com/microsoft/vscode-vsce/blob/f1fc6d255d634849db9a7f28e59a031c49cd4918/build/azure-pipelines.yml#L18

[rzhao271]

@lszomoru I believe the version format is different for node-pty: https://www.npmjs.com/package/node-pty?activeTab=versions

Here's what I see for @vscode/vsce: https://www.npmjs.com/package/@vscode/vsce?activeTab=versions

[lszomoru]

If node-pty is using custom version number format then it is up to the package owner to increment it. If you specify the nextVersion template parameter (list vsce does) we will run npm version ${{ parameters.nextVersion }} --no-git-tag-version --allow-same-version to update the package.json.