[RELEASE] develop → staging: vite chunk-cycle hotfix + dispute-bond UI + dependabot bumps#3205
Merged
Merged
Conversation
Bumps [@storybook/blocks](https://github.com/storybookjs/storybook/tree/HEAD/code/lib/blocks) from 8.6.12 to 8.6.14. - [Release notes](https://github.com/storybookjs/storybook/releases) - [Changelog](https://github.com/storybookjs/storybook/blob/v8.6.14/CHANGELOG.md) - [Commits](https://github.com/storybookjs/storybook/commits/v8.6.14/code/lib/blocks) --- updated-dependencies: - dependency-name: "@storybook/blocks" dependency-version: 8.6.14 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [@mysten/dapp-kit](https://github.com/MystenLabs/ts-sdks) from 0.19.11 to 1.0.6. - [Release notes](https://github.com/MystenLabs/ts-sdks/releases) - [Commits](https://github.com/MystenLabs/ts-sdks/commits/@mysten/deepbook-v3@1.0.6) --- updated-dependencies: - dependency-name: "@mysten/dapp-kit" dependency-version: 1.0.6 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…storybook/blocks-8.6.14 chore: bump @storybook/blocks from 8.6.12 to 8.6.14
…mysten/dapp-kit-1.0.6 chore: bump @mysten/dapp-kit from 0.19.11 to 1.0.6
cloud.tangle.tools was hard-broken (`TypeError: Cannot read properties of undefined (reading 'forwardRef')`, only the purple background shell visible) because the post-#3199/#3203 rebuild produced this chunk graph: react-*.js ──imports `_getDefaultExportFromCjs` from──▶ radix-*.js radix-*.js ──top-level Qu.reduce → Yu → `i.forwardRef`──▶ react-*.js Rollup hoists the CJS-interop helper into whichever chunk happens to own the right modules under the current content-hash layout. On this build it landed in radix, so react imported it back, forming a cycle that crashed at module init: radix's top-level Primitive.* reduce ran before react's named exports were initialised. Fix: co-locate react/react-dom with @radix-ui in a single chunk. @radix-ui already depends on react, so they must evaluate in this order anyway — putting them together makes the chunk graph acyclic. Verified locally on both apps: - tangle-cloud: react chunk has zero cross-chunk imports → leaf - tangle-dapp: react chunk imports only from `noble` (also a leaf) - Both apps mount cleanly under preview with no pageerror events
…nk-cycle fix(vite): merge @radix-ui into react chunk to break load-order cycle (prod hotfix)
Closes the TODO carried since v0.14.0 — `cancelSlash` stopped auto-refunding the disputer's bond, so disputers now need a pull-pattern claim flow. Adds: - `usePendingDisputeBondRefund(account)` — reads `pendingDisputeBondRefund(address)` on TANGLE and surfaces the outstanding refund balance for the connected disputer. - `useClaimDisputeBondTx()` — wraps `claimDisputeBond()` via the shared `useContractWrite` plumbing; invalidates the refund balance query on success so the UI updates without a page refresh. - Operator-manage page: emerald refund-available card that appears when there's a non-zero pending refund (or after a failed claim attempt). Surfaces the amount, a Claim refund button, and a Dismiss affordance when an error needs to be cleared. Wires through `libs/tangle-shared-ui/src/data/graphql/index.ts` re-exports so downstream consumers can use the hooks directly.
feat(tangle-cloud): wire dispute-bond claim flow (v0.15.0)
drewstone
changed the title
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.
Production hotfix cascade — Stage 1/2.
Promotes the following to staging on the way to master:
Master release PR will follow once this merges.
Follow-up to discuss (post-incident)
The current 3-branch model (develop → staging → master) has been a recurring source of merge artifacts — recent history shows multiple cleanup commits like `a725b00ad fix: remove staging-only web3-api-provider files`, `cff4de8c5 fix: restore api-config.ts to develop version (staging merge artifact)`, `81bac419c fix: restore ChainListCard to develop version`. Worth retiring the staging branch and pointing the staging-deploy Netlify environment at `develop` directly. Will open a separate proposal.