-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Tags no longer fetch with Git v2.48.0 #2041
Comments
...looking at #2039 which hopefully fixes this: I presume the difference is that with 2.47, tags in the fetch depth are fetched by default, and with 2.48 they're not? |
Same here, but the issue only appears on the macos runners for us. There, also the install path changed between git versions: |
This appears to have been reported to the git@vger.kernel.org mailing list; see here for the entire thread. AFAICT, there does not appear to be any fix yet in 2.48.1 or on |
The Git version on Ubuntu runners was updated 2 hours ago causing all of our builds to fail
* Remove Demarteau and Romano * Add a note recommending reevaluating at the beginning of the year * Work around actions/checkout#2041
Thanks for reporting this. |
So an NAI has my immediate attention now that it's been announced that it will have the best possible future for the team as well as a new product that I believe will make the best possible market for this project as well as the future. Meeting this milestone |
It's not clear whether this is a problem with my expectations of the
fetch-tags
option, a bug incheckout
, or a bug in Git 2.48.0, but ancestral tags are no longer fetched as of Git 2.48.0 for shallow (but not too shallow) builds.Here, v0.6.0-dev is a nearish ancestor of the branch
backports/v0.5
being tested. With 2.47, tags within the fetch depth are fetched. With 2.48, only the ref is fetched: no tags.Full run output with git 2.47.1
Full run output with git 2.48.0
This issue first appeared when the GHA ubuntu-24.04 runner image updated from 20250105.1.0 to 20250113.1.0 .
The text was updated successfully, but these errors were encountered: