chore: bump wails/v3 beta.4 -> beta.5 + @wailsio/runtime to match (Dependabot #2) - #32
Merged
Conversation
…pendabot #2) Read the full beta.5 release notes/changelog and diffed the actual commit range (v3.0.0-beta.4...v3.0.0-beta.5) before touching anything, per this goal's explicit ask for extra scrutiny on this bump. Findings: - beta.5 is a small, 3-commit bug-fix release: macOS activation-policy focus-steal fix (application_darwin.go), two Linux GTK/WebKit fixes (linux_cgo*.go, webview_window_linux.go). No other files changed. - (a) NSWindow/NSPanel: no window/panel API changes at all -- application_darwin.go's only change is activation-policy-gated activateIgnoringOtherApps, unrelated to window/panel class. ADR-0033's documented NSWindow-only limitation (settingsservice_panel.go) is UNCHANGED by this release -- no non-activating-panel mechanism to adopt, nothing to follow up on yet. - (b) Dock bounce/badge: confirmed absent by grepping the actual @wailsio/runtime@3.0.0-beta.5 npm tarball for "bounce"/"badge" -- zero matches. The prior session's note that beta.6-era runtime unlocks dock-bounce is consistent with this: it is not in beta.5. @wailsio/runtime was pinned to the literal string "latest" in package.json (not an actual semver range), which is why it had silently drifted to a resolved beta.1 in package-lock.json for months despite go.mod being on beta.4 -- "latest" only re-resolves when the lockfile doesn't already satisfy it, so it never moved on its own. Fixed to an exact "3.0.0-beta.5" pin, matching the Go side exactly (PR #6, the Dependabot PR for this exact bump, was already closed -- this supersedes it properly instead of leaving the drift). Bindings: regenerated via `task common:generate:bindings` (both with the pre-existing beta.4 wails3 CLI and after upgrading the installed CLI to match beta.5) -- zero diff either time, confirming no bound method signature or generation-format changes in this release. Full local suite green: go vet, golangci-lint (0 issues), go test (-race -cover, all packages ok), go build (desktop + server tags), eslint/tsc/boundaries/vitest (231/231)/frontend build, file-loc-limit, root-file-naming, rules-frontmatter. Local full e2e run (55 spec files): 1 apparent failure in layout.spec.ts's build-badge test, root-caused to an environment artifact specific to this sandboxed git-worktree checkout, not a real regression -- go build's automatic VCS stamping (-buildvcs=auto) embedded a DIFFERENT branch's commit (docs/ratified-queue-reorder's tip) into the e2e server binary's BuildInfo.Revision, rather than this worktree's own checked-out HEAD, even though `git rev-parse HEAD` in the exact same shell/cwd correctly reports this branch's commit -- reproduced deterministically across three separate rebuilds. CI checks out a plain, non-worktree clone, so this class of mismatch cannot occur there; treating CI's run (this branch's actual DoD gate) as authoritative rather than chasing a local-sandbox-only artifact. Two other local-only test hiccups (quick-panel status-text race, seed-completeness run-timing) passed on Playwright's own automatic retry, consistent with ordinary 4-worker local resource contention rather than anything wails-related. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft
alicoding
enabled auto-merge (squash)
August 12, 2026 20:31
alicoding
added a commit
that referenced
this pull request
Aug 15, 2026
…pendabot #2) (#32) Read the full beta.5 release notes/changelog and diffed the actual commit range (v3.0.0-beta.4...v3.0.0-beta.5) before touching anything, per this goal's explicit ask for extra scrutiny on this bump. Findings: - beta.5 is a small, 3-commit bug-fix release: macOS activation-policy focus-steal fix (application_darwin.go), two Linux GTK/WebKit fixes (linux_cgo*.go, webview_window_linux.go). No other files changed. - (a) NSWindow/NSPanel: no window/panel API changes at all -- application_darwin.go's only change is activation-policy-gated activateIgnoringOtherApps, unrelated to window/panel class. ADR-0033's documented NSWindow-only limitation (settingsservice_panel.go) is UNCHANGED by this release -- no non-activating-panel mechanism to adopt, nothing to follow up on yet. - (b) Dock bounce/badge: confirmed absent by grepping the actual @wailsio/runtime@3.0.0-beta.5 npm tarball for "bounce"/"badge" -- zero matches. The prior session's note that beta.6-era runtime unlocks dock-bounce is consistent with this: it is not in beta.5. @wailsio/runtime was pinned to the literal string "latest" in package.json (not an actual semver range), which is why it had silently drifted to a resolved beta.1 in package-lock.json for months despite go.mod being on beta.4 -- "latest" only re-resolves when the lockfile doesn't already satisfy it, so it never moved on its own. Fixed to an exact "3.0.0-beta.5" pin, matching the Go side exactly (PR #6, the Dependabot PR for this exact bump, was already closed -- this supersedes it properly instead of leaving the drift). Bindings: regenerated via `task common:generate:bindings` (both with the pre-existing beta.4 wails3 CLI and after upgrading the installed CLI to match beta.5) -- zero diff either time, confirming no bound method signature or generation-format changes in this release. Full local suite green: go vet, golangci-lint (0 issues), go test (-race -cover, all packages ok), go build (desktop + server tags), eslint/tsc/boundaries/vitest (231/231)/frontend build, file-loc-limit, root-file-naming, rules-frontmatter. Local full e2e run (55 spec files): 1 apparent failure in layout.spec.ts's build-badge test, root-caused to an environment artifact specific to this sandboxed git-worktree checkout, not a real regression -- go build's automatic VCS stamping (-buildvcs=auto) embedded a DIFFERENT branch's commit (docs/ratified-queue-reorder's tip) into the e2e server binary's BuildInfo.Revision, rather than this worktree's own checked-out HEAD, even though `git rev-parse HEAD` in the exact same shell/cwd correctly reports this branch's commit -- reproduced deterministically across three separate rebuilds. CI checks out a plain, non-worktree clone, so this class of mismatch cannot occur there; treating CI's run (this branch's actual DoD gate) as authoritative rather than chasing a local-sandbox-only artifact. Two other local-only test hiccups (quick-panel status-text race, seed-completeness run-timing) passed on Playwright's own automatic retry, consistent with ordinary 4-worker local resource contention rather than anything wails-related. Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
github.com/wailsapp/wails/v3beta.4 -> beta.5 (Dependabot build(deps): Bump github.com/wailsapp/wails/v3 from 3.0.0-beta.5 to 3.0.0-beta.6 #2) and@wailsio/runtimeto the matching3.0.0-beta.5(superseding PR build(deps): Bump @wailsio/runtime from 3.0.0-beta.1 to 3.0.0-beta.5 in /frontend #6, already closed but leaving the npm package drifted).Findings requested by the goal brief
(a) NSWindow/NSPanel (ADR-0033's Quick Panel focus-steal limitation): No window/panel API changes in beta.5 at all. The only darwin file touched (
application_darwin.go) is an activation-policy-gated fix foractivateIgnoringOtherApps(background/agent apps no longer steal focus at launch) -- unrelated to the window/panel class Wails creates. ADR-0033's documented NSWindow-only limitation is unchanged -- nothing to follow up on yet, no redesign attempted.(b) Dock bounce/badge: Confirmed absent from beta.5 by grepping the actual
@wailsio/runtime@3.0.0-beta.5npm tarball for "bounce"/"badge" -- zero matches. Consistent with the prior session's note that this lands in beta.6+, not beta.5.Also fixed
@wailsio/runtimewas pinned to the literal string"latest"inpackage.json(not a real semver range) -- which is why it had silently drifted to a resolvedbeta.1in the lockfile for months despitego.modbeing on beta.4 ("latest"only re-resolves when the lockfile doesn't already satisfy it). Repinned to an exact"3.0.0-beta.5", matching the Go side.Bindings
Regenerated via
task common:generate:bindings, both with the pre-existing beta.4wails3CLI and again after upgrading the installed CLI to beta.5 -- zero diff either time. No bound method signature or generation-format changes in this release.Test plan
go vet,golangci-lint(0 issues),go test -race -cover(all packages ok)go build(desktop + server tags) -- both greennpm run lint/tsc/boundaries/test(231/231)/build-- all greenlayout.spec.ts's build-badge test, root-caused to a sandboxed-git-worktree-specific artifact --go build's automatic VCS stamping embedded a different branch's commit intoBuildInfo.Revisionthan this worktree's own checked-out HEAD, reproduced deterministically across 3 rebuilds, even thoughgit rev-parse HEADin the identical shell/cwd is correct. CI checks out a plain non-worktree clone, so this can't occur there -- treating CI as the authoritative gate for this one. Two other local-only hiccups (quick-panel status race, seed-completeness run timing) passed on Playwright's automatic retry, consistent with ordinary local resource contention.🤖 Generated with Claude Code
https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft