op-deployer always returns version 0.0.0-dev after build

[rich-hyun]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

Issue Description

I'm trying to use op-deployer to deploy the OP Stack on Sepolia as part of the tutorials.

I built op-deployer locally from the optimism monorepo, and everything compiles successfully.
However, when I run:

It always returns:

Logs

No response

Additional Information

Regardless of which Git tag or branch I checkout before building (e.g., op-deployer/v0.3.0),
the resulting binary always shows v0.0.0-dev.

This causes issues when trying to run apply, because some standard fields like SystemConfigOwner are not validated correctly.
The tool seems to assume the intent-type is "standard" and throws an error about a zero address —
even though my intent.json includes a valid systemConfig.owner.

I checked:

• My .deployer/intent.json is fully valid and parses correctly
• I'm using --private-key on apply
• I'm using the latest pnpm build from the monorepo

What I'm trying to understand

• Is there a way to build op-deployer such that it includes the proper version metadata (like v0.3.x)?
• Are certain runtime features (e.g., --intent-type custom) disabled because of this missing version tag?
• What is the recommended way to make sure I'm not running an old or incomplete version of op-deployer?

Thanks in advance for your help!

Feedback

No response

[opfocus]

Is there a way to build op-deployer such that it includes the proper version metadata (like v0.3.x)?
You may need to provide the flag value when building. (This should not help you determine if this is the version you need)
Are certain runtime features (e.g., --intent-type custom) disabled because of this missing version tag?、
You should prefer --intent-type custom. Normally we create an op-stack tesnet not to join the superchain
What is the recommended way to make sure I'm not running an old or incomplete version of op-deployer?
It's no problem to download the compiled version in release, or use version tag.