ci: Replace create-release with full automated release workflow

- Merges version branch to master
- Runs tests (aborts on failure)
- Builds VSIX and creates GitHub release
- Publishes to VS Code Marketplace via VSCE_PAT
- Creates next version branch and sets it as default on GitHub

Also adds CONTRIBUTING.md explaining the branching model

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: msarson

.github/workflows/create-release.yml

@@ -0,0 +1,102 @@
+name: Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: 'Version being released (e.g., 0.8.8)'
+        required: true
+        type: string
+      next_version:
+        description: 'Next development version branch to create (e.g., 0.8.9)'
+        required: true
+        type: string
+
+permissions:
+  contents: write
+  administration: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout version branch
+        uses: actions/checkout@v4
+        with:
+          ref: version-${{ inputs.version }}
+          fetch-depth: 0
+
+      - name: Configure git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run tests
+        run: npm run test:server
+
+      - name: Compile release build
+        run: npm run compile:release
+
+      - name: Install vsce
+        run: npm install -g @vscode/vsce
+
+      - name: Package extension
+        run: vsce package
+
+      - name: Merge version branch into master
+        run: |
+          git checkout master
+          git merge version-${{ inputs.version }} --no-ff -m "Release v${{ inputs.version }}: merge version-${{ inputs.version }} into master"
+          git push origin master
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: v${{ inputs.version }}
+          name: Release v${{ inputs.version }}
+          draft: false
+          prerelease: false
+          files: ./clarion-extensions-${{ inputs.version }}.vsix
+          generate_release_notes: true
+          body: |
+            ## Installation
+
+            Download the VSIX file below and install it in VS Code:
+            1. Open VS Code
+            2. Go to Extensions (Ctrl+Shift+X)
+            3. Click "..." menu → "Install from VSIX..."
+            4. Select the downloaded file
+
+            ## Marketplace
+
+            This version is also available on the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=msarson.clarion-extensions).
+
+            ## What's New
+
+            See [CHANGELOG.md](https://github.com/msarson/Clarion-Extension/blob/master/CHANGELOG.md) for full details.
+
+      - name: Publish to VS Code Marketplace
+        run: vsce publish --pat ${{ secrets.VSCE_PAT }}
+
+      - name: Create next version branch
+        run: |
+          git checkout master
+          git checkout -b version-${{ inputs.next_version }}
+          git push origin version-${{ inputs.next_version }}
+
+      - name: Set next version branch as default
+        run: |
+          gh api --method PATCH /repos/msarson/Clarion-Extension \
+            -f default_branch=version-${{ inputs.next_version }}
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release.yml

@@ -0,0 +1,53 @@
+# Contributing to Clarion Extension
+
+Thanks for your interest in contributing! Please read the following before opening a PR.
+
+## Branching Model
+
+This project uses a simple release-branch model:
+
+| Branch | Purpose |
+|--------|---------|
+| `master` | Stable released code — only updated at release time |
+| `version-X.X.X` | Active development for the next release |
+
+**Always branch from and target the current development branch** (e.g. `version-0.8.8`), not `master`. You can see which branch is the current development branch by checking the repository's default branch.
+
+PRs targeting `master` directly will be asked to retarget.
+
+## Getting Started
+
+```bash
+git clone https://github.com/msarson/Clarion-Extension.git
+cd Clarion-Extension
+git checkout version-0.8.8   # or whatever the current default branch is
+npm install
+npm run compile
+```
+
+## Development
+
+```bash
+npm run watch        # continuous rebuild
+npm run test:server  # run server-side tests (no VS Code needed)
+npm run test:client  # run client tests (requires VS Code Extension Host)
+```
+
+Press **F5** in VS Code to launch an Extension Development Host for manual testing.
+
+## Submitting a PR
+
+1. Fork the repo
+2. Branch from the current development branch (`version-X.X.X`)
+3. Make your changes with tests where applicable
+4. Ensure `npm run test:server` passes
+5. Open a PR targeting the current development branch
+
+## Release Process
+
+Releases are handled by the maintainer via the **Release** GitHub Actions workflow, which:
+- Merges the version branch into `master`
+- Builds and packages the VSIX
+- Creates a GitHub release
+- Publishes to the VS Code Marketplace
+- Creates the next development branch and sets it as default