Kevin Ingersoll

0.7.2 includes [a nice change that we might want](https://github.com/pvolok/mprocs/pull/151)

audit CallWithSignature module

1

https://github.com/latticexyz/mud/tree/main/packages/world-module-callwithsignature We now install CallWithSignature module by default during deploy as its needed for EntryKit, so we should get this audited.

Our threejs template is super outdated and using old patterns. It'd be great to start a new one with latest three.js/react-three-fiber best practices and ideally building off of the base...

Our phaser template is super outdated and using old patterns. It'd be great to start a new one with latest Phaser best practices and ideally building off of the base...

wip store sync cleanup

1

TODO - [ ] dedupe SyncProgress - [ ] migrate SyncProgress to something that isn't storage adapter specific? - [ ] use `createSyncAdapter` inside `syncToRecs` instead of duplicating logic

we can now release a snapshot using a branch with slashes, but can't run it with "test published packages" due to it failing on `mud@some/tag` https://github.com/latticexyz/mud/blob/227db4d37db5dd26607f77e805d91701ba2e38db/.github/workflows/test-published-packages.yml#L35 npm things `@some/tag` means...

update templates CI workflow to use built templates

1

the templates workflow currently uses templates from their source with linked/workspace deps: https://github.com/latticexyz/mud/blob/main/.github/workflows/templates.yml ideally it should use the template output from `pnpm create mud` to mimic what users will see...

for easier deployment with vercel: https://github.com/latticexyz/mud-workshop/blob/f71d2f9878da29b32c7488bf23bf18ff71e516f0/package.json#L7-L9

sometimes we miss that CI fails after a merge and would be good to send a notification to discord when this happens