Release 9.7.0#321
Merged
Merged
Conversation
Release 9.6.0
Rollout of the release automation piloted in sandwich-sdk: release.yml (workflow_dispatch) runs the whole release via the shared workflow — version calculation, release PRs, bot approval, CI gate, merge — and publish_release.yml creates the GitHub release when the release PR merges to main, so the publish workflow fires on release:[released] as before. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GjdKcoaoecn6TKWmnUZzji
…DEV-1181) Deleted: manual prerelease dispatch lanes (replaced by the Release workflow), tag-triggered release PR creation (prerelease/* tags no longer drive releases) and the Development Build prerelease on pushes to main (the GitHub release is now created directly by publish_release). Publish, checks, stale and upgrade_sandwich workflows are untouched. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GjdKcoaoecn6TKWmnUZzji
…omation-rollout-to-all-sdk-repos Add one-click release workflows (DEV-1181)
…(DEV-1192) Bump sandwich to 7.10.1. LoadScreen(contextKey, onSuccess, onError) returns a typed NoCodesScreen (id, contextKey, defaultSelectedProductId, typed defaultVariables); requests are correlated by contextKey carried in both success and failure payloads. Custom builder actions surface via the new optional NoCodesCustomActionDelegate interface (kept separate from NoCodesDelegate for source compatibility on Unity 2018.3, which has no default interface methods). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KQEJXqfVNxqoUcKXhSPhWn
…code (DEV-1192) An unparseable success payload now fails the correlated callbacks instead of leaving them pending forever, and unsupported platforms (noop wrapper) fail synchronously instead of never responding. Map the ClientError code both natives emit since sandwich 7.10.1. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KQEJXqfVNxqoUcKXhSPhWn
The pending-callback fix only covered the null-return path; an anomalous payload throwing inside the NoCodesScreen constructor still escaped into the UnitySendMessage handler and leaked the correlated callbacks. Return null on mapping failure so the existing parse-error path fails them. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BVh5VVyvxemyHT2oRSyXWK
…loadscreen-defaultvariables-and-custom-action Bridge No-Codes loadScreen, defaultVariables and custom action event (DEV-1192)
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.
Release PR
What's New
LoadScreen(contextKey, onSuccess, onError)method — loads a screen without presenting it and returns a typedNoCodesScreenwith id, context key, default selected product id and typedDefaultVariablesNoCodesCustomActionDelegateinterface — implement it alongside yourNoCodesDelegateto receive custom actions configured in the builder