feat: Adds opt-in only wasm target to vapor CI workflows#54
feat: Adds opt-in only wasm target to vapor CI workflows#54gwynne merged 5 commits intovapor:mainfrom
Conversation
0xTim
left a comment
There was a problem hiding this comment.
@scottmarchant can you enable the WASM build in the self test workflow so it's run as part of CI here?
Yep, working on that. Turns out there is a hidden gotcha limitation, can't have more than 10 inputs on the workflow input. I'll probably split it up or something. |
…ms, rather than individual toggles. This provides workaround for the maximum 10 input limit GitHub imposes on workflow_dispatch.
|
@0xTim I added wasm to the self test workflow, but doing so caused us to exceed the 10 input maximum on workflow_dispatch. To work around that, I refactored the workflow_dispatch to provide a dropdown choice for platforms instead. This is a little less flexible than before. You can select If there is a better way to address that issue, please let me know. That limitation only applies to the |

Change summary
Added swift wasm as an opt-in only CI target, to help prevent future breakages to swift wasm builds in vapor repositories.
New usage of the wasm build will be added to vapor repositories on a case-by-case basis, once the required wasm support is in place.
Notes
This PR is part of a larger effort by PassiveLogic to add wasm support to many popular repositories.
Testing done
Verified this new workflow functions correctly using a temporary PR that enables the new wasm build.
See https://github.com/PassiveLogic/sql-kit/actions/runs/15886122859/job/44798410586?pr=1