You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8ed2f4c
Browse filesBrowse the repository at this point in the historyBrowse files
fix(persistence): keep the teardown when the failure-path confinement check cannot run
The confinement re-check inside the catch block of safeWriteJson re-resolved
the publish target and the scope root outside the try, so a realpath failure
there bypassed the backup rollback and the staged cleanup and replaced the
failure the caller was told about. The two resolutions now sit inside the
guard, an escape is undone and reported as before, and a scope that cannot
be canonicalized is reported and lets the rollback and cleanup below run.
The row that fails without it:
src/utils/__tests__/safeWriteJson.test.ts, restores the committed file and
drops the staged file when the failure-path confinement check cannot run.
Requested-by: #2357
0 commit comments