Khem Raj escreveu (sexta, 26/01/2024 à(s) 17:58):
> On Fri, Jan 26, 2024 at 8:24 AM Jose Quaresma
> wrote:
> >
> >
> >
> > Alexander Kanavin escreveu (sexta, 26/01/2024
> à(s) 16:10):
> >>
> >> Hello Jose,
> >>
> >> there was a 1.21 update earlier, what happened to that?
> >
> >
> > Hi Alex,
>
On Fri, Jan 26, 2024 at 8:24 AM Jose Quaresma wrote:
>
>
>
> Alexander Kanavin escreveu (sexta, 26/01/2024 à(s)
> 16:10):
>>
>> Hello Jose,
>>
>> there was a 1.21 update earlier, what happened to that?
>
>
> Hi Alex,
>
> I know and I've already done some work on this but unfortunately there are
Alexander Kanavin escreveu (sexta, 26/01/2024 à(s)
16:10):
> Hello Jose,
>
> there was a 1.21 update earlier, what happened to that?
>
Hi Alex,
I know and I've already done some work on this but unfortunately there are
runtime problems.
Hello Jose,
there was a 1.21 update earlier, what happened to that?
Alex
On Fri, 26 Jan 2024 at 17:06, Jose Quaresma wrote:
>
> Upgrade to latest 1.20.x release [1]:
>
> $ git log --oneline go1.20.12..go1.20.13
> a95136a88c (tag: go1.20.13) [release-branch.go1.20] go1.20.13
> 5c38c04957
Upgrade to latest 1.20.x release [1]:
$ git log --oneline go1.20.12..go1.20.13
a95136a88c (tag: go1.20.13) [release-branch.go1.20] go1.20.13
5c38c04957 [release-branch.go1.20] crypto/tls: align FIPS-only mode with
BoringSSL policy
9e4abed39b [release-branch.go1.20] crypto/internal/boring:
