Skip to content

chore(release): v0.262.1 -- dig-rewards-coin 0.11 - #635

Merged
MichaelTaylor3d merged 2 commits into
mainfrom
release/v0.262.1
Oct 3, 2026
Merged

MichaelTaylor3d merged 2 commits into
mainfrom
release/v0.262.1

Conversation

@MichaelTaylor3d

Copy link
Copy Markdown
Contributor

Cuts v0.262.1 to main: the dig-node#634 dependency bump plus the workspace version bump and CHANGELOG section.

What is in this cut

Branch is origin/main (64321c63, tag v0.262.0) + a cherry-pick of c3d6f96f (#634, merged to develop). develop at c3d6f96f differs from main only by #634 and the workspace version line, so the cut sweeps no other work.

Commit Content
c3d6f96f (#634) build(deps): bump dig-rewards-coin to 0.11, raise dig-* floors (§2.4b)
release commit version 0.262.0 -> 0.262.1 + CHANGELOG section (Cargo.toml, Cargo.lock, CHANGELOG.md only)

SemVer

Patch (0.262.0 -> 0.262.1): dependency bump only, no wire/RPC/API change. CommitmentEpochStarted is only returned by withdraw_committed_incentives, which dig-node never calls (guard test chain_port.rs:570-580).

Tickets

Closes DIG-Network/dig_ecosystem#3450

Release mechanics

Merging this PR does not cut the tag; the stable release is dispatched separately.

🤖 Generated with Claude Code

MichaelTaylor3d and others added 2 commits October 3, 2026 07:31
* build(deps): bump dig-rewards-coin to 0.11 (dig_ecosystem#3450)

Also raises the floors of the caret-compatible dig-* deps to their latest patch.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* build(deps): refresh Cargo.lock for dig-rewards-coin 0.11 (dig_ecosystem#3450)

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#3450

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@MichaelTaylor3d

Copy link
Copy Markdown
Contributor Author

PASS (loop-security, dig-node#635)

Head SHA audited: db330c46dcddcc9cee9275ce8b2c831f5356c150 (base main 64321c6 / v0.262.0)

  • (a) Lock: package set identical to origin/main, 800 entries, same name/version/source/checksum tuples except dig-rewards-coin 0.10.0 -> 0.11.0 (checksum present, registry source). Sources are only crates.io plus the two pre-existing rev-pinned git deps (dig-gossip, digstore). 784 registry packages, 784 checksums. The windows-sys / socket2 edges re-select versions already in the lock; they add no package. Release commit's own lock change is the dig-node-service version line only.
  • (b) dig-rewards-coin 0.10.0 -> 0.11.0 (registry source diffed): Cargo.toml differs only by version, same deps, build = false, no build.rs. src changes are clawback.rs (new epoch-started refusal in withdraw_committed_incentives, which gains an observed: &ChainObservation parameter), error.rs (new CommitmentEpochStarted), state.rs (read predicate refactored to the shared fn, same boundary). The delta adds a refusal and no new spend, network or custody path. dig-node never references withdraw_committed_incentives (only the guard test at chain_port.rs:570-580 and comments), so the signature change cannot break or expose it. reader_error_to_port_error keeps a wildcard arm (chain_port.rs:310-317).
  • (c) Release commit db330c4 touches only Cargo.toml (workspace version), Cargo.lock (dig-node-service version), CHANGELOG.md (new 0.262.1 section). Whole PR vs main: those plus crates/dig-node-service/Cargo.toml (the build(deps): bump dig-rewards-coin to 0.11 (dig_ecosystem#3450) #634 content: dig-rewards-coin 0.11 and dig-* floors raised to already-resolved versions). No source .rs file changes.
  • Secrets / authz / input / amplification / persisted state: no code path changed. No finding. Defence-in-depth: none worth a ticket.

Not covered: build/test execution (CI's job); the upstream crate's tests; transitive-crate source for the windows-sys/socket2 re-selection (already-present versions, no new code enters the tree).

@MichaelTaylor3d MichaelTaylor3d left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PASS at head db330c46dcddcc9cee9275ce8b2c831f5356c150 (loop-reviewer, read-only gate; same-identity so posted as a comment review).

Checked:

  • Diff vs main = #634 content (crates/dig-node-service/Cargo.toml + Cargo.lock) + release commit. Cargo.toml/Cargo.lock/crate diff is line-identical to c3d6f96^..c3d6f96 except the one dig-node-service lock version line 0.262.0 -> 0.262.1. Two commits only (8061397, db330c4); no swept-in develop work.
  • Release commit touches only Cargo.toml (workspace version 0.262.1), Cargo.lock (dig-node-service 0.262.1), CHANGELOG.md.
  • Version consistency: Cargo.toml == lock == CHANGELOG heading ## [0.262.1] - 2026-10-03 == title v0.262.1. Tag v0.262.1 does not exist; v0.262.0 is latest.
  • Title 49 chars, chore(release): ... valid; "Lint commit messages" pass.
  • CHANGELOG section well-formed (Build / deps bullet, #634 ref), placed above 0.255.0 following the file's existing format.
  • Closes DIG-Network/dig_ecosystem#3450 present in PR body, plain text, outside any code span.
  • SemVer patch: dependency bump, no wire/RPC/API change.
  • Required checks pass: Check version increment, Lint commit messages, Release-script tests, Rustfmt, Clippy, Test + coverage, Analyze (actions/js-ts/rust), CodeQL, build .deb amd64 and arm64, build .msi.
  • NOT yet terminal at time of verdict: build .pkg (macos-universal) pending. Orchestrator must confirm it green before merging.

Not run: local build/test (relied on CI); no inline threads (no defects). Threads open: 0.

@MichaelTaylor3d
MichaelTaylor3d merged commit c32ab77 into main Oct 3, 2026
15 checks passed
@MichaelTaylor3d
MichaelTaylor3d deleted the release/v0.262.1 branch October 3, 2026 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant