Improvements to BCD GitHub releases & options for downstreaming changes to consumers

[bsmth]

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?

• [ ] The current BCD release
• [X] The current version of the main branch

Do you have anything more you want to share?

We can improve how quickly consumers know about feature status by automating releases either:

• On a schedule -- this is already occurring on Tuesdays/Fridays
• When a browser has a new stable release (we should know this from browser data)

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:

• [x] https://github.com/mdn/bcd-utils/pull/24
• [x] https://github.com/mdn/browser-compat-data/pull/20561

For background info,

• Dependabot typically adds 24 hours delay between a GitHub release in BCD and a downstream PR opened (e.g., package.json)
• Nightly builds will add another ~24 hours to the data being visible on MDN

Notes

• What may help is release-please or release drafter for floating PR with all changes since last release