> To help ensure reliable access, we recommend updating workflows that use HTTPS Git operations to authenticate with a Git credential, such as a personal access token.
so it looks like anonymous access to Git repositories is being limited. That will be very disruptive to many people with build scripts etc. It's disappointing to see it rolled out without any announcement.
(I am seeing about half of Jenkins jobs fail with this error.)
> To help ensure reliable access, we recommend updating workflows that use HTTPS Git operations to authenticate with a Git credential, such as a personal access token.
so it looks like anonymous access to Git repositories is being limited. That will be very disruptive to many people with build scripts etc. It's disappointing to see it rolled out without any announcement.
(I am seeing about half of Jenkins jobs fail with this error.)