fix(apm-audit): --no-drift to skip cache-replay (v5.1.2 follow-up)#14
Merged
danielmeppiel merged 1 commit intomainfrom May 8, 2026
Merged
fix(apm-audit): --no-drift to skip cache-replay (v5.1.2 follow-up)#14danielmeppiel merged 1 commit intomainfrom
danielmeppiel merged 1 commit intomainfrom
Conversation
setup-only avoids overwriting tampered files but leaves the install cache empty. The 'drift' check (cache-replay) then aborts on every audit: drift: drift replay aborted: cache miss for ... --no-drift skips that replay. content-integrity still hash-checks every deployed file against the lockfile (no cache needed) so tamper is still caught. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Setup-only mode (PR #13) leaves install cache empty. Drift check then aborts on cache miss. --no-drift skips replay; content-integrity still catches file tamper via lockfile hashes.