/target
**/*.rs.bk
Cargo.lock
# ...but DO commit the native crate's lock: the `native` CI lane builds it as a
# verified artifact, so it must resolve the exact deps (pyo3 patch) it was
# verified against, not float on every CI run.
!native/Cargo.lock
# Same rationale for goldenembed: the `goldenembed` CI lane builds it (and links
# onnxruntime via `ort`), so pin the exact resolved deps it was verified against.
!goldenembed/Cargo.lock
# Same rationale for goldencheck-native: the publish-goldencheck-native workflow
# builds it as a verified wheel, so pin the exact resolved deps. (goldencheck-core
# is a pyo3-free library dep -- its lock stays ignored, like score-core/graph-core.)
!goldencheck-native/Cargo.lock
# Same rationale for score-wasm: build_wasm.sh produces a shipped .wasm artifact
# and wasm-bindgen-cli MUST match the exact wasm-bindgen crate version resolved
# here; a floating lock would silently produce broken JS glue at runtime.
!score-wasm/Cargo.lock
# Same rationale for goldenflow-wasm: same wasm-bindgen wrapper shape as
# score-wasm, also destined to ship a built .wasm artifact via a build script.
!goldenflow-wasm/Cargo.lock
# Same rationale for datafusion-udf: the python_goldenmatch CI lane builds this
# cdylib (datafusion 53 / arrow 58 / ort), so its deps must NOT float. Its lock
# was previously (mistakenly) ignored, which let a fresh resolve pull the broken
# brotli 8.0.3 (`StandardAlloc` no longer satisfies `Allocator<T>`); pinning the
# lock (brotli held at 8.0.2) keeps the verified resolve reproducible.
!datafusion-udf/Cargo.lock
*.so
*.dylib
*.dll
*.pdb
.env
__pycache__/
*.pyc
*.egg-info/
dist/
build/
