Version Packages (alpha)#179
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/prerelease/v2
branch
from
83672eb to
1514e33
Compare
github-actions
Bot
force-pushed
the
changeset-release/prerelease/v2
branch
from
1514e33 to
d816167
Compare
github-actions
Bot
force-pushed
the
changeset-release/prerelease/v2
branch
from
d816167 to
5e9ac2e
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 prerelease/v2, this PR will be updated.
prerelease/v2is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonprerelease/v2.Releases
@deroll/app@2.0.0-alpha.9
Patch Changes
2.0.0-alpha.7and2.0.0-alpha.8were published with unresolvedworkspace:*references to@deroll/cmioand@deroll/core, making them uninstallable. The release process now resolvesworkspace:andcatalog:protocols to concrete versions beforechangeset publish.@deroll/explorer@0.2.0-alpha.3
Minor Changes
enabled+status(OK/FAILED/DIVERGED/CORRUPTED) instead ofstate, carry a withdrawal config, foreclosure lifecycle fields and three new sync checkpoints; epochs gainstaged_at_blockand the CLAIM_STAGED/CLAIM_FORECLOSED statuses; inputs gain REPORTS_LIMIT_EXCEEDED. Adds a Withdrawals tab (list + per-account detail) for post-foreclosure withdrawal events, and Withdrawal config / Foreclosure sections on the application overview#file-…anchor), a per-file Raw URL, or thegist:id/file.tsshorthandPatch Changes
@deroll/decoderimport external for decoders registered as hand-pasted esm.sh URLs — without the flag esm.sh rewrote the kit import to an absolute npm URL the import map cannot remap, silently loading@deroll/decoder@0.1.0(npm'slatest) instead of the pinned kit, so v3 portal deposits failed to decode@deroll/decoderimport map at the kit's home in this monorepo, pinned to a commit — esm.sh intermittently fails to resolve floating branch refs, which broke every kit-using decodercartesi_getChainId(e.g. running without an EVM reader) — the connection dot now also probescartesi_getNodeVersionand treats any RPC-level reply as connected, omitting the chain id when unavailable@deroll/docs@1.0.0-alpha.7
Patch Changes
@deroll/examples@2.0.0-alpha.11
Patch Changes