WIP – ci: add FFI binding verification workflows #1539
No reviewers
Labels
No labels
DB & Storage
Deployment
Error Handling & Logging
Maintenance
Payment Backend
backport
backport v0.13.x
backport v0.14.x
backport v0.15.x
bindings
blocked
bug
cdk-sql
ci
cli
deps
documentation
duplicate
enhancement
good first issue
help wanted
invalid
keep-open
ldk-node-ui
migrations
mint
mutation-testing
needs rebase
needs review
new nut
nut change
question
ready
rust-version
rustfmt
stacked hold
stale
testing
wallet
weekly-report
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
cashubtc/cdk!1539
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "add-ffi-verification-workflows"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.switching to ready to trigger the CI
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.