Add workflow for server PR testing (#481)

* fix linting issues

* Add workflow server PR testing

Author: tortmayr

.claude/skills/generate-changelog/SKILL.md

@@ -8,6 +8,7 @@ description: Generate changelog entries from merged PRs since the last release.
 Generate changelog entries by analyzing merged PRs since the last release.
 
 Execute these phases in order:
+
 1. **Data Gathering** — find last release, fetch PRs, classify, generate entries
 2. **Changelog Update** — write entries into CHANGELOG.md
 3. **Review & Approval** — present the actual diff to the user for review
@@ -20,11 +21,13 @@ Execute these phases in order:
 ### Step 1.1: Find the latest release tag
 
 Run:
+
 ```bash
 git tag --sort=-creatordate | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -1
 ```
 
 Record as `LAST_TAG`. Get the tag's date:
+
 ```bash
 git log -1 --format=%aI $LAST_TAG
 ```
@@ -46,12 +49,13 @@ Use the date portion only from `TAG_DATE` (e.g. `2026-02-09`).
 ### Step 1.4: Filter PRs
 
 **Skip rules** (in order):
+
 1. PR has the `changelog` label → skip (already tracked in a previous changelog update)
 2. Author login is `dependabot` or `dependabot[bot]` → skip
 3. Title matches version bump patterns → skip:
-   - Starts with `Switch to` and contains `-next`
-   - Title is a bare version like `vX.Y.Z`
-   - Title starts with `Release v`
+    - Starts with `Switch to` and contains `-next`
+    - Title is a bare version like `vX.Y.Z`
+    - Title starts with `Release v`
 4. Title contains `update changelog` (case insensitive) → skip
 5. Title is purely CI/metadata (readme badges, workflow config) AND body does NOT contain `[x] This PR should be mentioned in the changelog` → skip
 
@@ -62,9 +66,9 @@ Use the date portion only from `TAG_DATE` (e.g. `2026-02-09`).
 1. If body contains `[x] This PR introduces a breaking change` → **breaking**
 2. If body contains `[ ] This PR introduces a breaking change` → **normal**
 3. If no checkbox info, analyze title and body:
-   - Breaking keywords: "refactor", "rename", "remove", "replace", "migrate", "breaking", "deprecate"
-   - Clearly non-breaking (bug fix, docs, minor enhancement) → **normal**
-   - Uncertain → flag for user review
+    - Breaking keywords: "refactor", "rename", "remove", "replace", "migrate", "breaking", "deprecate"
+    - Clearly non-breaking (bug fix, docs, minor enhancement) → **normal**
+    - Uncertain → flag for user review
 
 ### Step 1.6: Assign category tags
 
@@ -75,57 +79,65 @@ Pick the most fitting tag from the vocabulary (Step 1.2) based on PR title and b
 #### Entry Format
 
 **Normal changes:**
+
 ```
 -   [tag] Description [#N](https://github.com/OWNER/REPO/pull/N)
 ```
 
 **Breaking changes** with migration sub-items:
+
 ```
 -   [tag] Description [#N](https://github.com/OWNER/REPO/pull/N)
     -   Migration detail 1
     -   Migration detail 2
 ```
 
 **Multiple PRs for the same change:**
+
 ```
 -   [tag] Description [#N](url) [#M](url)
 ```
 
 #### Style Guide
 
 **Formatting:**
-- Entry prefix: `-   ` (dash + exactly 3 spaces)
-- Sub-item indent: 4 spaces + `-   ` (4 spaces from parent dash)
-- Sub-sub-item indent: 8 spaces + `-   `
-- Single space between `[tag]` and description text
-- Single space before PR link at end of line
-- PR links are mandatory, full URLs: `[#123](https://github.com/OWNER/REPO/pull/123)`
+
+-   Entry prefix: `-   ` (dash + exactly 3 spaces)
+-   Sub-item indent: 4 spaces + `-   ` (4 spaces from parent dash)
+-   Sub-sub-item indent: 8 spaces + `-   `
+-   Single space between `[tag]` and description text
+-   Single space before PR link at end of line
+-   PR links are mandatory, full URLs: `[#123](https://github.com/OWNER/REPO/pull/123)`
 
 **Wording:**
-- Always start with a **present tense imperative verb** (not past tense)
-- Common verbs: Fix, Improve, Add, Update, Extend, Ensure, Introduce, Remove, Refactor, Rename, Provide, Allow, Support
-- **Bug fixes**: "Fix a bug that caused/prevented...", "Fix X behavior"
-- **Features**: "Introduce...", "Add support for...", "Provide..."
-- **Enhancements**: "Improve...", "Extend...", "Ensure that..."
-- **Refactors**: "Refactor...", "Rework...", "Rename..."
-- Be specific — never "Fix various issues"
+
+-   Always start with a **present tense imperative verb** (not past tense)
+-   Common verbs: Fix, Improve, Add, Update, Extend, Ensure, Introduce, Remove, Refactor, Rename, Provide, Allow, Support
+-   **Bug fixes**: "Fix a bug that caused/prevented...", "Fix X behavior"
+-   **Features**: "Introduce...", "Add support for...", "Provide..."
+-   **Enhancements**: "Improve...", "Extend...", "Ensure that..."
+-   **Refactors**: "Refactor...", "Rework...", "Rename..."
+-   Be specific — never "Fix various issues"
 
 **Capitalization:**
-- Tags are always lowercase: `[diagram]`, not `[Diagram]`
-- Description starts lowercase after the tag (unless proper noun or code element)
-- Section headers: Title Case (`### Potentially Breaking Changes`)
+
+-   Tags are always lowercase: `[diagram]`, not `[Diagram]`
+-   Description starts lowercase after the tag (unless proper noun or code element)
+-   Section headers: Title Case (`### Potentially Breaking Changes`)
 
 **Description cleanup from PR title:**
-- Remove issue tracker prefixes (e.g. `GLSP-1234:`, `GH-123:`, `ISSUE-456:`)
-- Remove conventional commit prefixes: `fix:`, `feat:`, `chore:`
-- Rephrase bug-report style to changelog style:
-  - BAD: "Edit label UI does not resize on graph zoom"
-  - GOOD: "Fix edit label UI not resizing on graph zoom"
-- Keep concise — one line
+
+-   Remove issue tracker prefixes (e.g. `GLSP-1234:`, `GH-123:`, `ISSUE-456:`)
+-   Remove conventional commit prefixes: `fix:`, `feat:`, `chore:`
+-   Rephrase bug-report style to changelog style:
+    -   BAD: "Edit label UI does not resize on graph zoom"
+    -   GOOD: "Fix edit label UI not resizing on graph zoom"
+-   Keep concise — one line
 
 **Breaking changes:**
-- Describe what changed, why it's breaking, and how to migrate
-- Extract migration sub-items from the PR body's "What it does" section
+
+-   Describe what changed, why it's breaking, and how to migrate
+-   Extract migration sub-items from the PR body's "What it does" section
 
 ---
 
@@ -136,13 +148,15 @@ Pick the most fitting tag from the vocabulary (Step 1.2) based on PR title and b
 Read `CHANGELOG.md` in the repository root.
 
 **Active section detection:**
-- An active section has the `- active` suffix (e.g. `## v2.7.0 - active`)
-- If an active section exists → merge new entries into it
-- If the topmost section is a released version (no `- active` suffix) → create a new active section above it
+
+-   An active section has the `- active` suffix (e.g. `## v2.7.0 - active`)
+-   If an active section exists → merge new entries into it
+-   If the topmost section is a released version (no `- active` suffix) → create a new active section above it
 
 **Creating a new section:**
-- Bump the minor version of `LAST_TAG` (e.g. `v2.6.0` → `v2.7.0`)
-- Insert after the title line, before the first `## ` heading:
+
+-   Bump the minor version of `LAST_TAG` (e.g. `v2.6.0` → `v2.7.0`)
+-   Insert after the title line, before the first `## ` heading:
 
 ```markdown
 ## v2.7.0 - active
@@ -160,9 +174,10 @@ Read `CHANGELOG.md` in the repository root.
 Only include "Potentially Breaking Changes" if there are breaking entries.
 
 **Merging into existing active section:**
-- Check PR numbers against existing entries to avoid duplicates
-- Append new entries to the appropriate subsection
-- Create missing subsections as needed
+
+-   Check PR numbers against existing entries to avoid duplicates
+-   Append new entries to the appropriate subsection
+-   Create missing subsections as needed
 
 ### Step 2.2: Write the updated CHANGELOG.md
 
@@ -185,13 +200,14 @@ Present the diff to the user.
 List any entries flagged as uncertain (category or breaking status) and ask the user to resolve them.
 
 Even if nothing is uncertain, ask:
+
 > "Does everything look correct, or would you like to adjust any entries?"
 
 ### Step 3.3: Collect user feedback
 
-- **Approve as-is** → done (or proceed to Phase 4 if PR was requested)
-- **Request edits** → apply changes, show updated diff, ask again
-- **Resolve uncertain items** → apply, show updated diff
+-   **Approve as-is** → done (or proceed to Phase 4 if PR was requested)
+-   **Request edits** → apply changes, show updated diff, ask again
+-   **Resolve uncertain items** → apply, show updated diff
 
 **Do NOT proceed to Phase 4 unless the user explicitly requests a PR.**
 
@@ -200,11 +216,13 @@ Even if nothing is uncertain, ask:
 ## Phase 4: PR Creation (Optional)
 
 Only execute this phase if the user explicitly requests a PR (either in their initial prompt or after reviewing the changelog). If the user hasn't mentioned a PR, ask after approval:
+
 > "Would you like me to create a PR for this changelog update, or are you done?"
 
 ### Step 4.1: Determine the branch name
 
 Check if `changelog-update` exists on remote:
+
 ```bash
 git ls-remote --heads origin changelog-update
 ```
@@ -229,6 +247,7 @@ Report the PR URL.
 ### Step 4.4: Label referenced PRs
 
 Add the `changelog` label to every PR mentioned in the new entries:
+
 ```bash
 gh pr edit PR_NUMBER --add-label "changelog"
 ```

.github/workflows/e2e-server-pr.yml

@@ -0,0 +1,124 @@
+name: 'E2E Server PR'
+
+concurrency:
+  group: e2e-server-pr-${{ github.event.inputs.server_pr }}
+  cancel-in-progress: true
+
+on:
+  workflow_dispatch:
+    inputs:
+      server_pr:
+        description: 'glsp-server-node PR number to test against'
+        required: true
+        type: string
+      client_pr:
+        description: 'glsp-client PR number (optional, defaults to master)'
+        required: false
+        type: string
+
+jobs:
+  resolve-server-ref:
+    name: Resolve Server PR
+    runs-on: ubuntu-latest
+    outputs:
+      server_ref: ${{ steps.resolve-server.outputs.server_ref }}
+      client_ref: ${{ steps.resolve-client.outputs.client_ref }}
+    steps:
+      - name: Resolve server PR branch
+        id: resolve-server
+        uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7.0.1
+        with:
+          script: |
+            const prNumber = '${{ github.event.inputs.server_pr }}';
+            const { data: pr } = await github.rest.pulls.get({
+              owner: 'eclipse-glsp',
+              repo: 'glsp-server-node',
+              pull_number: parseInt(prNumber)
+            });
+            core.setOutput('server_ref', pr.head.ref);
+            core.info(`Resolved server PR #${prNumber} to branch: ${pr.head.ref}`);
+
+      - name: Resolve client PR branch
+        id: resolve-client
+        if: github.event.inputs.client_pr != ''
+        uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7.0.1
+        with:
+          script: |
+            const prNumber = '${{ github.event.inputs.client_pr }}';
+            const { data: pr } = await github.rest.pulls.get({
+              owner: 'eclipse-glsp',
+              repo: 'glsp-client',
+              pull_number: parseInt(prNumber)
+            });
+            core.setOutput('client_ref', pr.head.ref);
+            core.info(`Resolved client PR #${prNumber} to branch: ${pr.head.ref}`);
+
+  integration-test:
+    name: E2E Server PR
+    needs: [resolve-server-ref]
+    timeout-minutes: 120
+    runs-on: ubuntu-latest
+    env:
+      STANDALONE_URL: 'file://${{ github.workspace }}/glsp-client/examples/workflow-standalone/app/diagram.html'
+      GLSP_SERVER_PORT: '8081'
+      GLSP_SERVER_PLAYWRIGHT_MANAGED: 'false'
+      GLSP_WEBSOCKET_PATH: 'workflow'
+      GLSP_SERVER_DEBUG: 'true'
+      GLSP_SERVER_TYPE: 'node'
+
+    steps:
+      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        with:
+          ref: ${{ needs.resolve-server-ref.outputs.client_ref || 'master' }}
+          path: 'glsp-client'
+
+      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        with:
+          repository: 'eclipse-glsp/glsp-server-node'
+          ref: ${{ needs.resolve-server-ref.outputs.server_ref }}
+          path: 'glsp-server-node'
+
+      - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        with:
+          repository: 'eclipse-glsp/glsp-playwright'
+          path: 'glsp-playwright'
+
+      - uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0
+        with:
+          node-version: '22'
+
+      - name: Build glsp-client
+        run: |
+          cd glsp-client
+          yarn
+
+      - name: Build glsp-server-node
+        run: |
+          cd glsp-server-node
+          yarn
+
+      - name: Start GLSP server
+        run: |
+          cd glsp-server-node
+          yarn start:websocket &
+          echo "Waiting for GLSP server to be ready on port 8081..."
+          timeout 60 bash -c 'until nc -z localhost 8081; do sleep 1; done'
+          echo "GLSP server is ready"
+
+      - name: Build glsp-playwright
+        run: |
+          cd glsp-playwright
+          yarn
+
+      - name: Run Playwright tests
+        id: run_playwright_tests
+        run: |
+          cd glsp-playwright
+          yarn test:standalone
+
+      - name: Upload Playwright report
+        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        if: always()
+        with:
+          name: playwright-report-integration
+          path: glsp-playwright/examples/workflow-test/playwright-report/

examples/workflow-standalone/src/globals.d.ts

@@ -1,2 +1,17 @@
+/********************************************************************************
+ * Copyright (c) 2024-2026 EclipseSource and others.
+ *
+ * This program and the accompanying materials are made available under the
+ * terms of the Eclipse Public License v. 2.0 which is available at
+ * http://www.eclipse.org/legal/epl-2.0.
+ *
+ * This Source Code may also be made available under the following Secondary
+ * Licenses when the conditions for such availability set forth in the Eclipse
+ * Public License v. 2.0 are satisfied: GNU General Public License, version 2
+ * with the GNU Classpath Exception which is available at
+ * https://www.gnu.org/software/classpath/license.html.
+ *
+ * SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
+ ********************************************************************************/
 declare const GLSP_SERVER_HOST: string;
 declare const GLSP_SERVER_PORT: string;

packages/client/src/features/label-edit-ui/label-edit-ui.ts

@@ -1,5 +1,5 @@
 /********************************************************************************
- * Copyright (c) 2024 EclipseSource and others.
+ * Copyright (c) 2024-2026 EclipseSource and others.
  *
  * This program and the accompanying materials are made available under the
  * terms of the Eclipse Public License v. 2.0 which is available at