Skip to content
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.

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

Fix: broadcast create transaction #6

Merged
merged 3 commits into from
Dec 16, 2024

Conversation

0xteddybear
Copy link
Contributor

foundry pushed a breaking change adding the --broadcast flag to forge create, making a dry run the default

logging should make it more evident if something like this happens in the future, but I'm open to removing it

.cwd(cwd)
.json()
core.info(`Deployed spell ${contractName} to address ${result.deployedTo}`)
core.debug(`Deploy result: ${result}`)
Copy link
Contributor

@krzkaczor krzkaczor Dec 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are u sure that result doesn't leak Tenderly's admin RPC URL for example? I assume that the debug log output is public for public repos... I would probably remove this line.

Logging concrete data with core.info is fine IMO.

Copy link
Contributor Author

@0xteddybear 0xteddybear Dec 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't checked that specifically, but also remember that the warning messages that made me realize of the newly added --broadcast flag weren't present in the json output
Also given foundry is likely to push breaking changes like the one motivating this PR, even if secrets aren't being leaked now, they could be leaked with future foundry updates.

Good catch, thanks! implemented it in e75276a

@krzkaczor krzkaczor merged commit 815e38f into marsfoundation:main Dec 16, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants