-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Opera Android updater yields two current releases #29649
Copy link
Copy link
Closed
Labels
bugConfirmed bugs in the repository (i.e. linter bugs), NOT browser implementation bugs.Confirmed bugs in the repository (i.e. linter bugs), NOT browser implementation bugs.data:browsersData about browsers (versions, release dates, etc). This data is used for validation.Data about browsers (versions, release dates, etc). This data is used for validation.infraInfrastructure issues (npm, GitHub Actions, releases) of this projectInfrastructure issues (npm, GitHub Actions, releases) of this project
Metadata
Metadata
Assignees
Labels
bugConfirmed bugs in the repository (i.e. linter bugs), NOT browser implementation bugs.Confirmed bugs in the repository (i.e. linter bugs), NOT browser implementation bugs.data:browsersData about browsers (versions, release dates, etc). This data is used for validation.Data about browsers (versions, release dates, etc). This data is used for validation.infraInfrastructure issues (npm, GitHub Actions, releases) of this projectInfrastructure issues (npm, GitHub Actions, releases) of this project
Type
Fields
Give feedbackNo fields configured for issues without a type.
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?
mainbranchDo you have anything more you want to share?
No response