Add an internal cli argument to create template with path dependencies #212
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we use git dependencies and update the version number, we might reference a tag that does not exist, which leads to build failures. We used to work around this by creating a temporary tag for the new version and replace it with the proper tag later when we do the release. However, this violates the principle that git tags should be fixed and point to the exact commit that created the release.
In d69c87e, I tried to fix this by patching the git dependencies. Unfortunately it seems like this only works if the original dependency source exists, otherwise cargo will error out before applying the patches.
This PR tries to solve the problem by adding a new internal flag to our CLI (not shown in the help output). When this flag is given, the Rust template will use path dependencies instead of git dependencies. By using this flag in our CLI test, we don't depend on the planned release tag anymore.