Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages (next) #1685

Merged
merged 1 commit into from
Oct 6, 2023
Merged

Version Packages (next) #1685

merged 1 commit into from
Oct 6, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 3, 2023

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@latticexyz/[email protected]

Major Changes

  • 3d0b3ed: Removes .mudbackup file handling and --backup, --restore, and --force options from mud set-version command.

    To revert to a previous MUD version, use git diff to find the version that you changed from and want to revert to and run pnpm mud set-version <prior-version> again.

Patch Changes

@latticexyz/[email protected]

Minor Changes

  • d075f82: - Moves contract write logic out of createContract into its own writeContract method so that it can be used outside of the contract instance, and for consistency with viem.

    • Deprecates createContract in favor of getContract for consistency with viem.
    • Reworks createNonceManager's BroadcastChannel setup and moves out the notion of a "nonce manager ID" to getNonceManagerId so we can create an internal cache with getNonceManager for use in writeContract.

    If you were using the createNonceManager before, you'll just need to rename publicClient argument to client:

      const publicClient = createPublicClient({ ... });
    - const nonceManager = createNonceManager({ publicClient, ... });
    + const nonceManager = createNonceManager({ client: publicClient, ... });

Patch Changes

@latticexyz/[email protected]

Minor Changes

  • 4385c5a: Allow the gas-report CLI to parse logs via stdin, so it can be used with custom test commands (e.g. mud test).

    Usage:

    # replace `forge test -vvv` with the custom test command
    GAS_REPORTER_ENABLED=true forge test -vvv | pnpm gas-report --stdin

Patch Changes

  • ba17bda: Pass through stdin logs in gas-report. Since the script piping in logs to gas-report can be long-running, it is useful to see its logs to know if it's stalling.

@latticexyz/[email protected]

Minor Changes

  • 9352648: Since #1564 the World can no longer call itself via an external call.
    This made the developer experience of calling other systems via root systems worse, since calls from root systems are executed from the context of the World.
    The recommended approach is to use delegatecall to the system if in the context of a root system, and an external call via the World if in the context of a non-root system.
    To bring back the developer experience of calling systems from other sysyems without caring about the context in which the call is executed, we added the SystemSwitch util.

    - // Instead of calling the system via an external call to world...
    - uint256 value = IBaseWorld(_world()).callMySystem();
    
    + // ...you can now use the `SystemSwitch` util.
    + // This works independent of whether used in a root system or non-root system.
    + uint256 value = abi.decode(SystemSwitch.call(abi.encodeCall(IBaseWorld.callMySystem, ()), (uint256));

    Note that if you already know your system is always executed as non-root system, you can continue to use the approach of calling other systems via the IBaseWorld(world).

Patch Changes

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

Patch Changes

[email protected]

Patch Changes

  • f99e889: Bump viem to 1.14.0 and abitype to 0.9.8

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

Patch Changes

  • f99e889: Bump viem to 1.14.0 and abitype to 0.9.8

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

Patch Changes

  • f99e889: Bump viem to 1.14.0 and abitype to 0.9.8

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

Patch Changes

@latticexyz/[email protected]

@latticexyz/[email protected]

@latticexyz/[email protected]

[email protected]

[email protected]

@latticexyz/[email protected]

@latticexyz/[email protected]

@latticexyz/[email protected]

@latticexyz/[email protected]

@latticexyz/[email protected]

@latticexyz/[email protected]

@latticexyz/[email protected]

@github-actions github-actions bot requested review from alvrs, dk1a and holic as code owners October 3, 2023 08:45
@vercel
Copy link

vercel bot commented Oct 3, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
mud-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 4, 2023 10:10am

@github-actions github-actions bot force-pushed the changeset-release/main branch from 759e945 to fa38347 Compare October 3, 2023 08:52
@github-actions github-actions bot force-pushed the changeset-release/main branch from fa38347 to bd3bcdb Compare October 3, 2023 10:54
@github-actions github-actions bot force-pushed the changeset-release/main branch from bd3bcdb to 389dca1 Compare October 3, 2023 11:01
@github-actions github-actions bot force-pushed the changeset-release/main branch from 389dca1 to f470a21 Compare October 3, 2023 14:25
@github-actions github-actions bot force-pushed the changeset-release/main branch from f470a21 to 4095b9f Compare October 3, 2023 14:54
@github-actions github-actions bot force-pushed the changeset-release/main branch from 4095b9f to c4892a1 Compare October 3, 2023 16:27
@github-actions github-actions bot force-pushed the changeset-release/main branch from c4892a1 to 668a08f Compare October 3, 2023 17:06
@github-actions github-actions bot force-pushed the changeset-release/main branch from 668a08f to b77b2da Compare October 3, 2023 17:10
@github-actions github-actions bot force-pushed the changeset-release/main branch from b77b2da to 84c211b Compare October 3, 2023 17:51
@github-actions github-actions bot force-pushed the changeset-release/main branch from 84c211b to e806f76 Compare October 3, 2023 17:58
@github-actions github-actions bot force-pushed the changeset-release/main branch from e806f76 to 66b3f8f Compare October 3, 2023 18:25
@github-actions github-actions bot force-pushed the changeset-release/main branch from 66b3f8f to e21c380 Compare October 4, 2023 10:09
@alvrs alvrs merged commit 9ff4f45 into main Oct 6, 2023
@alvrs alvrs deleted the changeset-release/main branch October 6, 2023 12:07
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.

1 participant