Bump the native pin to include renderer resource forwarding - #48
Conversation
The cutover is only honest with it: registered images and fonts ride the renderer channel, so image- and font-carrying widgets (Noro) render identically device-less — verified live, including crash-replay.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe native SDK submodule now points to commit ChangesNative SDK update
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Greptile SummaryUpdates the native SDK submodule to revision The native revision alignment was verified before and after this update: the release audit passed, and its expected revision matches both the committed submodule reference and the checked-out native SDK revision. No defects were found. Confidence Score: 5/5
What T-Rex did
Reviews (1): Last reviewed commit: "Bump the native pin to weaver-main with ..." | Re-trigger Greptile |
Completes #47 — that PR merged at the commit before this pin bump landed on its branch, so master currently ships the shared-renderer cutover without SunkenInTime/native#26 (registered image + font forwarding). Until this merges, image- and font-carrying widgets (Noro) render device-less with blank art and system-font text.
One commit, cherry-picked from the #47 branch: submodule pin → native weaver-main
7368f7f5(the #26 merge), release-audit ratchet updated, audit passing locally. The receipts for what the pin carries are in #26: Noro art + Cozette verified live under the cutover, byte-identical across a host crash + replay, 43.1 MB device-less with zero arena regions.Summary by CodeRabbit