Use fetch-depth: 0 so setuptools_scm picks up tags in CI

[kjaymiller]

Summary

• Adds fetch-depth: 0 to all three actions/checkout steps in .github/workflows/test.yml.
• Without it, the shallow CI clone has no tags, setuptools_scm falls back to 0.0.dev…, and uv re-resolution fails on dependabot PRs that touch pyproject.toml without updating uv.lock (see Bump the production group across 1 directory with 3 updates #1164 for a live example).
• Full diagnosis in CI checkouts are shallow; setuptools_scm reports junk version and breaks resolution on dependabot PRs #1169.

Fixes #1169

Test plan

• All test-against-python-matrix jobs pass on this PR.
• After merge, comment @dependabot rebase on Bump the production group across 1 directory with 3 updates #1164 and confirm its matrix turns green.

🤖 Generated with Claude Code

[kjaymiller]

As with all issues when it comes to workflows we can't test all that effectively until it's merged

[brass75]

I hope this does what you think it does because I have no idea.

[kjaymiller]

hmmm maybe we try dlemstra/Magick.NET#1528 (comment)

[kjaymiller]

I hope this does what you think it does because I have no idea.

Great challenge on this. I'm glad we have AI Attestation to make us reconsider.. the link above was found by me (not ai)

[brass75]

hmmm maybe we try dlemstra/Magick.NET#1528 (comment)

Based on this I think all we would need is fetch-tags: true and not the depth change.

[kjaymiller]

Set up two test branches to verify whether fetch-depth: 0 is needed or if fetch-tags: true (shallow + tag refs) would suffice. Both have a rich downgrade to force uv to re-resolve like a dependabot PR, plus workflow_dispatch so they can be triggered manually.

• TEST (do not merge): fetch-tags variant for #1170 #1171 — fetch-tags: true variant
• TEST (do not merge): fetch-depth 0 variant for #1170 #1172 — fetch-depth: 0 variant (matches this PR)

Trigger:

gh workflow run "PyTest" --ref issue-1169-test-fetch-tags
gh workflow run "PyTest" --ref issue-1169-test-depth-0

If #1171 passes, fetch-tags: true is enough and this PR can be slimmed to use that instead. If #1171 fails on the cli extra error from #1169, fetch-depth: 0 is the right call.

Both branches are labeled DO NOT MERGE.

[brass75]

I think the fetch-tags is sufficient. Those test failures are from some weird dependency issue regarding the CLI. We should remove that dependency.

[kjaymiller]

Results in: fetch-depth: 0 is required.

Variant	Run	gen-coverage-badge	matrix (3.10–3.13)	latest-os (win/mac)
fetch-tags: true (#1171)	26263272755	❌	❌	❌
fetch-depth: 0 (#1172)	26263280788	✅	✅	✅

The fetch-tags: true jobs failed with the exact #1169 error — tag refs alone aren't enough because the tag's target commit isn't in the shallow history, so setuptools_scm falls back to 0.0.dev0 and render-engine-cli==2025.11.1 → render-engine>=2025.11.1a1 becomes unsatisfiable:

Because render-engine-cli==2025.11.1 depends on your project and render-engine[cli] depends on render-engine-cli==2025.11.1, we can conclude that render-engine[cli] depends on itself at an incompatible version.

This PR's fetch-depth: 0 is the right call. The test PRs (#1171, #1172) can be closed.