Merge branch 'master' into worktree-global-shortcuts

Author: leaanthony

.github/workflows/generate-sponsor-image.yml

@@ -10,31 +10,34 @@ jobs:
     name: Update Sponsors
     runs-on: ubuntu-latest
     if: github.repository == 'wailsapp/wails'
+    permissions:
+      contents: write
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
+        with:
+          # Use the bypass-capable token so the auto-commit can push directly
+          # to the protected master branch (same pattern as publish-npm.yml).
+          token: ${{ secrets.WAILS_REPO_TOKEN || github.token }}
 
       - name: Set Node
-        uses: actions/setup-node@v2
+        uses: actions/setup-node@v4
         with:
-          node-version: 20.x
+          node-version: "22"
 
       - name: Update Sponsors
         run: cd scripts/sponsors && chmod 755 ./generate-sponsor-image.sh && ./generate-sponsor-image.sh
         env:
           SPONSORKIT_GITHUB_TOKEN: ${{ secrets.SPONSORS_TOKEN }}
           SPONSORKIT_GITHUB_LOGIN: wailsapp
 
-      - name: Create Pull Request
-        uses: peter-evans/create-pull-request@v6
-        with:
-          commit-message: "chore: update sponsors.svg"
-          add-paths: "website/static/img/sponsors.svg"
-          title: "chore: update sponsors.svg"
-          body: |
-            Auto-generated by the sponsor image workflow
-            
-            [skip ci] [skip actions]
-          branch: update-sponsors
-          base: master
-          delete-branch: true
-          draft: false
+      - name: Commit updated sponsor image
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          if git diff --quiet -- website/static/img/sponsors.svg; then
+            echo "No sponsor changes to commit."
+            exit 0
+          fi
+          git add website/static/img/sponsors.svg
+          git commit -m "chore: update sponsors.svg [skip ci]"
+          git push

.github/workflows/publish-npm.yml

@@ -78,10 +78,10 @@ jobs:
           version: 3.x
           repo-token: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Use Node.js 20
+      - name: Use Node.js 22
         uses: actions/setup-node@v4
         with:
-          node-version: "20"
+          node-version: "22"
 
       - name: Upgrade npm for Trusted Publishing
         # Trusted Publishing (OIDC) requires npm >= 11.5.1.
@@ -109,15 +109,43 @@ jobs:
           npm test
           npm run build
 
+      - name: Verify generated artifacts
+        # Fail the publish if (re)generation did not produce the expected
+        # outputs — both the npm package payload (dist/, gitignored, what gets
+        # published) and the tracked bundled runtime that is committed back to
+        # master below. A missing/empty file here means a silent build failure.
+        working-directory: v3
+        run: |
+          set -euo pipefail
+          required=(
+            "internal/assetserver/bundledassets/runtime.js"
+            "internal/assetserver/bundledassets/runtime.debug.js"
+            "internal/runtime/desktop/@wailsio/runtime/dist/runtime.js"
+          )
+          for f in "${required[@]}"; do
+            if [ ! -s "$f" ]; then
+              echo "::error::expected generated artifact missing or empty: v3/$f"
+              exit 1
+            fi
+          done
+          echo "All expected runtime artifacts were generated."
+
       - name: Bump version
         id: bump-version
         working-directory: v3/internal/runtime/desktop/@wailsio/runtime
         run: |
           echo "version=$(npm --no-git-tag-version --force version prerelease)" >> "$GITHUB_OUTPUT"
 
-      - name: Commit changes
+      - name: Commit regenerated runtime + version bump
+        # Commit ALL regenerated tracked files back to master, not just the
+        # version bump: the bundled runtime (internal/assetserver/bundledassets),
+        # generated events (v3/pkg/events/events.go) and TypeDoc output all come
+        # from `task runtime:build` and must stay in sync with the published
+        # package. dist/ is gitignored, so `git add -A` will not commit it.
         run: |
-          git add .
+          git add -A
+          echo "Files committed back to master:"
+          git status --short
           git commit -m "[skip ci] Publish @wailsio/runtime ${{ steps.bump-version.outputs.version }}"
           git push
 
@@ -127,4 +155,7 @@ jobs:
         # Requires a Trusted Publisher to be configured for @wailsio/runtime on
         # npmjs.com (repo: wailsapp/wails, workflow: publish-npm.yml).
         working-directory: v3/internal/runtime/desktop/@wailsio/runtime
-        run: npm publish --access public
+        # --tag latest: v3 ships prerelease (alpha.N) as the default dist-tag,
+        # matching the templates' "@wailsio/runtime": "latest" pin. npm >= 11
+        # requires an explicit --tag to publish a prerelease as latest.
+        run: npm publish --access public --tag latest

docs/astro.config.mjs

