Skip to content

Nightly + stable release #73

Nightly + stable release

Nightly + stable release #73

Manually triggered August 9, 2026 15:35
Status Success
Total duration 17m 43s
Artifacts

nightly-release.yml

on: workflow_dispatch
Nightly — resolve version
Nightly — resolve version
Stable — changelog + tag
23s
Stable — changelog + tag
Nightly — build  /  fmt + clippy
Nightly — build / fmt + clippy
Matrix: Nightly — native packages / deb
Waiting for pending jobs
Nightly — native packages  /  build .msi (windows-x64)
Nightly — native packages / build .msi (windows-x64)
Nightly — native packages  /  build .pkg (macos-universal)
Nightly — native packages / build .pkg (macos-universal)
Stable — verify release assets  /  Verify v0.104.0 carries the native install packages
17m 15s
Stable — verify release assets / Verify v0.104.0 carries the native install packages
Matrix: Nightly — build / build-linux
Waiting for pending jobs
Matrix: Nightly — build / build
Waiting for pending jobs
Nightly — native packages  /  Attach packages to the release
Nightly — native packages / Attach packages to the release
Matrix: Nightly — build / verify-linux-floor
Waiting for pending jobs
Nightly — publish + prune
0s
Nightly — publish + prune
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
Stable — changelog + tag
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Stable — changelog + tag
dig-constants 0.10.0 is published; the newest copy here is 0.9.0. Adopt it only if it stays on this repo's chia line — a dig-constants release that jumps chia-protocol/chia-wallet-sdk links a second chia_protocol into the graph and will not compile against the vendored fork.
Stable — changelog + tag
cargo cannot unify semver-incompatible 0.x minors, so each copy is linked into a different subsystem and they can disagree about a value that is meant to be canonical by construction. This does not block the release: the holders above pin their copies in PUBLISHED metadata that dig-node cannot edit, and collapsing them takes a cross-repo publish cascade (dig_ecosystem#2072). Every copy at or above 0.4.0 agrees on the chain identity, which is why this is a warning and the floor above is not.
Stable — changelog + tag
0.9.0 <- dig-clvm, dig-node-core, dig-node-service
Stable — changelog + tag
0.8.0 <- dig-download
Stable — changelog + tag
0.5.1 <- dig-nat, digstore-chain
Stable — changelog + tag
0.4.0 <- dig-gossip
Stable — changelog + tag
dig-constants resolves to 4 DIFFERENT versions in one binary: 0.4.0 0.5.1 0.8.0 0.9.0