Skip to content

Fix release withserialized files #235

@cbrzn

Description

@cbrzn

Serialized WASM modules are being created for the embedded wraps; being the reason that it is faster to initialize the WASM Package, hence, improving the dev exp.

At first, we were committing the files but we got this error: https://github.com/polywrap/rust-client/actions/runs/6036435666/job/16379292848#step:4:2154. Meaning that, when running cargo publish it is modifying somehow the serialized modules; hence, throwing this error.

Then, a PR to ignore the serialized files was merged #231 and now we're having this error: https://github.com/polywrap/rust-client/actions/runs/6037828180/job/16383805428#step:4:2603. Meaning that, when running cargo publish the serialized files where created but they haven't been committed

We can:
a) Check why the serialized file is modified in the cargo publish process, this would fix situation #1
b) Keep ignoring the files and allow the crates to be pushed with non-committed files, this would fix situation #2

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions