Skip to content

Conversation

@Sabourifar
Copy link
Contributor

Templates currently generate:
command = "cargo install -q worker-build@^0.7 && worker-build --release"

Modern versions of Cargo reject the incomplete version specifier @0.7, causing: error: invalid value '[email protected]' ... unexpected end of input while parsing minor version number

Change to unpinned install to use the latest compatible worker-build: command = "cargo install -q worker-build && worker-build --release"

This resolves Cargo syntax errors on fresh Windows (and other) projects without affecting existing functionality.

Templates currently generate:
command = "cargo install -q worker-build@^0.7 && worker-build --release"

Modern versions of Cargo reject the incomplete version specifier `@0.7`, causing:
error: invalid value '[email protected]' ... unexpected end of input while parsing minor version number

Change to unpinned install to use the latest compatible worker-build:
command = "cargo install -q worker-build && worker-build --release"

This resolves Cargo syntax errors on fresh Windows (and other) projects without affecting existing functionality.
@Sabourifar Sabourifar changed the title fix: remove invalid pinned version in build command fix(templates): remove invalid pinned version in generated wrangler.toml build command Dec 15, 2025
@guybedford
Copy link
Collaborator

I believe it is only cargo install [email protected] that doesn't work in Cargo and not cargo install worker-build@^0.7.

So perhaps you were hitting a case of cargo install [email protected] somewhere instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants