Repository navigation
Error: The configuration file "/home/runner/work/_temp/user-config-from-action.yml" is outside of the workspace #2145
Description
As of an hour ago, we have been receiving errors from the github/codeql-action/init@v3 action with no changes being made on our end.
This is happening during the "Load language configuration" step. Please see the below error:
Error: The configuration file "/home/runner/work/_temp/user-config-from-action.yml" is outside of the workspace
Since there were no changes on our end, I feel a bug or backwards-incompatible change may have been introduced in a recent commit. I am looking to see if there's anything obvious I can find.
Edit:
A fix has been proposed 🎉
#2147
Reacted by Grzegorz Eliszewski, Robbie Blaine, robertm34, navjotkaur, Mikita Butsko, Masaya Suzuki, Ben Griffiths and Yusuke Goto
Activity
p5 commentedon Feb 15, 2024
The individual commit appears to be 191f59f which introduced the error
p5 commentedon Feb 15, 2024
I believe we have identified the commit which introduced the error, and the logic which is causing it.
This code requires the configuration file to be inside the workspace directory before proceeding
https://github.com/github/codeql-action/blob/main/src/config-utils.ts#L886-L902
But this doesn't account for 191f59f moving the configuration file outside the workspace, into a
_tempdirectoryangelapwen commentedon Feb 15, 2024
Thank you for the notification: we've identified the error and have a fix up at #2147 As soon as it's in
main, we'll release again tov2andv3.angelapwen commentedon Feb 15, 2024
The fix is merged, and we're going through the release process for
v2andv3again. In the meantime, we've manually retaggedv2andv3to the version prior to the faulty release, so workflows using those tags should already no longer be seeing this issue.p5 commentedon Feb 15, 2024
Have confirmed our CodeQL workflows using
@v3are working again.Thank you!
Will close this issue as complete.
angelapwen commentedon Feb 15, 2024
Thank you also for identifying the commit with the error 😄 we were doing it at the same time internally and you were just as fast!