Repository navigation
fix(⬆️): upgrade to Dawn 157.0.0 - #577
Merged
Merged
Conversation
Depend on react-native-webgpu-dawn 157.0.0, the Dawn react-native-skia builds for Skia chrome/m157 (Dawn ada567700e). The dawn label becomes chrome-m157, the check-dawn.ts pins move to the new commit (the device-destroy workaround has no upstream fix yet, the vendored ExternalTextureParams.h is unchanged), and the one new FeatureName, SharedBufferMemoryHostPointer, is mapped.
This was referenced Oct 18, 2026
…ty table The Skia release that depends on react-native-webgpu-dawn 157.0.0 shipped as 3.7.0, and this branch releases as 0.17.0.
3.7.0 depends on react-native-webgpu-dawn 157.0.0, the version this branch pins, so the example resolves a single Dawn again.
|
🎉 This PR is included in version 0.17.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
1 participant
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.
Moves Dawn to the build react-native-skia publishes for Skia
chrome/m157:react-native-webgpu-dawn157.0.0 (Dawnada567700e, 2026-10-10, 441 commits after the 154.3.0 one). Companion of wcandillon/react-native-skia#4268.packages/webgpu/package.jsonpinsreact-native-webgpu-dawn157.0.0; thedawnlabel becomeschrome-m157(react-native-skia 3.0.x compares it, and 3.0.x cannot pair with this Dawn).scripts/check-dawn.ts: the two entries move to the new commit. The device-destroy-before-surface-release workaround stays (no upstream fix in this Dawn: nothing touched the Vulkan swapchain teardown on the way), and the vendoredExternalTextureParams.his byte-identical to the file at the new commit.GPUFeatures.h: maps the onewgpu::FeatureNamethis Dawn adds,SharedBufferMemoryHostPointer(shared-buffer-memory-host-pointer).No other source change: Dawn's C and C++ headers only gained identifiers since 154.3.0, and the example app builds for the iOS simulator (74 files of the pod recompiled, zero errors) and for Android arm64 (
libwebgpu_dawn.sofrom the package) against 157.0.0.Merge order
The example installs react-native-skia 3.0.8, whose podspec refuses this pairing, so its native build was red until a react-native-skia release depended on 157.0.0. Order: react-native-skia#4268 merged (it resolves its own example's Dawn to 157.0.0 and shipped 3.7.0), then bump
apps/examplehere to react-native-skia 3.7.0 and merge this as 0.17.0 (main carries a feat since 0.16.1), then react-native-skia bumps its example to 0.17.0 and drops its resolution. The compatibility rows in both repos assume those two version numbers.