Opera Android updater yields two current releases

[caugner]

What type of issue is this?

Infrastructure issue

What is the issue?

See: https://github.com/mdn/browser-compat-data/actions/runs/25652711327/job/75294105229#step:5:16

The update browser releases script added a new current release without marking the previously current release as retired.

What behavior were you expecting?

The update browser releases script should have marked the previously current release as retired.

What version(s) of BCD is the issue present in?

• The current BCD release
• The current version of the main branch

Do you have anything more you want to share?

No response

[caugner]

The explanation is that the Opera RSS feed returns the user of the latest comment in a thread as dc:creator, but we are filtering on a specific user (associated with Opera). So as soon as someone else comments in the release thread, we skip that thread:

• "Opera for Android 98" (88625, May 5) — dc:creator: cska133 ← filtered out, it's a reply
• "Opera for Android 97" (88511, Apr 16) — dc:creator: abitkulova ← matches

With the fix in #29657, we handle this case. There is a remaining risk that we "miss" a release if someone comments before we run the updater, or if the update PR isn't merged immediately. If that happens, we might be able use the JSON API of the forum (apparently NodeBB-based) to get the original author of the release posts.