Releases: spotify/target-determinator
Releases · spotify/target-determinator
v0.1.3
v0.1.2-debug-2
feat: log file mode and execute bit in hash-debug source_file lines
v0.1.2-debug-1
feat: add --hash-debug flag for per-target hash component logging When --hash-debug is passed, logs each target's hash inputs to stderr: - Source files: label, absolute path, and content hash - Rules: each rule input's label and hash, then the rule's final hash with its class, skylark env hash, and configuration This enables diagnosing non-deterministic hashes across CI agents by comparing the debug output from two runs on the same commit.
v0.1.2
v0.1.1
v0.1.0
What's Changed
- feat: add hash persistence, hash diffing, and bazel query backend by @honnix in #1
- fix: targets spuriously returned in cache case by @honnix in #3
- feat: add --rule-class-fingerprint flag by @honnix in #2
- fix: adapt walker_test to NewTargetHashCache 5-arg signature by @honnix in #4
New Contributors
Full Changelog: https://github.com/spotify/target-determinator/commits/v0.1.0
rule-class-fingerprint-1
feat: add --rule-class-fingerprint flag Introduce a repeatable --rule-class-fingerprint=<glob>[,<glob>...]:<file>[,<file>...] flag that mixes the SHA-256 of each file into the hash of any target whose rule class matches one of the globs. This closes the gap where --query-backend=query misses toolchain changes in sub-module files (e.g., tools/modules/rules_java.MODULE.bazel referenced via local_path_override) that do not surface via SkylarkEnvironmentHashCode. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>