WIP – ci: add FFI binding verification workflows#1539
Open
WIP – ci: add FFI binding verification workflows#1539
Conversation
Contributor
Author
|
switching to ready to trigger the CI |
callebtc
changed the title
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
3 participants
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.
Summary
This PR introduces 4 new GitHub Actions workflows to verify that changes in the core
cdkrepository do not break downstream FFI bindings.Workflows Added
ffi-python.yml: Generates Python bindings, installs them, and runs basic verification.ffi-kotlin.yml: Generates Kotlin bindings and verifies they compile.ffi-swift.yml: Generates Swift bindings and verifies the native package builds (on macOS).ffi-flutter.yml: Patches the Flutter Rust bridge to use the local CDK and verifies compilation.These workflows trigger on
pushandpull_requestto themainbranch.