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

chore(deps): update rust-wasm-bindgen monorepo #3888

Closed
wants to merge 1 commit into from

Conversation

ScriptedAlchemy
Copy link
Member

@ScriptedAlchemy ScriptedAlchemy commented May 11, 2024

This PR contains the following updates:

Package Type Update Change
wasm-bindgen-futures (source) dev-dependencies minor 0.3.22 -> 0.4.0
wasm-bindgen-test dev-dependencies minor 0.2.45 -> 0.3.0

Release Notes

rustwasm/wasm-bindgen (wasm-bindgen-test)

v0.2.50

Compare Source

Released 2019-08-19.

Added
  • Experimental support with a WASM_INTERFACE_TYPES=1 environment variable has
    been added to emit a Wasm Interface Types custom section, making the output of
    wasm-bindgen a single standalone WebAssembly file.
    #​1725
Fixed
  • Unrelated errors are now no longer accidentally swallowed by the
    instantiateStreaming fallback.
    #​1723

v0.2.49

Compare Source

Released 2019-08-14.

Added
  • Add binding for Element.getElementsByClassName.
    #​1665

  • PartialEq and Eq are now implemented for all web-sys types.
    #​1673

  • The wasm-bindgen-futures crate now has support for futures when the
    experimental WebAssembly threading feature is enabled.
    #​1514

  • A new enable-interning feature is available to intern strings and reduce the
    cost of transferring strings across the JS/Rust boundary.
    #​1612

  • The wasm-bindgen CLI has experimental support for reading native
    webidl-bindings custom sections and generating JS glue. This support is in
    addition to Rust's own custom sections and allows using wasm-bindgen with
    binaries produced by other than rustc possibly.
    #​1690

  • New environment variables have been added to configure webdriver startup
    arguments.
    #​1703

  • New JsValue::{is_truthy,is_falsy} methods are now available.
    #​1638

Changed
  • JS import shims are now skipped again when they are unnecessary.
    #​1654

  • WebAssembly output files now directly embed the module/name for imports if
    supported for the target and the import, reducing JS shims even further.
    #​1689

Fixed
  • Support for threads have been updated for LLVM 9 and nightly Rust.
    #​1675
    #​1688

  • The anyref passes in wasm-bindgen have seen a number of fixes to improve
    their correctness and get the full test suite running.
    #​1692
    #​1704

  • Support for futures-preview 0.3.0-alpha.18 has been added to
    wasm-bindgen-futures.
    #​1716


v0.2.48

Compare Source

Released 2019-07-11.

Added
  • All typed arrays now implement From for the corresponding Rust slice type,
    providing a safe way to create an instance which copies the data.
    #​1620

  • Function::bind{2,3,4} are now available in js-sys.
    #​1633

Changed
  • More WebGL methods have been updated to use shared slices instead of mutable
    slices.
    #​1639

  • When using the bundler target the import of the wasm file now uses the
    .wasm extension to ensure a wasm file is loaded.
    #​1646

  • The old internal Stack trait has been removed since it is no longer used.
    #​1624

Fixed
  • The js_sys::global() accessor now attempts other strategies before falling
    back to a Function constructor which can violate some strict CSP settings.
    #​1650

  • Dropping a JsFuture no longer logs a benign error to the console.
    #​1649

  • Fixed an assertion which could happen in some modules when generating
    bindings.
    #​1617


v0.2.47

Compare Source

Released 2019-06-19.

Changed
  • The HtmlHyperlinkElement should now include more native methods after a
    small edit to the WebIDL.
    #​1604

  • Duplicate names for getters/setters now have a first-class wasm-bindgen
    error.
    #​1605

Fixed
  • TypeScript definition of init with --target web now reflects that the
    first argument is optional.
    #​1599

  • A panic with the futures 0.3 support has been fixed.
    #​1598

  • More slice types are recognized as becoming immutable in some WebIDL methods.
    #​1602

  • The function table is now no longer too aggressively removed.
    #​1606


v0.2.46

Compare Source

Released 2019-06-14.

Added
  • Bindings for Array#flat and Array#flatMap have been added.
    #​1573

  • All #[wasm_bindgen] types now AsRef to themselves.
    #​1583

  • When using --target web the path passed to init is no longer required.
    #​1579

Fixed
  • Some diagnostics related to compiler errors in #[wasm_bindgen] have been
    improved.
    #​1550

  • The support for weak references has been updated to the current JS proposal.
    #​1557

  • Documentation and feature gating for web-sys dictionaries has improved.
    #​1572

  • Getter and setter TypeScript has been fixed.
    #​1577

  • The env_logger crate and its tree of dependencies is no longer required to
    build web-sys.
    #​1586



Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

Copy link

Workflow status is failure ❌
Unfortunately test report wasn't generated, it can be if no workspaces changed. Please check the workflow run below.
Link to GitHub workflow: Github Workflow Link

@github-actions github-actions bot added the workflow-failure Workflow is failed label May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workflow-failure Workflow is failed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant