New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

API deployment uses previous BCD version #133

Closed

caugner opened this issue Jan 15, 2025 · 1 comment · Fixed by mdn/browser-compat-data#25661

Labels

Contributor

caugner commented Jan 15, 2025

I noticed repeatedly that the BCD tables on MDN don't reflect the state of the latest BCD release.

For example, on 2024-01-15 https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code#browser_compatibility does not include the change from mdn/browser-compat-data#25644, although this was released in BCD v5.6.30 on 2025-01-14.

Similar issue with mdn/browser-compat-data#25630 that landed in BCD v5.6.29, but only appeared on https://developer.mozilla.org/en-US/docs/Web/API/Navigator/gpu#browser_compatibility with the BCD v5.6.30 release.

caugner mentioned this issue

fix(workflows/release): trigger deployment after publish mdn/browser-compat-data#25661

Merged

mdn-bot added the needs triage label

Contributor Author

caugner commented Jan 22, 2025

Resolved via mdn/browser-compat-data#25661.

Verified via latest prod deployment, which used latest BCD 5.6.32: https://github.com/mdn/bcd-utils/actions/runs/12889981283/job/35938495366#step:5:14

caugner closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment