Repository navigation
Release to npm - #528
Merged
Merged
Release to npm#528
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #528 +/- ##
=======================================
Coverage 95.81% 95.81%
=======================================
Files 93 93
Lines 1794 1794
Branches 312 312
=======================================
Hits 1719 1719
Misses 73 73
Partials 2 2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
lkostrowski
previously approved these changes
Aug 24, 2026
saleor-deployments
Bot
force-pushed
the
changeset-release/main
branch
from
August 26, 2026 09:25
2531e99 to
e0b400b
Compare
saleor-deployments
Bot
force-pushed
the
changeset-release/main
branch
from
September 23, 2026 07:08
e0b400b to
c83bd4e
Compare
saleor-deployments
Bot
force-pushed
the
changeset-release/main
branch
from
October 1, 2026 08:42
c83bd4e to
f9447e6
Compare
saleor-deployments
Bot
force-pushed
the
changeset-release/main
branch
from
October 5, 2026 14:35
f9447e6 to
29aa185
Compare
lkostrowski
enabled auto-merge (squash)
October 5, 2026 14:36
lkostrowski
approved these changes
Oct 5, 2026
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@saleor/app-sdk@1.16.0
Minor Changes
c94ac69: Forward Dashboard-owned keyboard shortcuts out of the app iframe so global handlers (e.g. Cmd+K) keep working while the app has focus.
Public API
shortcutsChangedevent — Dashboard → app, full-replace list of{ id, key, metaKey?, ctrlKey?, altKey?, shiftKey? }. Stored as the optionalappBridgeState.dashboardShortcuts(always set by AppBridge, defaults to[]). Entries without a non-emptyidandkeyare dropped with a warning.new AppBridge({ forwardKeyboardShortcuts })— defaulttrue. Passfalseto disable, or{ shouldForward(event) }to claim a registered chord back for the app.matchDashboardShortcut,createShortcutForwarder— matcher and listener used internally; exported for tests and non-React hosts.AppBridge.destroy()— detaches the instance from the window: stops forwarding shortcuts, stops receiving Dashboard events, and drops all subscribers. Safe to call more than once.AppBridgeProvidernow destroys the AppBridge it created when it unmounts (an instance passed viaappBridgeInstanceis left alone, since the caller owns it). Without this, React StrictMode's double-mount left two live bridges on the same window and every shortcut and event was handled twice.Forwarding is a no-op until the Dashboard advertises a registry, so older Dashboards are unchanged.
There is deliberately no
actions.TriggerShortcut(...)helper. ThetriggerShortcutaction is dispatched by AppBridge itself in response to a real keypress that matched the advertised registry, and its payload only describes that keypress — apps should not synthesize input on the user's behalf. A capability an app wants to invoke directly (e.g. opening the command palette) belongs behind its own action instead.Dashboard contract (implement in the Dashboard repo alongside this release)
After
handshake,postMessageto the app iframe:Full replace, not a delta. Send again when the owned set changes (route/context). Send
{ shortcuts: [] }to revoke.Handle
triggerShortcutinuseAppActions:payload.shortcutIdand run that command.{ type: "response", payload: { actionId, ok: true } }.ok: false(do not stay silent — silence times outdispatchafter 10s).Move focus out of the iframe when the resulting UI opens (e.g.
.focus()the command-palette input). Without this, subsequent typing stays in the app.keyisKeyboardEvent.key, matched case-insensitively. Modifier flags are exact: registering Cmd+K does not swallow Cmd+Shift+K.f01c044: Added optional
deprecationReasonfield toAppManifest. Apps can declare their deprecation and point users to a replacement app. Supported in Saleor 3.23+.