Skip to content

Commit b02250e

Browse files
committed
fix(registry): refresh recorded hashes after HYP-S006 edit
The hypatia-rules spec's source_hash is sha256(git ls-files -s hypatia-rules/), so editing hypatia-rules/registry-staleness.a2ml changes it. The registry had been regenerated BEFORE that edit was staged, leaving the recorded hash stale — which registry-verify.yml (--check) correctly caught. Regenerate after the edit is committed so the recorded hash matches; `--check` is green again.
1 parent fd5c5c8 commit b02250e

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

.machine_readable/REGISTRY.a2ml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -270,7 +270,7 @@ name = "Standards Hypatia Rules"
270270
stream = "integration"
271271
home = "hypatia-rules/"
272272
canonical_doc = "hypatia-rules/README.adoc"
273-
source_hash = "sha256:a63e95c5e43ced2ee13c58014175da156c71ab731f01449e3a61b3e2f33bbe52"
273+
source_hash = "sha256:797f42c3ac24cf610e1e0da0e9e019f3f0dce527d1f80857ab2adb85741159d3"
274274
route = "the dogfooding rules that scan THIS repo (incl. drift detection)"
275275

276276
[[spec]]

0 commit comments

Comments
 (0)