Skip to content

build: build against the SDK fork instead of a pinned base plus patch - #2

Merged
gavdevs merged 2 commits into
mainfrom
migrate-sdk-main
Nov 2, 2026
Merged

gavdevs merged 2 commits into
mainfrom
migrate-sdk-main

Conversation

@gavdevs

@gavdevs gavdevs commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • Build Borealis against gavdevs/light-sdk main (b1a2d85), which now carries the package-install, Play sign-in, uninstall, pinned-dependency, and exact-version allowlist work in-tree.
  • Retire the patch/apply-extension CI steps and the extension provenance in the release packaging; the patch file and sdk-extension/ stay in the repo as a documented fallback.
  • Fix BorealisSyncJob for the LightJobResult.Success signature change from the upstream audio rewrite.

Verification

  • Fresh clone at the exact CI layout, no patch applied: 86 unit tests pass, assembleDebug succeeds.
  • Both CI pre-check suites (:sdk:client:testDebugUnitTest --tests 'com.thelightphone.sdk.auth.*', plugin validation tests) pass against the pinned SDK.
  • Debug dependency provenance TSV contains all three pinned deps (gplayapi 3.6.4, tink 1.20.0, protobuf 4.34.1) plus the SDK project modules.

Notes

  • The release pipeline itself (release-package.py) has been updated for the new provenance shape but not run end-to-end; it only runs on version tags.

The upstream audio rewrite gave LightJobResult.Success two required fields and
the summary no longer travelled via output data alone. The call site carries
both fields explicitly.
The SDK fork now carries the package-install, Play sign-in, uninstall, pinned
dependency, and exact-version allowlist work that used to be applied here as a
patch plus a checked-in extension. All of it is now the SDK's own code, so the
build needs no local patch step and no extension installer, and the release
provenance fetches the full SDK tree rather than a base-plus-delta.

As a side effect this moves Borealis off 52fbc5a and onto the fork's main.
@gavdevs
gavdevs merged commit a030967 into main Nov 2, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant