Skip to content

feat: prettify bytes ourselves - #11062

Open
nmattia wants to merge 6 commits into
masterfrom
nm-pretty-bytes
Open

feat: prettify bytes ourselves#11062
nmattia wants to merge 6 commits into
masterfrom
nm-pretty-bytes

Conversation

@nmattia

@nmattia nmattia commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

This drops the pretty-bytes dependency (last update 9 years ago). Instead we now make the bytes pretty ourselves.

This cleans up our dependency graph and closes the following (low severity) vulnerability: GHSA-g98v-hv3f-hcfr

@github-actions github-actions Bot added the feat label Aug 7, 2026
This drops the [pretty-bytes](https://crates.io/crates/pretty-bytes)
dependency (last update 9 years ago). Instead we now make the bytes
pretty ourselves.

This cleans up our dependency graph and closes the following (low
severity) vulnerability: GHSA-g98v-hv3f-hcfr
@nmattia
nmattia marked this pull request as ready for review August 7, 2026 10:46
@nmattia
nmattia requested review from a team as code owners August 7, 2026 10:46
@nmattia
nmattia enabled auto-merge August 7, 2026 10:46
github-actions[bot]

This comment was marked as spam.

@zeropath-ai

zeropath-ai Bot commented Aug 7, 2026

Copy link
Copy Markdown

No security or compliance issues detected. Reviewed everything up to dd90b34.

Security Overview
Detected Code Changes
Change Type Relevant files
Refactor ► Cargo.Bazel.json.lock
    Update checksums and remove deprecated atty/pretty-bytes entries
► Cargo.Bazel.toml.lock
    Remove deprecated atty/pretty-bytes entries and adjust hermit-abi dependencies
► Cargo.lock
    Remove deprecated atty/pretty-bytes entries and adjust hermit-abi dependencies
► bazel/rust.MODULE.bazel
    Remove deprecated pretty-bytes crate specification from module
► rs/sns/integration_tests/BUILD.bazel
    Remove pretty-bytes from BASE_DEPENDENCIES
► rs/sns/integration_tests/Cargo.toml
    Remove pretty-bytes dependency

claude and others added 4 commits August 7, 2026 13:48
Resolves merge conflict in Cargo.Bazel.json.lock by taking origin/master's
version wholesale (git checkout --theirs); CI's Lock Generate autofix job
will regenerate the correct content. No other conflicts. Verified the
PR's own changes (removal of pretty-bytes/atty deps, hand-rolled
pretty_bytes() in sns_governance_mem_test_canister.rs) survived intact.
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.

3 participants