deps(deps): bump const-hex from 1.17.0 to 1.19.0#2501
Conversation
🧾 cargo-vet automated audit summary
CI did not commit anything. Review the patch locally and create the final signed commit yourself.
|
Bumps [const-hex](https://github.com/danipopes/const-hex) from 1.17.0 to 1.19.0. - [Commits](DaniPopes/const-hex@v1.17.0...v1.19.0) --- updated-dependencies: - dependency-name: const-hex dependency-version: 1.19.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
1e8109e to
7c459bd
Compare
🧾 cargo-vet automated audit summary
CI did not commit anything. Review the patch locally and create the final signed commit yourself.
|
There was a problem hiding this comment.
Dependency-only bump (const-hex 1.17.0 → 1.19.0) in both runtime and build deps, with matching lockfile update.
I don’t see a concrete blocking issue in this PR itself:
- No application code paths changed.
- No migration/state/permission/payment logic touched.
- Lockfile checksum and version move are consistent.
Given upstream notes include parsing behavior change (accepting 0X prefix), the only practical risk is behavior broadening if your code intentionally rejected uppercase prefix inputs. That appears non-blocking from this diff, but worth keeping in mind for any strict input-validation assumptions.
LGTM for merge.
Bumps const-hex from 1.17.0 to 1.19.0.
Commits
5f2a3cbchore: Release const-hex version 1.19.09ec02cfchore: allow unused portable_simd8b0eb94feat: allow upper case prefix 0X (#49)1143588chore: Release const-hex version 1.18.16155cbdperf: branch only once in decode_maybe_check (#46)c326e35feat: add SIMD decode for wasm32 and portable-simd (#45)18736fechore: remove cfg!(miri) NEON skips on aarch64 (#44)271dda6perf: add NEON SIMD decode for aarch64 (#43)22291dcperf: single-pass AVX2 decode with validation (#41)eab3dafperf: optimize SIMD check and encode implementations (#39)