Publishing your VSCode Extensions from GitHub Actions

Automation is key! That is how I think anyway. I’m not too fond of repetition, but for some reason, I had not yet automated my Visual Studio Code extension publishing. I always did this manually from my terminal by running vsce publish.

With my latest extension, I thought, now is the time to automate this as well.

Setting up your workflow

When publishing your Code extensions, you need to use the Visual Studio Code Extension command-line tool: vsce. Typically this is something you install locally by running npm i -g vsce.

In this case, we will do this on GitHub Actions instead, but before you can start, you need to create your Personal Access Token or also called PAT.

When you got this PAT, add it as a GitHub Secret to your project.

Show image

We will use this secret in the GitHub Actions workflow which looks as follows:

1
name: Release
2
on:
3
  release:
4
    types:
5
      - published
6
  workflow_dispatch:
7

8
jobs:
9
  release:
10
    runs-on: ubuntu-latest
11

12
    steps:
13
      - uses: actions/checkout@v2
14
      - uses: actions/setup-node@v1
15
        with:
16
          node-version: 14
17
          registry-url: https://registry.npmjs.org/
18

19
      - name: Install the dependencies
20
        run: npm i
21

22
      - name: Install vsce
23
        run: npm i -g vsce
24

25
      - name: Publish
26
        run: vsce publish -p ${{ secrets.VSCE_PAT }}