Fails the build when .github/workflows/actions.lock stops matching the
workflows, or when a locked pin no longer verifies upstream, so a stale or
tampered lockfile cannot go unnoticed between dependency updates.
Mutable action tags are a supply-chain risk: a moved tag runs different code
without a diff. Every workflow action is now pinned through
.github/workflows/actions.lock, and CI verifies the lockfile so an out-of-sync
or tampered one fails instead of running.
release.yml also runs nightly on main with craft-common-actions' dry-run: every release build
except macOS, with nothing signed, pushed or drafted. Breakage that only the release build hits
(riscv64, Flatpak, FreeBSD, packaging) then shows up the next morning instead of on release
day, as it did on 11 Nov 2026.
The FreeBSD jobs in release.yml were kept here only while the repo was private, as their comment
says, so they ran on a larger runner. The repo is public now. They also install the VM host's qemu
without the shared fallback mirrors, so the v0.4.0 release failed at that step while ubuntu.com
did not resolve. Remove them and let the shared release workflow build FreeBSD (has-freebsd
defaults to true).
Clears all 69 open SonarCloud issues.
- `packaging/{linux,macos,freebsd,web}/*.sh`: `[[ ]]` in place of `[ ]` for bash tests (SonarCloud shell:S7688). Every script has a bash shebang; no test uses `-a`/`-o`, escaped parentheses or an unquoted pattern on the right of `=`. `bash -n` passes on each.
- `packaging/web/package.sh`: the wasm size override is read as base 10 (`$((10#…))`), since `-gt` inside `[[` evaluates its operands arithmetically (a leading zero would read as octal). Same as photocraft.
- `crates/ui-egui/src/property/input.rs`: the reversed-limits slider test passes its limits through variables, as imported limits arrive, instead of a literal `3.0..=2.0` (rust:S7432). Same range, same test.
Compile and tests are left to CI.
Retain sampler insertion, graph items, annotation editing, metadata and menu fixes. Integrate function search and quick-insert toolbars, deduplicate categorized search results, and apply current search text before selection.
The toolbar's New graph, Open package, Save and Export buttons stayed
enabled behind a dialog and did nothing when clicked. They now follow
the same rule as the menu items.
Node search takes no keys, focus or outside clicks while input is
blocked and does not open behind a blocker. The add-node menu's letter
filter does not change while blocked. Sample tiles are disabled behind
a dialog. A file dialog keeps its commands enabled only when nothing
else blocks input. The control protocol notes that the installed-update
notice does not block.
Delete edited the package behind the Save, Discard, Cancel prompt, and
floating OS windows stayed live behind every dialog, because no single
function said whether input was blocked.
Modality::capture answers it from the app's dialogs, the unsaved prompt,
native file dialogs, the update prompt and result window, and egui's
modal layer. Shortcuts, Graph, Function and FX-Map keys, the node search
and add menus, file drops, floating OS windows, Home's actions and menu
items all read it. Home and the Shortcuts list do not block.
Behind a file dialog, the commands that show one still run, so File >
Open brings a hidden macOS Open panel forward.
ui.menu.invoke now returns an error behind a dialog instead of ok,
ui.menu.list reports those items as disabled, and package_save without a
path in bridge mode returns the same error. command.run is unchanged.
Floating panels drawn inside the main window, as on the web build, still
take clicks behind a dialog until the dialogs use egui's modal layer.