There was a bug that was happening when building multiple qa releases when main remained the same. The reason for this is that the cache key was based around the github.sha. This is fine when it is triggered by a normal sha, but comments triggering a run actually are run from the sha of main. This means that the build directory is cached for ANY qa build going into main and it will restore from that point until main is a new sha. An example of this occurred in add-ons.
To fix this, we are detecting the actual sha that we're using from the release that we built.
There was a bug that was happening when building multiple qa releases when
mainremained the same. The reason for this is that the cache key was based around thegithub.sha. This is fine when it is triggered by a normal sha, but comments triggering a run actually are run from theshaofmain. This means that the build directory is cached for ANY qa build going intomainand it will restore from that point untilmainis a new sha. An example of this occurred in add-ons.To fix this, we are detecting the actual sha that we're using from the release that we built.