Skip to content

[chore] Refactor crates for publishing#937

Merged
Wizdave97 merged 4 commits into
mainfrom
publish-crates
May 30, 2026
Merged

[chore] Refactor crates for publishing#937
Wizdave97 merged 4 commits into
mainfrom
publish-crates

Conversation

@Wizdave97

Copy link
Copy Markdown
Member

No description provided.

Wizdave97 added 4 commits May 29, 2026 16:48
forge auto-installs forge-std into the foundry lib dirs during the
release build, and the untracked dirs trip cargo-release's dirty check.
The workspace-inherited version pinned the dev-dep to the unpublished
ismp 2512.1.0, deadlocking publication (ismp depends on serde-hex-utils
in turn). A path-only dev-dep is stripped from the published manifest,
so verification no longer requires ismp on the crates.io index.
ismp gained a hard dependency on ismp-abi in #916, which in turn depends
on beefy-verifier-primitives. Publishing ismp therefore requires both on
crates.io: drop the publish=false guard on beefy-verifier-primitives,
add license fields, and pin versions on the workspace dep declarations.
crypto-utils depended on the polytope-labs ssz-rs git fork (added in
#916), which cannot be published to crates.io. Move the ssz ByteVector
and BLS aggregation helpers — the only code touching ssz-rs — into a new
publish=false bls-utils crate, leaving crypto-utils with just the
signature-verification utilities so it can publish again. Repoint the
four consumers (sync-committee/bsc/pharos) at bls-utils.
@Wizdave97 Wizdave97 merged commit 3d1a197 into main May 30, 2026
13 checks passed
@Wizdave97 Wizdave97 deleted the publish-crates branch May 30, 2026 11:13
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.

2 participants