-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Open
Labels
Cmd-forge-vbCommand: forge verify-bytecodeCommand: forge verify-bytecodeT-bugType: bugType: bugfirst issueA good way to start contributingA good way to start contributing
Description
Component
Forge
Have you ensured that all of these are up to date?
- Foundry
- Foundryup
What version of Foundry are you on?
forge --version forge Version: 1.3.5-stable Commit SHA: 9979a41 Build Timestamp: 2025-09-09T04:49:44.505104000Z (1757393384) Build Profile: maxperf
What version of Foundryup are you on?
foundryup: 1.0.1
What command(s) is the bug in?
forge verify-bytecode
Operating System
macOS (Apple Silicon)
Describe the bug
Typical workflow for using forge verify-bytecode is to check out a commit at a given production tag (e.g., v1.3.0) and run forge verify-bytecode against that code.
A few times I have run into an issue where I'm confused why it's not matching the bytecode, only to realize I needed to do a forge clean. Having forge verify-bytecode auto-compile changed files similar to how forge test works would solve this.
zerosnacks
Metadata
Metadata
Assignees
Labels
Cmd-forge-vbCommand: forge verify-bytecodeCommand: forge verify-bytecodeT-bugType: bugType: bugfirst issueA good way to start contributingA good way to start contributing
Type
Projects
Status
Backlog