[ci] release #73
Merged
[ci] release #73
Conversation
This file contains hidden or 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]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Deploying loop-decoder with
|
| Latest commit: |
70b73da
|
| Status: | ⚡️ Build in progress... |
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
497f993 to
70b73da
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.
Releases
@3loop/transaction-decoder@0.11.0
Minor Changes
d169992: Refactor stores to call
setwhen the data is not found in strategies. This introduces new types for store values, tobe able to differentiate between a missing value, and one that was never requested.
Success- The data is found successfully in the storeNotFound- The data is found in the store, but is missing the valueMetaEmpty- The contract metadata is not found in the storeThis change requires the users of the library to persist the NotFound state. Having the NotFound state allows us
to skip the strategy lookup, which is one of the most expensive operations when decoding transactions.
We suggest to keep a timestamp for the NotFound state, and invalidate it after a certain period of time. This will
ensure that the strategy lookup is not skipped indefinitely. Separately, users can upload their own data to the store.
Patch Changes
@3loop/transaction-interpreter@0.2.1
Patch Changes
web@0.1.14
Patch Changes