Skip to content

build: use the Common NU7 dependency stack - #1093

Closed
p0mvn wants to merge 6 commits into
mainfrom
build/nu7-common-dependencies
Closed

p0mvn wants to merge 6 commits into
mainfrom
build/nu7-common-dependencies

Conversation

@p0mvn

@p0mvn p0mvn commented Sep 21, 2026 •

Copy link
Copy Markdown
Collaborator

Pins Zakura's Common dependencies to the immutable NU7 revision from zakura-core/common#474, replacing the remaining crates.io address, protocol, and transparent packages with their Zakura forks.

Zakura now uses the finalized NU7 branch ID 0x77190AD8 and converts Common's unconditional NU7 network-upgrade variant without an unstable cfg. The full workspace resolves one coherent Common type family.

Validation:

  • cargo check --workspace --locked
  • cargo fmt --all -- --check
  • git diff --check

Stack dependency:

  • This draft intentionally consumes unpublished 1.3.0-alpha.1 Common crates from the immutable fix(network): credit replenishment budget on failed dials #474 Git revision.
  • The crates.io publish graph check will remain blocked until the Common stack is merged and those prerelease crates are published; this PR must not publish Zakura crates before then.

Additional validation:

  • cargo test -p zakura-chain --locked
  • cargo deny --workspace --all-features check bans licenses sources --allow banned
  • cargo deny --workspace --all-features check advisories --allow banned
  • cargo vet check --store-path ./qa/supply-chain/
  • ./scripts/changelog.py check

@p0mvn
p0mvn force-pushed the build/nu7-common-dependencies branch from b497ca2 to 9ed46b8 Compare September 23, 2026 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants