Repository navigation
Preserve historical validation across Git read deadlines - #91
Merged
Merged
Conversation
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
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.
Historical retention and nonmaterial-amendment checks could treat an exhausted Git read deadline as a missing or unsupported original record. Browser validation then cached a false error even though CLI validation and the committed history were valid.
Propagate timed-out history reads to the existing retry path, preserving rejection of genuinely unsupported original adoption. Regression coverage exercises committed patch upgrades, same-cache and worker-snapshot retries, HTTP recovery, amendment source history, and historical access-review recovery.
Validation: two independent combined code/security reviews; focused regressions passed; full Node 24 validation passed (59 engine files, scaffolder, script tests, model and README checks), clean consumer setup, package dry runs, dependency audit, and fresh committed-workspace browser checks. Coordinated patch release: 0.20.7.
CI: https://github.com/Alignbase/filegrc/actions/runs/40231589451 (all five required checks passed).
Release commit:
8f3b20190654e5a37f5ac89be09b0b0352dabfd9; merged tree matches reviewed head3a7891b74d3e9ed12a1fd8ee0d16c6715428d2d6.Release: https://github.com/Alignbase/filegrc/releases/tag/v0.20.7
Publish verification: https://github.com/Alignbase/filegrc/actions/runs/40232421573 (passed, including installed README setup).
Both npm package versions and latest tags verified at 0.20.7. Scaffolder SLSA provenance resolves to the exact release commit; engine signed provenance is present in the Sigstore transparency log at index 3468731129 with the same release commit and tag.