Update lencode and safe-bigmath - #3107
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🛡️ AI Review — Skeptic (security review)VERDICT: SAFE VERY HIGH scrutiny (account under 90 days and one public repository), mitigated by repository write access; no Gittensor association found; branch chore/update-lencode → release-449. Static analysis covered the complete dependency-only diff. Both direct updates are immutably resolved by a Git revision or registry checksum; no review trust-boundary, runtime logic, origin, or CI workflow changes are present. FindingsNo findings. ConclusionNo malicious behavior or concrete security vulnerability was found in the dependency update. 🔍 AI Review — Auditor (domain review)VERDICT: 👍 UNKNOWN Gittensor association; newer account with substantial repository activity and write access. This remains a coherent, lockfile-complete dependency update:
FindingsNo findings. ConclusionThe dependency and lockfile changes are consistent, narrowly scoped, and present no concrete domain-correctness issue. CI should provide the unavailable formatting and compilation validation. |
|
🔄 AI review updated — Skeptic: SAFE |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
|
🔄 AI review updated — Skeptic: SAFE Auditor: 👍 |
Motivation
Update
safe-bigmathto its 0.4.2 revision and align the workspace'slencodedependency with the version required by that release.Changes
safe-bigmathGit revision from 0.4.1 to 0.4.2.lencodeandlencode-macrosfrom 0.1.6 to 1.2.1.Cargo.lockto capture the resulting transitive dependency changes.Behavioral impact
No Subtensor source code or public API is changed directly. The updated libraries are used by the swap pallet's high-precision arithmetic implementation, so existing swap tests and workspace CI should validate compatibility.
Migration and spec version
No storage migration is required. The PR targets
release-449, which has no corresponding live-network spec-version check, so this dependency-only change does not include a spec-version bump.Validation
The lockfile is consistent with the manifest changes, and
git diff --checkpasses. Full compilation and tests are delegated to CI; local Cargo validation was unavailable because the existing toolchain/cache directories were read-only.