I have my own composite actions used as follows:
- uses: myci-actions/add-deb-repo@master
# ...
i.e. it refers to latest master branch.
Then, if I update the action, the master points to updated action.
But the runner seems still using older (cached?) version of the action.
In the build log it prints:
☁ git clone 'https://github.com/myci-actions/add-deb-repo' # ref=master
but the action used is still old one.
Looks like the runner checks that ref=master did not change since last run and does not update the cached action?
Though, re-running the job makes the problem go away. So, looks like the problem happens only the first time after the action was updated. And it happens per runner, i.e. if the same job is run for the first time on another runner, it will give the error again.
I have my own composite actions used as follows:
i.e. it refers to latest
masterbranch.Then, if I update the action, the
masterpoints to updated action.But the runner seems still using older (cached?) version of the action.
In the build log it prints:
but the action used is still old one.
Looks like the runner checks that
ref=masterdid not change since last run and does not update the cached action?Though, re-running the job makes the problem go away. So, looks like the problem happens only the first time after the action was updated. And it happens per runner, i.e. if the same job is run for the first time on another runner, it will give the error again.