-
Notifications
You must be signed in to change notification settings - Fork 196
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) #2192
Merged
Merged
Version Packages (next) #2192
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 25, 2024 18:19
5359f4f
to
f747668
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 26, 2024 12:48
f747668
to
de9b619
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 26, 2024 18:05
de9b619
to
036f349
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 29, 2024 10:48
036f349
to
9008e6b
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 29, 2024 10:59
9008e6b
to
5bfbdc2
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 29, 2024 14:46
5bfbdc2
to
ef34ffa
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 30, 2024 14:14
ef34ffa
to
d40cc61
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 30, 2024 14:48
d40cc61
to
7517a63
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 30, 2024 16:59
7517a63
to
7e9405a
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
January 31, 2024 21:25
7e9405a
to
7814823
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 1, 2024 10:51
7814823
to
3101b21
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 1, 2024 16:22
3101b21
to
2a7aff8
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 1, 2024 19:48
2a7aff8
to
126d769
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 2, 2024 19:15
d2ba3c8
to
db870bb
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 5, 2024 11:10
db870bb
to
272919c
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 6, 2024 16:53
272919c
to
72ce45e
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 7, 2024 15:39
72ce45e
to
b19a78c
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 9, 2024 16:27
b19a78c
to
952888f
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 9, 2024 16:46
952888f
to
8c739b6
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 14, 2024 20:12
8c739b6
to
4f110e4
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 15, 2024 19:14
4f110e4
to
c664431
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 16, 2024 12:07
c664431
to
4420597
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 16, 2024 12:26
4420597
to
34a9a79
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 16, 2024 12:44
34a9a79
to
ede319a
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 20, 2024 15:56
ede319a
to
b439137
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
February 20, 2024 17:00
b439137
to
0cd7342
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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, runchangeset pre exit
onmain
.Releases
@latticexyz/[email protected]
Major Changes
@latticexyz/[email protected]
Major Changes
@latticexyz/[email protected]
Major Changes
@latticexyz/[email protected]
Major Changes
StoreCore
'sregisterCoreTables
method toregisterInternalTables
.Patch Changes
bytes32
table ID value rather than computing it in Solidity. This saves a bit of gas across all storage operations.ResourceIds
table before the table was registered.StoreCore.registerStoreHook
to useStoreHooks._push
for gas efficiency.StoreCore
to check that tables exist before registering store hooks.@latticexyz/[email protected]
Major Changes
aabd307: Bumped Solidity version to 0.8.24.
db7798b: Renamed
CoreModule
toInitModule
andCoreRegistrationSystem
toRegistrationSystem
.618dd0e:
WorldFactory
now expects a user-providedsalt
when callingdeployWorld(...)
(instead of the previous globally incrementing counter). This enables deterministic world addresses across different chains.When using
mud deploy
, you can provide abytes32
hex-encoded salt using the--salt
option, otherwise it defaults to a random hex value.Minor Changes
WorldFactory
now derives a salt based on number of worlds deployed bymsg.sender
, which should help with predictable world deployments across chains.Patch Changes
bytes32
table ID value rather than computing it in Solidity. This saves a bit of gas across all storage operations.WorldRegistrationSystem
to check that systems exist before registering system hooks.args
parameter toencodedArgs
to better reflect that it is ABI-encoded arguments.StoreCore
'sregisterCoreTables
method toregisterInternalTables
.@latticexyz/[email protected]
Major Changes
Minor Changes
SystemSwitch
to properly call non-root systems from root systems.Patch Changes
bytes32
table ID value rather than computing it in Solidity. This saves a bit of gas across all storage operations.args
parameter toencodedArgs
to better reflect that it is ABI-encoded arguments.@latticexyz/[email protected]
Minor Changes
aabd307: Bumped Solidity version to 0.8.24.
618dd0e:
WorldFactory
now expects a user-providedsalt
when callingdeployWorld(...)
(instead of the previous globally incrementing counter). This enables deterministic world addresses across different chains.When using
mud deploy
, you can provide abytes32
hex-encoded salt using the--salt
option, otherwise it defaults to a random hex value.Patch Changes
bytes32
table ID value rather than computing it in Solidity. This saves a bit of gas across all storage operations.InitModule
naming.@latticexyz/[email protected]
Minor Changes
Patch Changes
bytes32
table ID value rather than computing it in Solidity. This saves a bit of gas across all storage operations.contractToInterface
[email protected]
Minor Changes
Patch Changes
bytes32
table ID value rather than computing it in Solidity. This saves a bit of gas across all storage operations.@latticexyz/[email protected]
Minor Changes
createStoreSync
now waits for idle between each chunk of logs in a block to allow for downstream render cycles to trigger. This means that hydrating logs from an indexer will no longer block until hydration completes, but rather allow foronProgress
callbacks to trigger.Patch Changes
int32
,uint32
,int64
, anduint64
types to avoid overflows@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
@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]
[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]