Release automation

.github/workflows/build.yml

@@ -1,4 +1,4 @@
-name: Lint, build and test
+name: Lint and package
 on:
   push:
     branches:
@@ -8,7 +8,7 @@ on:
 
 jobs:
   build:
-    name: Build and test
+    name: Build, test and package
     strategy:
       matrix:
         os: [ubuntu-latest, windows-latest]

.github/workflows/release.yml

@@ -0,0 +1,39 @@
+name: Package and create a release with assets
+on:
+  push:
+    tags:
+      - "*"
+
+jobs:
+  build:
+    name: Package and create a release with assets
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Set up JDK 11
+        uses: actions/setup-java@v3
+        with:
+          java-version: 11
+          distribution: 'zulu'
+          cache: 'maven'
+      - name: Cache Maven packages
+        uses: actions/cache@v3
+        with:
+          path: ~/.m2
+          key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }}
+          restore-keys: ${{ runner.os }}-m2
+      - name: Test and package
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: mvn --batch-mode --update-snapshots package
+      - run: mkdir staging && cp **/target/*.jar staging
+      - run: cd magik-language-server/client-vscode && npm install . && npm run package
+      - run: cp magik-language-server/client-vscode/magik-language-server-*.vsix staging
+
+      - name: Release
+        uses: softprops/action-gh-release@v1
+        with:
+          files: |
+            staging/*

README.md

@@ -84,7 +84,7 @@ $ mvn -B versions:set -DnewVersion=<version> -DgenerateBackupPoms=false
 
 Be sure to also update the symbolic links in `magik-language-server/client-vscode/server`. Then update `magik-language-server/client-vscode/client/src/const.ts`, and `magik-language-server/client-vscode/client/package.json` and related package files.
 
-Creation and uploading of artifacts is currently done by hand.
+Then, create a release by pushing a new tag to Github.
 
 ### SonarCloud