build(deps): Bump github.com/wailsapp/wails/v3 from 3.0.0-beta.5 to 3.0.0-beta.6 - #2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
force-pushed
the
dependabot/go_modules/github.com/wailsapp/wails/v3-3.0.0-beta.5
branch
2 times, most recently
from
August 12, 2026 03:22
d363b59 to
562b8ad
Compare
6 tasks
alicoding
added a commit
that referenced
this pull request
Aug 12, 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>
Bumps [github.com/wailsapp/wails/v3](https://github.com/wailsapp/wails) from 3.0.0-beta.5 to 3.0.0-beta.6. - [Release notes](https://github.com/wailsapp/wails/releases) - [Commits](wailsapp/wails@v3.0.0-beta.5...v3.0.0-beta.6) --- updated-dependencies: - dependency-name: github.com/wailsapp/wails/v3 dependency-version: 3.0.0-beta.5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/go_modules/github.com/wailsapp/wails/v3-3.0.0-beta.5
branch
from
August 12, 2026 20:43
562b8ad to
ec87fe8
Compare
6 tasks
alicoding
added a commit
that referenced
this pull request
Aug 13, 2026
Read the full beta.6 release notes/changelog (3-commit range, v3.0.0-beta.5...v3.0.0-beta.6) before touching anything, per this goal's ask for extra scrutiny on wails bumps. Findings: - (a) Dock bounce/badge: beta.6 adds macOS Dock bounce for window flashing (wailsapp/wails#5921). Confirmed against the actual PR diff -- it extends the existing WebviewWindow.Flash(enabled bool) to macOS via [NSApp requestUserAttention:NSInformationalRequest], a one-shot self-completing bounce, not a persistent badge (disabling is a no-op). Go-only (webview_window.go, webview_window_darwin.go), no new JS/TS binding. Mill doesn't call Flash anywhere today -- an available, unused unlock, not adopted here (composition-boundary question for a future goal, not a mechanical dependency bump). - (b) Window/panel APIs: no NSWindow/NSPanel or activation-policy changes in beta.6. ADR-0033's "no non-activating-panel mechanism at beta.4" (settingsservice_panel.go) remains accurate and unchanged. - @wailsio/runtime: npm never published a 3.0.0-beta.6 tarball at all (registry jumps 3.0.0-beta.5 -> 3.0.0-beta.7 directly). Verified both beta.6 feature PRs (#5930 bounded event storage/ordered delivery, #5921 dock bounce) touch Go-only files with zero JS/TS runtime changes, so the frontend stays exact-pinned at 3.0.0-beta.5 with no protocol-compatibility risk -- there is no "matching" beta.6 npm version to move to. wails3 CLI upgraded to beta.6 for binding generation (`task common:generate:bindings`) -- zero diff, confirming no bound method signature or generation-format changes in this release, same as the beta.5 pass. Also fixed a pre-existing drift in .github/workflows/release.yml: its wails3 CLI install was still pinned at beta.4, never updated when go.mod moved to beta.5 -- now matches go.mod at beta.6. go.sum: only wails/v3 and its transitive golang.org/x/net (v0.55.0 -> v0.56.0) moved. Claude-Session: https://claude.ai/code/session_018pkViCNAuZp2vBv2K9AbUh Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
Looks like github.com/wailsapp/wails/v3 is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/go_modules/github.com/wailsapp/wails/v3-3.0.0-beta.5
branch
August 13, 2026 03:17
alicoding
added a commit
that referenced
this pull request
Aug 13, 2026
…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
added a commit
that referenced
this pull request
Aug 15, 2026
) Verified before adopting, not assumed: ls-lint's own docs frame it as naming-CONVENTION validation, not an "allowlist" feature, which made a first read look like a rejection. Checked further -- its regex: rule, applied correctly, achieves the same practical effect Mill needs (flag any root .go file whose name doesn't match an established family). Two real config mistakes caught only by testing against an intentionally -impossible regex before trusting a real one, not by reading the docs alone: - A `.: .go: regex:...` directory-key wrapper, modeled on the one scoped-subdirectory example in ls-lint's own README, silently no-ops -- confirmed by watching an impossible regex produce zero errors against 100+ real .go files. There is no dedicated "root only" syntax; a bare `.go:` key directly under `ls:` applies recursively to the whole tree instead. - Fixed by inverting the scoping: `ignore: internal` excludes the one other place .go files legitimately live, since Go package-naming convention already governs internal/domain/* and internal/adapters/* and this rule shouldn't touch them. Re-verified the same impossible-regex probe now correctly flags only root files, then installed the real pattern and confirmed it passes on the current (correct) tree and fails on a deliberately introduced bad file (removed after confirming), per .claude/rules/testing.md's own "prove it catches what it's for" discipline. The real pattern is derived from Mill's actual current root file list (not an idealized "main + *service + *_test" guess, which would have immediately flagged idgen.go, configuremcpserver.go, and the whole ADR-0006 trigger* dispatch family as violations) -- and left open-ended for the trigger family (trigger[a-z]*) so a future triggerwebhook.go needs no config change. Installed via `go install .../cmd/ls_lint@v2.3.1`, matching how this repo already sets up gopls/wails3 -- no npm/Homebrew dependency. Wired into both CI (new root-file-naming job) and Lefthook (new root-file-naming hook, glob-scoped to *.go), and documented as a one-time local prerequisite in CLAUDE.md alongside golangci-lint. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FYwojT8GdUbYSoggbvEFft
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>
alicoding
added a commit
that referenced
this pull request
Aug 15, 2026
Read the full beta.6 release notes/changelog (3-commit range, v3.0.0-beta.5...v3.0.0-beta.6) before touching anything, per this goal's ask for extra scrutiny on wails bumps. Findings: - (a) Dock bounce/badge: beta.6 adds macOS Dock bounce for window flashing (wailsapp/wails#5921). Confirmed against the actual PR diff -- it extends the existing WebviewWindow.Flash(enabled bool) to macOS via [NSApp requestUserAttention:NSInformationalRequest], a one-shot self-completing bounce, not a persistent badge (disabling is a no-op). Go-only (webview_window.go, webview_window_darwin.go), no new JS/TS binding. Mill doesn't call Flash anywhere today -- an available, unused unlock, not adopted here (composition-boundary question for a future goal, not a mechanical dependency bump). - (b) Window/panel APIs: no NSWindow/NSPanel or activation-policy changes in beta.6. ADR-0033's "no non-activating-panel mechanism at beta.4" (settingsservice_panel.go) remains accurate and unchanged. - @wailsio/runtime: npm never published a 3.0.0-beta.6 tarball at all (registry jumps 3.0.0-beta.5 -> 3.0.0-beta.7 directly). Verified both beta.6 feature PRs (#5930 bounded event storage/ordered delivery, #5921 dock bounce) touch Go-only files with zero JS/TS runtime changes, so the frontend stays exact-pinned at 3.0.0-beta.5 with no protocol-compatibility risk -- there is no "matching" beta.6 npm version to move to. wails3 CLI upgraded to beta.6 for binding generation (`task common:generate:bindings`) -- zero diff, confirming no bound method signature or generation-format changes in this release, same as the beta.5 pass. Also fixed a pre-existing drift in .github/workflows/release.yml: its wails3 CLI install was still pinned at beta.4, never updated when go.mod moved to beta.5 -- now matches go.mod at beta.6. go.sum: only wails/v3 and its transitive golang.org/x/net (v0.55.0 -> v0.56.0) moved. Claude-Session: https://claude.ai/code/session_018pkViCNAuZp2vBv2K9AbUh 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
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.
Bumps github.com/wailsapp/wails/v3 from 3.0.0-beta.5 to 3.0.0-beta.6.
Release notes
Sourced from github.com/wailsapp/wails/v3's releases.
Commits
114eef7chore(v3): bump to v3.0.0-beta.6 and update changelog [skip ci]dc806d7chore(changelog): auto-add entry for PR #5930 — fix(v3): keep oversized event...684d1cefix(v3): keep oversized event payloads out of evaluateJavaScript (#5930)9983f65chore(changelog): auto-add entry for PR #5931 — fix(v3): make asset server fl...d79d990fix(v3): make asset server flush semantics honest (#5931)07cbabffix(v3/macos): marshal main menu updates to UI thread (#5910)cbaeabcfix(v3/w32): call GetStockObject instead of GetDeviceCaps (#5875)be29bfbchore(changelog): auto-add entry for PR #5921 — Feat/mac dock bounce on flash30452dfFeat/mac dock bounce on flash (#5921)a6f414bchore(changelog): auto-add entry for PR #5924 — [v2] Fix nil pointer crash an...