-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Last release failing due to sparse-checkout #1651
Comments
Adding detail from my closed bug (also ubuntu-20.04)
|
We are investigating. As a workaround, you can pin to v4.1.1
|
it looks like an outdated git version is being used:
|
Indeed... my bad - the step of my build that fails was the windows build which is older: But #1386 reports that sparse-checkout wasn't working here until 2.28 and there's a check in the code that the min version for sparse is 2.25 already checkout/src/git-command-manager.ts Line 610 in 8410ad0
|
https://github.com/actions/checkout/blob/main/src/git-source-provider.ts#L212 this is where it's failing in ours - if sparseCheckout isn't enabled it calls |
Rolled back from |
…as it broke everything actions/checkout#1651
Any reason why this was rolled back rather than a v4.1.3 to revert? Dependabot keeps bringing this in as a suggested update, and then I get an error in one of our tools that uses libgit2 (libgit2/libgit2#6044) which doesn't handle the Looks like the release is still here and still tagged, so whatever rollback was done isn't complete: https://github.com/actions/checkout/releases/tag/v4.1.2 |
Yes, if v4.1.2 is fatally flawed, than a new v4.1.3 release needs to be tagged, not slipping the v4 tag. |
Dependabot has tried to update to 4.1.3 which is pre-release and also has this issue funfair-tech/funfair-server-code-analysis#218 not sure why dependabot is trying to update to pre-release given the dependabot config, but given that it has its shown that this version fails too |
v4.1.4 should have the fix for this issue. As for dependabot, we reached out to that team about pre-release being included in their updates. On the actions/checkout side we will avoid use pre-release until that's been looked at. |
Job template:
The text was updated successfully, but these errors were encountered: