build(deps): Bump @wailsio/runtime from 3.0.0-beta.1 to 3.0.0-beta.5 in /frontend - #6
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
dependabot
Bot
added
dependencies
Bumps [@wailsio/runtime](https://github.com/wailsapp/wails/tree/HEAD/v3/internal/runtime/desktop/@wailsio/runtime) from 3.0.0-beta.1 to 3.0.0-beta.5. - [Release notes](https://github.com/wailsapp/wails/releases) - [Commits](https://github.com/wailsapp/wails/commits/v3.0.0-beta.5/v3/internal/runtime/desktop/@wailsio/runtime) --- updated-dependencies: - dependency-name: "@wailsio/runtime" 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
force-pushed
the
dependabot/npm_and_yarn/frontend/wailsio/runtime-3.0.0-beta.5
branch
from
August 12, 2026 02:03
665342e to
25f01b9
Compare
Contributor
Author
|
Looks like @wailsio/runtime is no longer updatable, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/frontend/wailsio/runtime-3.0.0-beta.5
branch
August 12, 2026 07:25
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>
6 tasks
alicoding
added a commit
that referenced
this pull request
Aug 13, 2026
Command grows an optional extraBindings: KeyCombo[] alongside the existing 1:1 defaultBinding (shared/commands.ts, backward-compatible). shared/keybinding.ts's keyFromEventCode gains Slash support -- the '/' key is shift-independent like every other key here, so ⌘/ vs ⌘? (the Shift+/ glyph) is captured purely as a mod difference on the same physical key. palette.open carries both as extraBindings, checked against the full registry + RESERVED_COMBOS first (no collision -- nothing else uses '/'). dispatchCommandForEvent checks a command's effective (override- aware) primary plus its extras on every dispatch; extras themselves are deliberately not override-checked this pass -- Settings' recorder- based rebinding UI still edits only the primary, and extras render as read-only secondary KeyComboChips next to it (views/KeyboardShortcutsSection.tsx). Vitest covers dispatch-matches-either-binding, override-doesn't- disable-extras, and the no-extraBindings backward-compat case; keymap.spec.ts gained a live ⌘/ and ⌘⇧/ -> palette-opens case and a Settings-renders-the-two-read-only-chips case. Claude-Session: https://claude.ai/code/session_018pkViCNAuZp2vBv2K9AbUh Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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 13, 2026
Command grows an optional extraBindings: KeyCombo[] alongside the existing 1:1 defaultBinding (shared/commands.ts, backward-compatible). shared/keybinding.ts's keyFromEventCode gains Slash support -- the '/' key is shift-independent like every other key here, so ⌘/ vs ⌘? (the Shift+/ glyph) is captured purely as a mod difference on the same physical key. palette.open carries both as extraBindings, checked against the full registry + RESERVED_COMBOS first (no collision -- nothing else uses '/'). dispatchCommandForEvent checks a command's effective (override- aware) primary plus its extras on every dispatch; extras themselves are deliberately not override-checked this pass -- Settings' recorder- based rebinding UI still edits only the primary, and extras render as read-only secondary KeyComboChips next to it (views/KeyboardShortcutsSection.tsx). Vitest covers dispatch-matches-either-binding, override-doesn't- disable-extras, and the no-extraBindings backward-compat case; keymap.spec.ts gained a live ⌘/ and ⌘⇧/ -> palette-opens case and a Settings-renders-the-two-read-only-chips case. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018pkViCNAuZp2vBv2K9AbUh
alicoding
added a commit
that referenced
this pull request
Aug 15, 2026
…ent registry semantics Three independent, verified changes (goal-scoped work, tasks #1/#4/#6): - task build/package/build:server now echo their real output path on success, and task run's darwin/linux/windows tasks gained a missing deps: on build:native -- previously `task run` assumed a binary already existed and would fail on a fresh clone, despite its name and summary implying it's a standalone build+launch command (run:server already had this right; desktop run: didn't). - internal/adapters/execution.New now takes a full DSN (databaseURL) instead of hardcoding "sqlite:"+dbPath internally. DBOS itself already accepts Postgres/CockroachDB DSNs; the scheme choice moves to the caller (main.go), which now reads MILL_EXECUTION_DATABASE_URL as an override, falling back to the existing MILL_EXECUTION_DB_PATH/default sqlite path unchanged. A regulated deployment needing an externally managed audit database gets there via config, not an adapter rewrite. - The three ADR-0006/ADR-0015 self-registration registries (RegisterNodeType, RegisterTrigger, RegisterAuthStrategy) have two different duplicate-key behaviors (panic vs silent overwrite), undocumented until now. Recorded on all three functions plus a SPEC.md cross-reference -- not a decision, just making a real, previously-invisible inconsistency visible. Verified: go vet, golangci-lint (0 issues), go test ./internal/... -race -cover (all pass), go build for both desktop and CGO_ENABLED=0-equivalent server tags, check-loc.sh, check-rules-frontmatter.sh. Frontend checks skipped -- zero frontend files touched, matching lefthook.yml's own glob scoping. Taskfile run: fix verified via `task --dry` (confirms build:native now runs before launch) plus one live task package run earlier in the session; full live task run execution was blocked by resource contention with an unrelated, pre-existing `task dev` session on this machine and deliberately not forced. 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
Command grows an optional extraBindings: KeyCombo[] alongside the existing 1:1 defaultBinding (shared/commands.ts, backward-compatible). shared/keybinding.ts's keyFromEventCode gains Slash support -- the '/' key is shift-independent like every other key here, so ⌘/ vs ⌘? (the Shift+/ glyph) is captured purely as a mod difference on the same physical key. palette.open carries both as extraBindings, checked against the full registry + RESERVED_COMBOS first (no collision -- nothing else uses '/'). dispatchCommandForEvent checks a command's effective (override- aware) primary plus its extras on every dispatch; extras themselves are deliberately not override-checked this pass -- Settings' recorder- based rebinding UI still edits only the primary, and extras render as read-only secondary KeyComboChips next to it (views/KeyboardShortcutsSection.tsx). Vitest covers dispatch-matches-either-binding, override-doesn't- disable-extras, and the no-extraBindings backward-compat case; keymap.spec.ts gained a live ⌘/ and ⌘⇧/ -> palette-opens case and a Settings-renders-the-two-read-only-chips case. 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 @wailsio/runtime from 3.0.0-beta.1 to 3.0.0-beta.5.
Release notes
Sourced from @wailsio/runtime's releases.
... (truncated)
Commits
a3936a5[skip ci] Publish@wailsio/runtime3.0.0-beta.1