Skip to content

fix: always write -latest.json even when no new deployments occur #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
boyuanx merged 1 commit into from
Mar 3, 2026
Merged

fix: always write -latest.json even when no new deployments occur #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions src/DeployHelper.sol
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -232,11 +232,16 @@ abstract contract DeployHelper is CreateXHelper {
return;
}

// Always persist the cumulative -latest.json when it has content.
// This ensures the file is created after interrupted runs where
// contracts exist on-chain but the JSON was never written to disk.
if (bytes(finalJsonLatest).length > 0) {
vm.writeJson(finalJsonLatest, jsonPathLatest);
}

// Only write the timestamped diff file for actual new deployments
if (_hasNewDeployments) {
vm.writeJson(finalJson, jsonPath);
if (bytes(finalJsonLatest).length > 0) {
vm.writeJson(finalJsonLatest, jsonPathLatest);
}
}
}

Expand Down