Translation file for tfa 8.x-1.3 module release not found

Not that I know of.. Other than tagging 8.x-1.4 and keeping my fingers crossed that it would suddenly work. And unfortunately, I don't even know anymore which project I should change this to ask for help there.. Before it would be "Drupal.org webmasters".

Ha, sorry, tobiasb just pointed out that there is a pretty huge teaser on https://localize.drupal.org/issues ("Project or release not listed?")

But keep your fingers crossed please ;-)

I’ve re-saved the 8.x-1.3 release, sometimes that kickstarts some of the D.O. backends into working.

If that doesn’t fix it I think this would probably fall under Drupal.org Infrastructure as they handle the backend communications.

I’m sure how long we’re suppose to wait for Localization to see new versions.

Note for infrastructure in case it’s relevant:
This was originally tagged as a security release and was untagged by the security team.

Thanks so much for the fast reactions, you're awesome!

I've cross-posted at https://www.drupal.org/project/localizedrupalorg/issues/3403826 🐛 TFA release 8.x-1.3 not listed on l.d.o Active

Quoting from https://localize.drupal.org/issues:

Project or release not listed?

If you maintain a drupal.org project (module, theme, distribution) and it does not show up here or has "No data available", that means you do not have a release of your project for either Drupal 7.x or 8.x (maybe your project is a sandbox project). Because your development code can change from minute to minute, we are only parsing released packages, so translators can focus on shipped software to translate. If you think you have a release out but it is not listed in at most a day, please submit an issue and fill in your project and release name.

@cmlara unfortunately the kick did not have any effect. Fingers crossed that someone reacts on the cross-post.

Was worth a shot.

Not really much we can do from out side anymore. Pushing a new release technically is not a fix, just a method to hide the fault so we are likely better off letting the localization team sort this out.

While your here though. I do want to mention 📌 Replace TFA with 2FA in all user strings Needs work in case you, as a translator, might have any feedback for it.

This still hasn't been fixed by the translation team, however there is very little we can do from our side.

We have released new versions since this issue was opened and they do appear in the translation database.

I'm going to calls this a Duplicate of the upstream issue and close it out.