Repository navigation
chore(release): v0.262.2 -- remove never-emitted ChainPeakUnavailable - #637
Merged
Merged
Conversation
…system#3448) (#636) * refactor(rewards): remove never-emitted ChainPeakUnavailable Zero producers and zero consumers; the real adapter already refuses an absent peak via read_distributor (Other/Unavailable). Fix the chain_peak_height doc to name that refusal. Refs DIG-Network/dig_ecosystem#3448 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * test(rewards): pin absent-peak refusal at the chain port Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Refs DIG-Network/dig_ecosystem#3448 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
MichaelTaylor3d
commented
Oct 5, 2026
MichaelTaylor3d
left a comment
Contributor
Author
There was a problem hiding this comment.
PASS at e809735.
- Code hunks in port.rs, dispatch.rs, rewards_fixture.rs, rewards_chain_port_a3.rs are byte-identical (+/- lines) to #636.
- Cargo.toml workspace version 0.262.1 -> 0.262.2 only; Cargo.lock only the dig-node-service version line; CHANGELOG adds one [0.262.2] - 2026-10-05 section.
- Body has Closes DIG-Network/dig_ecosystem#3448 outside a code span.
- Note (non-gating): CHANGELOG top entry before this was 0.255.0, so the section sits above 0.255.0 (no 0.262.1 section exists).
- Not run: build/tests (scope was diff identity).
Contributor
Author
|
PASS (loop-security) -- head audited: Narrow scope: #637 adds nothing beyond #636.
No findings. Not covered: CI results, post-merge release workflow behaviour. |
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.
Release v0.262.2
Brings to
main:57c505ffrefactor(rewards): remove never-emitted ChainPeakUnavailable (refactor(rewards): remove never-emitted ChainPeakUnavailable (dig_ecosystem#3448) #636)The removed variant and its
REWARD_CHAIN_PEAK_UNAVAILABLEcode were never constructed (v0.262.1 included); no consumer exists org-wide, and dig-rpc-protocol SPEC §4.5 names no machine code. An absent chain peak still refuses as JSON-RPC-32032/data.codeCONTROL_ERROR. #636 passed loop-reviewer and loop-security at a9bf40f.Closes DIG-Network/dig_ecosystem#3448
🤖 Generated with Claude Code