🤖 Weekly update: refresh web spec data - #16
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated weekly refresh of the generated type baselines.
This PR is opened only because the latest
@webref/*/@mdn/*datachanged at least one published type cut. It bundles the full update:
package-lock.json— bumped@webref/*and@mdn/*.inputfiles/mdn.json— re-fetched MDN metadata.baselines/**— regenerated type definitions (see the diff).Packages this merge will republish
Computed by diffing each cut against its current npm
latest(predicted next version shown):
@baseline-types/dom-2022→1.0.20260711@baseline-types/dom-2023→1.0.20260711@baseline-types/dom-2024→1.0.20260711@baseline-types/dom-2025→1.0.20260711@baseline-types/dom-newly-available→1.0.20260711@baseline-types/dom-widely-available→1.0.20260711Merging keeps the published
@baseline-types/dom-<target>packages in syncwith the latest browser-compat data. Once this PR is merged, the
Release baseline packages workflow automatically rebuilds the cuts and
publishes any
@baseline-types/dom-<target>package whose types changed(and cuts a GitHub Release per published package). No manual publish step
is needed — just review the diff and merge.