Skip to content

Bump chia-bls from 0.38.2 to 0.46.0 #539

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

Bump chia-bls from 0.38.2 to 0.46.0 #539

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
62 changes: 55 additions & 7 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ python-source = "python"

[dependencies]
binascii = "0.1.4"
chia-bls = "0.38.2"
chia-bls = "0.46.0"

@cursor cursor Bot Jul 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Stale wasm lockfile after bump

Medium Severity

chia-bls is bumped to 0.46.0 in the root manifests, but wasm/Cargo.lock still resolves chialisp against chia-bls 0.38.2. The wasm package path-depends on this crate, so locked or freshly checked-out wasm builds can fail or keep an inconsistent BLS resolution until that lockfile is regenerated.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit eea8970. Configure here.

clvmr = { version = "0.17.5", features = ["pre-eval"] }
do-notation = "0.1.3"
hashlink = "0.11.0"
Expand Down
Loading