deploy_extension github action

Summary:
This diff adds a deploy_extensions github action which will deploy the extension on any changes to `pyre2/version.bzl`. This diff also switches the build action to use the version in `pyre2/version.bzl` so the extension version should always match the language server version in the marketplace.

To manually update the extension, developers should update the version in version.bzl (see the doc comment).

The version in `package.json` is not relevant because the build_extension action builds a specific version (`npx vsce package <platform> <version>`). this command updates package.json locally but does not get committed (if we don't want it modified we can `--no-update-package-json` on `npx vsce package` but I don't think it matters). if we want this to always be up to date with pyre2/version.bzl I can do that (I don't know if it matters).

Users of the extension should generally be disabling auto update and selecting a specific version of the extension (matching their pypy version) if they want to stay in sync with an old version.
{F1976279886}

I also opened a PR [here](EclipseFdn/publish-extensions#842) in order to make it [available in the open VSX registry](facebook/pyre-check#975 (comment))

Reviewed By: stroxler

Differential Revision: D71577667

fbshipit-source-id: 74e28230cf5bb1c6a33d72ad4f74f710277dbd77

Author: kinto0

.github/workflows/build_extension.yml

@@ -1,10 +1,25 @@
 name: build_extension
 on:
   workflow_dispatch:
+  workflow_call:
   push:
 
 jobs:
+  get_version:
+    runs-on: ubuntu-latest
+    outputs:
+      pyrefly_version: ${{ steps.pyrefly-version.outputs.PYREFLY_VERSION }}
+    steps:
+      - name: Checkout repo (to see version.bzl in nex step)
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # Get all history for all branches and tags
+      - name: Get version
+        id: pyrefly-version
+        run: echo "PYREFLY_VERSION=$(sed -n -e 's/^VERSION = "\(.*\)"/\1/p' pyre2/version.bzl)" >> $GITHUB_OUTPUT
   build_extension:
+    needs: get_version
+    if: success()
     strategy:
       fail-fast: false
       matrix:
@@ -61,11 +76,11 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 22
-      - run: npm ci
-        working-directory: lsp/
       - name: save platform name
         run: echo "platform=${{ matrix.platform }}-${{ matrix.arch }}" >> ${{ matrix.github_env }}
-      - run: npx vsce package --target ${{ env.platform }}
+      - run: npm ci
+        working-directory: lsp/
+      - run: npx vsce package --target ${{ env.platform }} ${{needs.get_version.outputs.pyrefly_version}}
         working-directory: lsp/
       - uses: actions/upload-artifact@v4
         with:

.github/workflows/deploy_extension.yml

@@ -0,0 +1,22 @@
+name: deploy_extension
+on:
+  push:
+    paths:
+      - pyre2/version.bzl
+    branches: [ main ]
+
+jobs:
+    build:
+        uses: ./.github/workflows/build_extension.yml
+
+    publish:
+        runs-on: ubuntu-latest
+        needs: build
+        if: success()
+        steps:
+            - name: upload
+              uses: actions/download-artifact@v4
+            - name: publish
+              run: npx vsce publish --packagePath $(find . -iname *.vsix)
+              env:
+                VSCE_PAT: ${{ secrets.VSCE_PAT }}

pyre2/version.bzl

@@ -1,7 +1,7 @@
 # IMPORTANT: *Any* change to this file will kick off an upload of a new version of pyrefly to PyPI,
-# although the upload will likely fail if you haven't changed the version number.
+# and a new VSCode extension although the upload will likely fail if you haven't changed the version number.
 #
-# An automated PyPI release happens once a week. To update the version for a manual release:
+# An automated PyPI/extension release happens once a week. To update the version for a manual release:
 # * The version number is in the format "<major>.<minor>.<patch>".
 # * Do exactly ONE of the following:
 #   * Increase the patch number by 1 if the release contains only minor changes like bug fixes.