GoogleChromeLabs / GoogleChromeLabs/chrome-for-testing
Wrong Stable version published in API
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 159
- Avg merge
- 18h 37m
- Merged PRs (30d)
- 3
Description
> [!IMPORTANT]
> **This issue tracker tracks bugs with [the Chrome for Testing availability dashboard](https://googlechromelabs.github.io/chrome-for-testing/) and [its API](https://github.com/GoogleChromeLabs/chrome-for-testing#json-api-endpoints).**
>
> - Are you reporting a bug that reproduces in Chrome for Testing but not in Chrome? File it here: https://goo.gle/cftbug
> - Are you reporting a bug in Chrome? File it here: https://crbug.com/new
**Describe the bug**
At 26-06-2026
Chrome for Testing availability dashboard shows latest stable version: 149.0.7827.201
API shows latest stable version: 150.0.7871.24
When check https://chromiumdash.appspot.com/schedule it shows that version 150 will be released in Stable chanel at Tue, Jul 14, 2026
It seems API shows wrong version for Stable channel.
**To reproduce**
Steps to reproduce the behavior:
Just use https://googlechromelabs.github.io/chrome-for-testing/last-known-good-versions-with-downloads.json
**Expected behavior**
A clear and concise description of what you expected to happen.
https://googlechromelabs.github.io/chrome-for-testing/last-known-good-versions-with-downloads.json should return version 149.0.7827.201 for stable channel now, and not version 150.0.7871.24
[last-known-good-versions-with-downloads.json](https://github.com/user-attachments/files/29368046/last-known-good-versions-with-downloads.json)
Contributor guide
Research direction
Start by comparing last-known-good-versions-with-downloads.json with the Chrome release schedule for the reported date and stable channel. Trace the API's source or generation entry point for these version values, then verify that the stable response reports 149.0.7827.201 rather than the upcoming 150.0.7871.24.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100