chore: update protobuf files and wasm client

[pablojhl]

No description provided.

[github-actions]

Coverage Report for ./client-vms

Status	Category	Percentage	Covered / Total
🔵	Lines	88.25%	2051 / 2324
🔵	Statements	88.25%	2051 / 2324
🔵	Functions	80.93%	208 / 257
🔵	Branches	93.76%	361 / 385

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
client-vms/src/gen-proto/nillion/membership/v1/service_pb.ts	100%	100%	100%	100%
client-vms/src/gen-proto/nillion/membership/v1/version_pb.ts	100%	100%	100%	100%
client-vms/src/gen-proto/nillion/payments/v1/balance_pb.ts	100%	100%	100%	100%
client-vms/src/gen-proto/nillion/payments/v1/config_pb.ts	100%	100%	100%	100%
client-vms/src/gen-proto/nillion/payments/v1/quote_pb.ts	100%	100%	100%	100%
client-vms/src/gen-proto/nillion/payments/v1/receipt_pb.ts	100%	100%	100%	100%
client-vms/src/gen-proto/nillion/payments/v1/service_pb.ts	100%	100%	100%	100%
client-vms/src/gen-proto/nillion/preprocessing/v1/element_pb.ts	100%	100%	100%	100%
client-vms/src/gen-proto/nillion/preprocessing/v1/generate_pb.ts	0%	0%	0%	0%	1-172
client-vms/src/vm/operation/store-values.ts	93.57%	96.42%	87.5%	93.57%	92-97, 181-183

Generated in workflow #66 for commit 834908c by the Vitest Coverage Report Action

[tim-hm]

Hi @pablojhl, a few bits from me:

• When bumping the wasm artefact I've been isolating that change to a single commit like here and including build details in commit-sha.txt. This really just a workaround until the nilvm repo is open source but its helpful if/when we need to bisect problems.
• I've re-run the pipeline and ran it locally, but with this commit tests are now failing.

Lemme know if you need assistance with any of that!

[pablojhl]

• When bumping the wasm artefact I've been isolating that change to a single commit like here and including build details in commit-sha.txt. This really just a workaround until the nilvm repo is open source but its helpful if/when we need to bisect problems.
• I've re-run the pipeline and ran it locally, but with this commit tests are now failing.

My fault, I should create it as a draft until the needed changes are merged into the nilvm repo. I tested the commit locally running the nillion-devnet from the branch that contains the changes are pending to merge and the tests are working fine. Anyway, I'm going to update the PR to draft until they are merged.

Sorry for the inconvenience.

[tim-hm]

Ahh that makes more sense!

[tim-hm]

Hi ya, looks good! Some suggestions from me:

• Its not immediately clear that chore: remove particles is also a wasm package bump ... might be worth making that distinction but not a show stopper by any stretch
• Given the updated protobuf files (and assuming you're looking to release and updated npm package?), I would also bump the client-vm PATCH

[pablojhl]

Hi ya, looks good! Some suggestions from me:

• Its not immediately clear that chore: remove particles is also a wasm package bump ... might be worth making that distinction but not a show stopper by any stretch
• Given the updated protobuf files (and assuming you're looking to release and updated npm package?), I would also bump the client-vm PATCH

Regarding the first point, do you mean adding a comment in the PR?