You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a mirror job for the x/crypto repo. It is now failing because commit 8b5121be2f68d8fc40bb06467003bdde1040a094 was applied on top of commit 5c40567. So the following commits have vanished from the head of release-branch.go1.13:
The release branches in x/crypto are really internal implementation details, they are not documented and not covered by our security policies, and I didn't know anyone actually used them.
I'm closing here as a dup, but feel free to subscribe to that other thread. I'm afraid the conclusion is "do not track those branches, only master is supposed to be tracked".
We have a mirror job for the x/crypto repo. It is now failing because commit 8b5121be2f68d8fc40bb06467003bdde1040a094 was applied on top of commit 5c40567. So the following commits have vanished from the head of release-branch.go1.13:
Was this expected?
The text was updated successfully, but these errors were encountered: