new release tag request

[sky1ove]

Dear AF3 team,

I noticed that the last official release, 3.0.1, was made in January, and there have been many commits since then.
Our HPC team has informed us that they require an official tagged release to update the AF3. Would it be possible to create an updated official tagged release?
Thanks!

[Augustin-Zidek]

Hello,

I am planning to release v3.0.2 once #394 and #387 are fixed.

Note though that each time we tag an official release, we do a large scale accuracy test internally, which makes the release slightly more involved, so it might still take some time.

I will keep this issue open until v3.0.2 is released.

[sky1ove]

@Augustin-Zidek Any updates on this?

[Augustin-Zidek]

Sorry, still working on the B200 testing and investigating numerical differences to A100/H100.

[llambourne]

Hi, do you have any idea on the timeline for the new release? I need to use the --resolve_msa_overlaps=false flag implementation and our research computing is team is also waiting for the tagged release.
Thank you!

[loscati]

Hi! I know the technical challenges that a release bump requires and I see that the project is undergoing some rearrangement (e.g. documentation, uv etc.). However, I am jumping on the train and highlight that I would be interested too in another release to deploy the model, and its improvements over the past year, in a cluster.

Thanks in advance for all the work!

[Augustin-Zidek]

Hi, quick update. Firstly, sorry for the long delay. Secondly, we are waiting for the autotuning cache for flash attention and SwiGLU to land in Tokamax (which will give AlphaFold 3 a performance boost). Once those are in and a new Tokamax version is released, I will ship the next AlphaFold 3 version. I hope this will happen by the end of March 2026.