Skip to content
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.

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

fix(deps): update dependency @mdn/browser-compat-data to v4.0.5 #3930

Merged
merged 1 commit into from
Sep 26, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 23, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@mdn/browser-compat-data 4.0.4 -> 4.0.5 age adoption passing confidence

Release Notes

mdn/browser-compat-data

v4.0.5

Compare Source

September 23, 2021

Notable changes
  • The feature-naming convention returns_promise has been adopted for features that capture some but not all browsers' APIs returning a Promise. The new data guideline brings consistency to competing styles used throughout the API data.

    The following features have been renamed to returns_promise (#​11630):

    • api.BaseAudioContext.decodeAudioData.promise_syntax
    • api.Document.exitFullscreen.returns_a_promise
    • api.Element.requestFullscreen.returns_a_promise
    • api.OfflineAudioContext.startRendering.Promise_based_startRendering

    The feature api.RTCPeerConnection.getStats.with_callbacks was removed and the data for several RTCPeerConnection methods expanded with returns_promise data. The following features have been added (#​12300):

    • api.RTCPeerConnection.addIceCandidate.returns_promise
    • api.RTCPeerConnection.createAnswer.returns_promise
    • api.RTCPeerConnection.createOffer.returns_promise
    • api.RTCPeerConnection.getStats.returns_promise
    • api.RTCPeerConnection.setLocalDescription.returns_promise
    • api.RTCPeerConnection.setRemoteDescription.returns_promise
  • The following non-existent, long-removed, or otherwise irrelevant features have been removed:

Known issues
  • In v3.3.9, the structure of features for css.properties.place-content, place-items, and place-self changed (#​11214). This is an incomplete fix to the problem of undocumented namespaces appearing in places where you might otherwise expect compatability data. The restructuring of the data is a work in progress and may change again in a future release. See #​6175 for more information.
Statistics
  • 8 contributors have changed 53 files with 1,649 additions and 2,580 deletions in 54 commits (v4.0.4...v4.0.5)
  • 13,414 total features
  • 809 total contributors
  • 3,583 total stargazers

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/mdn-browser-compat-data-4.x branch 2 times, most recently from e39075c to 85fffea Compare September 25, 2021 13:49
@renovate renovate bot force-pushed the renovate/mdn-browser-compat-data-4.x branch from 85fffea to 94da435 Compare September 26, 2021 00:38
@renovate renovate bot merged commit 0f32ef1 into master Sep 26, 2021
@renovate renovate bot deleted the renovate/mdn-browser-compat-data-4.x branch September 26, 2021 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant