GitHub advisory for tj-actions/changed-files, published on the 15th. Our tabletop team removed the affected CI action Monday. The trainee has closed Saturday's incident as "fixed in next build". What was that earlier run allowed to see while everyone was out eating chips?
We removed the affected CI action on Monday. Who is dealing with what Saturday's run could already see?
CI/CDRespuesta a incidentesSeguridad de la cadena de suministroMock job R17 was in the relevant interval and its recorded configuration permitted a test publishing credential. The sample record lacks enough detail to say whether anybody saw that value. We treated it as potentially exposed and contacted its owner through the established private route.
Yes. Independent owner revoked the exercise credential and issued a replacement to the intended job. Their test service accepted the replacement and rejected the retired one. We reviewed the old run through the authorised incident channel; no real historical logs or secret material in this game.