Improvements to BCD GitHub releases & options for downstreaming changes to consumers #22919
Open
3 of 4 tasks
Labels
enhancement 🥇
Nice to have features.
infra 🏗️
Infrastructure issues (npm, GitHub Actions, releases) of this project
What type of issue is this?
Infrastructure issue
What is the issue?
Data may be in BCD on a feature level (X supports Y in version Z), but the dependent systems may wait for this information to be made available via releases. This is mostly apparent when a new browser version is released and readers check MDN / Caniuse pages.
What behavior were you expecting?
The day of a major/stable browser release, a BCD GitHub release is available so that consumers can pick up data that is already captured in BCD on the feature level (X is now supported) and browser data (browser version X is now available) in their builds.
What version(s) of BCD is the issue present in?
main
branchDo you have anything more you want to share?
We can improve how quickly consumers know about feature status by automating releases either:
Additionally, for us to consider is how consumers (mdn/yari, web-platform-dx/web-features) can use their own workflows triggered upon BCD release instead of waiting for dependabot. This may be documentation only, as we can see here:
For background info,
Notes
The text was updated successfully, but these errors were encountered: