TL;DR: On Terragrunt 1.1.0-1.1.3, a `?depth=1` on a `git::` source breaks the clone: CAS lifts `ref` out of the URL but leaves `depth` in, so git sees a repository literally named `...vpc.git?depth=1`. Delete the `depth` parameter (it does nothing on CAS clones) or upgrade to 1.1.4+.

```text
Error: invalid repository name: .../vpc.git?depth=1
```

(git rejecting the URL Terragrunt handed it, with `?depth=1` glued to the repo name)

## Steps

1. Inspect the `source`: look for `?depth=` in the URL, e.g. `git::https://github.com/org/vpc.git?depth=1&ref=v5.21.0`.
   Expected: you find the parameter.
2. Delete the `depth` parameter: `git::https://github.com/org/vpc.git?ref=v5.21.0`.
   Expected: the URL is a clean repo URL plus `ref`.
3. If you need a specific clone depth, set `--cas-clone-depth` (default 1, -1 for full history); a `depth` on the source URL is never applied to a CAS clone.
   Expected: depth behaves as intended.
4. Or upgrade to Terragrunt 1.1.4+, which strips `depth` before invoking git.
   Expected: old sources work unmodified.

## When this applies

- Terragrunt 1.1.0-1.1.3, git source with `?depth=` (with or without `ref`).
- The error names your URL with `?depth=` attached to `.git`.

## When it doesn't apply

- 1.1.4+: `depth` is stripped automatically.
- Auth failures on the same URL: that's credentials, not the depth parameter.

## Tool versions

Terragrunt v1.1.0-v1.1.3 broken; fixed in v1.1.4.

## Why it happens

v1.1.0 made CAS the default path for git sources. CAS parses `ref` out of the URL to pin the clone, but the `depth` query parameter wasn't stripped, so the raw URL (still carrying `?depth=1`) was handed to git as the repository address.

## Edge cases

- A `depth` with NO `ref` fails the same way.
- This doesn't look like a version problem (the error names your URL), which is why it survived four releases before the changelog called it out.