A failing checkout hook now skips that repo and cleans up instead of ending the session.
What's wrong with this entry?
If a checkout hook fails for a repository that has no push target configured, the runner now skips that source and carries on, cleaning up the partial checkout, rather than aborting the whole session.
- If the partial checkout directory cannot be deleted, or its name collides with a prepared checkout only by letter case on a case-insensitive filesystem, it is left in place and you are warned that its contents may still be visible. Removal is retried when the session ends.
- Hook failures now carry the hook's exit code.
CheckoutHookFailedError
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Self-hosted runners report when warm-up finished
Both mention self hosted runner
-
v2.1.236
Self-hosted runner releases a session only after its work finishes
Both mention self hosted runner
-
v2.1.236
Runner waits for sessions to be released before shutting down
Both mention self hosted runner