I can understand the language ambiguity, but note that there are two posts there. The initial post, focused only on the Github token breach, as well as the updated post expanding the scope.
The line quoted is referring to the scope in the update, not the original Github token breach which we noted originally did in fact mean repos had potentially been compromised.
Hey, there! I'm a product manager working on Jenkins X. We are at work right now on multi-cluster support, actually.
I'd love to talk to you about it in more detail and get you involved in the experiments around it - feel free to email me at [email protected] if you'd like to be involved or chat more about it.
I can understand the language ambiguity, but note that there are two posts there. The initial post, focused only on the Github token breach, as well as the updated post expanding the scope.
The line quoted is referring to the scope in the update, not the original Github token breach which we noted originally did in fact mean repos had potentially been compromised.