chore: bump bulletin-deploy to 0.7.14#150
Merged
UtkarshBhardwaj007 merged 1 commit intomainfrom May 9, 2026
Merged
Conversation
Internal hardening of the chunked-storage path against WS-halt allocation storms (issues #142/#216/#287): per-deploy retry-budget circuit breaker (5 events / 30s, tunable via BULLETIN_RETRY_BUDGET_{MAX,WINDOW_MS}), recovery batch-size drop (2->1 in flight after first reconnect), and a synchronous onStatusChanged(CLOSE|ERROR) hook that destroys the PAPI client before its activeBroadcasts.forEach loop can mutate-while-iterating into OOM. Public surface (deploy / DeployContent / DeployOptions / DeployResult) is unchanged.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
|
Dev build ready — try this branch: |
Contributor
E2E Test Pass · ❌ FAILTag:
Sentry traces: view spans for this run |
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
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.
Summary
bulletin-deployfrom0.7.13→0.7.14. Public surface (deploy,DeployContent,DeployOptions,DeployResult) is unchanged; verified via diff of upstreamsrc/index.ts.Retry budget exhausted: …if more than 5 recovery events land within 30s. Tunable viaBULLETIN_RETRY_BUDGET_MAX/BULLETIN_RETRY_BUDGET_WINDOW_MS.onStatusChanged(CLOSE|ERROR)hook that destroys the PAPI client before itsactiveBroadcasts.forEachloop can mutate-while-iterating into OOM.isConnectionErrorextended to matchChainHead disjointed(PAPI's chainHead-state-inconsistent shape after our destroy mid-subscription) so retries route throughdoReconnect.deploy.status="ok"set on the success path (we already geterror/killedfrom the 0.7.13 series).new Uint8Array(fs.readFileSync(...))double-wrap removed (perf only).@scure/base2.0.0 → 2.2.0.@polkadot-apps/*count remains 0.CLAUDE.mdinvariant for the explicitbulletin-deploypin updated to reflect 0.7.14.patch).Test plan
pnpm install— clean resolve, no peer-dep regressionspnpm exec tsc --noEmit— cleanpnpm test— 486/486 passgrep '@polkadot-apps/' pnpm-lock.yaml— 0 hits