Invalid character `{` in package name about spin HOT 4 CLOSED

The issue stems most likely from a change to how cargo resolves git based dependencies. Cargo searches all of a git repository for Cargo.toml files and then resolves those projects even if they are not a part of a workspace. The template files get picked up as legitimate Cargo.toml manifests even though they're not.

I don't believe there's anyway to tell Cargo to ignore these files, so we might need to change how templating works to work around this Cargo issue.

from spin.

Maybe spin templates could be taught to strip a .tmpl suffix from input files?

from spin.

I found an allusion in https://blog.rust-lang.org/inside-rust/2024/03/26/this-development-cycle-in-cargo-1.78.html to package.include disabling git walking. Would that solve this, or would the downsides be unacceptable?

(I mean I'm okay with the .tmpl thing, just wondering.)

from spin.

I tried adding the templates to project.exclude, and it didn't work. This isn't surprising, as the package value is used for publishing crates, and I don't believe it's looked at when fetching a crate as a dependency.

from spin.