Skip to content

chore: remove wasm lib files after generating ts bindings#1822

Merged
fewerner merged 1 commit intomainfrom
felix/chore/remove-wasm-libfiles
Feb 4, 2026
Merged

chore: remove wasm lib files after generating ts bindings#1822
fewerner merged 1 commit intomainfrom
felix/chore/remove-wasm-libfiles

Conversation

@fewerner
Copy link
Contributor

@fewerner fewerner commented Feb 4, 2026

With this PR we remove lib files after ts bindings generation.
Keeping these files causes issues when running jvm-test or ios-test after ts bindings generation. It's cheap to regenerate them so we just remove them after bindings generation.

We also change the execution order for make local to run ts since kotlin and swift use the same lib files.

What's new in this PR


PR Submission Checklist for internal contributors
  • The PR Title
    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

@fewerner fewerner requested a review from a team February 4, 2026 08:56
@fewerner fewerner force-pushed the felix/chore/remove-wasm-libfiles branch 4 times, most recently from 4fa93e7 to 30e7ff7 Compare February 4, 2026 10:28
Keeping these files causes issues when running jvm-test or ios-test
after ts bindings generation. It's cheap to regenerate them so we just
remove them after bindings generation.

We also change the execution order for `make local` to run ts since
kotlin and swift use the same lib files.
@fewerner fewerner force-pushed the felix/chore/remove-wasm-libfiles branch from 30e7ff7 to 54f6768 Compare February 4, 2026 11:11
@fewerner fewerner merged commit 54f6768 into main Feb 4, 2026
30 checks passed
@fewerner fewerner deleted the felix/chore/remove-wasm-libfiles branch February 4, 2026 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants