chore: commit Cargo.lock - #180
Merged
Merged
Conversation
Track the workspace lockfile, per current Cargo guidance (recommended for libraries as well as binaries since 1.73): a fresh clone or CI run then builds and tests the exact dependency set the commit was made with, and dependency bumps become visible diffs. It never affects downstream Rust users, who resolve from their own lockfile. It also lands the file in the PyPI sdist — MANIFEST.in already lists it, but the release workflow builds the sdist from a clean checkout where the ignored file did not exist — which is what the conda-forge reviewer asked for on conda-forge/staged-recipes#33466 so the feedstock can build with `--locked`. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017VHexyxYasfatXebfxtphw
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017VHexyxYasfatXebfxtphw
ssmichael1
force-pushed
the
chore/commit-cargo-lock
branch
from
September 12, 2026 17:01
0359b01 to
bc41c42
Compare
…0204), drop yanked num-bigint 0.4.7 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017VHexyxYasfatXebfxtphw
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Track the workspace
Cargo.lockand drop it from.gitignore, per current Cargo guidance (recommended for libraries as well as binaries since 1.73). A fresh clone or CI run then builds and tests the exact dependency set the commit was made with, and dependency bumps become visible diffs. It never affects downstream Rust users, who resolve from their own lockfile.It also puts the lockfile into the PyPI sdist:
MANIFEST.inalready lists it, but the release workflow builds the sdist from a clean checkout where the ignored file never existed (the 0.21.2 sdist has none). That is what the conda-forge reviewer asked for on conda-forge/staged-recipes#33466 so the feedstock can build withcargo-manifest-args = ["--locked"].Goes in ahead of the 0.22.0 release (#179), which will be rebased on top so its lockfile entry for
satkitreads 0.22.0.🤖 Generated with Claude Code
https://claude.ai/code/session_017VHexyxYasfatXebfxtphw