chore: bump bulletin-deploy to 0.6.9 (stable)#20
Merged
UtkarshBhardwaj007 merged 1 commit intomainfrom Apr 17, 2026
Merged
Conversation
Upstream 0.6.9 ships two changes since our 0.6.9-rc.6 pin:
* fix(dotns, #101) — Lite signers are now correctly rejected on NoStatus
labels to match the on-chain PopRules contract. Closes a gap where the
classifier would let a Lite user through only for register() to revert.
* feat(dotns, #102) — new public `DotNS.preflight(label)` + internal
wiring inside `deploy()` so any deploy destined to fail DotNS aborts
BEFORE the Bulletin upload starts ("zero Bulletin bytes paid"). Also
exports `simulateUserStatus` and `popStatusName` helpers.
Our integration surface (`deploy()`, `DotNS.connect/classifyName/checkOwnership/
disconnect`) is untouched; this is drop-in for us. 147/147 tests pass, tsc
clean, format clean.
README + CLAUDE.md updated to reflect that we're on 0.6.9 stable (and the
general "pin explicitly, don't trust `latest`" rule). Changeset is a patch.
Contributor
|
Dev build ready — try this branch: |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
Summary
bulletin-deployfrom0.6.9-rc.6→0.6.9(now released as stable).latest" rule.What's in 0.6.9 since our rc.6 pin
Two substantive upstream commits:
NoStatuslabels, matching the on-chainPopRulescontract. Previously a Lite user could pass the classifier only to have the subsequentregister()revert. Internal correctness fix.DotNS.preflight(label)method, and bulletin-deploy's owndeploy()now runs that preflight BEFORE opening the Bulletin WebSocket. Net effect: deploys doomed to fail DotNS registration (bad label, reserved base name, domain owned by someone else, unresolvable PoP gate) now abort with zero Bulletin bytes uploaded. Also exportssimulateUserStatusandpopStatusNamehelpers. Additive — no existing API changed.Full release notes: https://github.com/paritytech/bulletin-deploy/releases/tag/v0.6.9
Breaking changes audit
None for us. We verified the four public APIs we depend on are still present and typed the same way:
deploy(content, domainName, options)— ✓DotNS#connect(options)— ✓DotNS#classifyName(label)— ✓DotNS#checkOwnership(label, ownerAddress?)— ✓DotNS#disconnect()— ✓Our
DeployOptionsusage (rpc,signer,signerAddress,mnemonic,attributes) is a strict subset of what 0.6.9 accepts. We still don't passjsMerkle: true(known-broken, falls back to Kubo binary) — unchanged.Interplay with our own preflight
We already have our own
checkDomainAvailability()that runs at domain-input time in the TUI (and before build in headless mode). bulletin-deploy 0.6.9's internaldotns.preflight()runs later in the pipeline — after the account-mapping check, beforegetProvider(). These are complementary:No deduplication needed.
Test plan
pnpm install— clean install, lockfile updatedpnpm exec tsc --noEmit— cleanpnpm test— 17 files, 147 tests passpnpm format:check— cleandot deployagainst an existing owned domain → "Already owned by you — will update the existing deployment"dot deploywith a Reserved name → aborts at availability check; no Bulletin bytes