@@ -295,7 +295,6 @@ export default defineConfig({
         {
           label: "Mobile",
           collapsed: true,
-          badge: { text: "Experimental", variant: "caution" },
           items: [
             { label: "Overview", link: "/guides/mobile" },
             { label: "Your First Mobile App", link: "/guides/mobile/first-mobile-app" },
@@ -305,6 +304,17 @@ export default defineConfig({
           ],
         },
 
+        // Experimental - opt-in experiments we're gathering feedback on
+        {
+          label: "Experimental",
+          collapsed: true,
+          items: [
+            { label: "Overview", link: "/experimental" },
+            { label: "Wake", link: "/experimental/wake" },
+            { label: "LLM Control (MCP)", link: "/guides/mcp-service" },
+          ],
+        },
+
         // Guides - Task-oriented patterns (Netflix: When to use it, when not to use it)
         {
           label: "Guides",
@@ -361,7 +371,7 @@ export default defineConfig({
               label: "Advanced Topics",
               collapsed: true,
               items: [
-                { label: "Server Build", link: "/guides/server-build", badge: { text: "Experimental", variant: "caution" } },
+                { label: "Server Build", link: "/guides/server-build" },
                 { label: "Custom Templates", link: "/guides/advanced/custom-templates" },
                 { label: "WML (Wails Markup)", link: "/guides/advanced/wml" },
                 { label: "Panic Handling", link: "/guides/advanced/panic-handling" },

docs/src/content/docs/changelog.mdx

@@ -31,6 +31,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 */
 ## [Unreleased]
 
+## v3.0.0-alpha2.107 - 2026-06-27
+
+## Added
+- Add experimental Wake documentation with sidebar navigation in [PR](https://github.com/wailsapp/wails/pull/5613) by @leaanthony
+
 ## v3.0.0-alpha2.106 - 2026-06-24
 
 ## Changed

docs/src/content/docs/experimental/index.mdx

@@ -0,0 +1,76 @@
+---
+title: Experimental Features
+description: A home for in-progress experiments in Wails v3 — what they are, why they exist, and how to give feedback.
+sidebar:
+    label: Overview
+    order: 0
+    badge:
+        text: Experimental
+        variant: caution
+---
+
+import { Aside, CardGrid, LinkCard } from '@astrojs/starlight/components';
+
+<Aside type="caution" title="Here be experiments">
+Everything in this section is, by definition, an experiment. Features here are
+opt-in, off by default, and may change shape, get renamed, or be removed
+entirely between releases. Don't build anything load-bearing on them without
+being ready for churn.
+</Aside>
+
+## What "Experimental" means
+
+Wails ships experiments in the open. An experiment is an idea we think is
+promising enough to put in your hands early — but one we haven't fully
+committed to yet. We're publishing it *because* we want to learn from real use
+before deciding whether it becomes a permanent, supported part of Wails.
+
+That means a few things are true of everything in this section:
+
+- **It's opt-in.** Experiments never change the default behaviour of `wails3`.
+  You turn them on deliberately (usually with an environment variable or a
+  build flag), and with them off, nothing about your existing workflow
+  changes.
+- **It might not survive.** Some experiments graduate into stable features.
+  Others get reworked beyond recognition, or dropped. We'd rather try things
+  in public and learn fast than ship only what we're already certain about.
+- **The API isn't frozen.** Names, flags, defaults and behaviour can shift
+  between releases while an experiment is finding its shape. Release notes will
+  call out the changes, but don't expect the stability guarantees that stable
+  features carry.
+
+## We want your feedback
+
+This is the important part. Experiments live or die by what we hear back from
+people actually using them. If you try one of these, we genuinely want to know:
+
+- Did it work for your project? Where did it fall down?
+- Was it faster / clearer / nicer — or not worth the switch?
+- What would have to be true for you to use it by default?
+
+The most useful feedback is concrete: what you ran, what you expected, what
+actually happened. Each experiment has its own thread in the **Experiments**
+category on GitHub Discussions:
+
+<CardGrid>
+  <LinkCard
+    title="Experiments Discussions"
+    description="Find the thread for the experiment you're using and tell us how it worked out, what broke, or what's missing."
+    href="https://github.com/wailsapp/wails/discussions/categories/experiments"
+  />
+</CardGrid>
+
+## Current experiments
+
+<CardGrid>
+  <LinkCard
+    title="Wake"
+    description="An alternative, Wails-aware build runner for your existing Taskfiles. Faster incremental builds, structured output, parallel by default."
+    href="/experimental/wake"
+  />
+  <LinkCard
+    title="LLM Control (MCP)"
+    description="A built-in Model Context Protocol server that lets LLM agents inspect, test, and drive a running Wails app — no user code required, enabled with a build tag."
+    href="/guides/mcp-service"
+  />
+</CardGrid>