1
0
mirror of https://github.com/alecthomas/chroma.git synced 2026-06-11 21:52:26 +02:00
Files
renovate[bot] 4498d71bf4 chore(deps): update dependency binaryen to v129 (#1238)
This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [binaryen](https://redirect.github.com/WebAssembly/binaryen) | major |
`125` → `129` |

---

### Release Notes

<details>
<summary>WebAssembly/binaryen (binaryen)</summary>

###
[`v129`](https://redirect.github.com/WebAssembly/binaryen/blob/HEAD/CHANGELOG.md#v129)

- Add a `BinaryenDataSegmentRef` type to the C API.
([#&#8203;8286](https://redirect.github.com/WebAssembly/binaryen/issues/8286))
- Add `BinaryenGetDataSegment` and `BinaryenGetDataSegmentByIndex` to
the C API, which allow looking up a data segment by name or index.
- Add `BinaryenDataSegmentGetName` to the C API, which allows looking up
a data segment's name.
- Convert `BinaryenGetMemorySegmentByteOffset`,
`BinaryenGetMemorySegmentByteLength`, `BinaryenGetMemorySegmentPassive`
and `BinaryenCopyMemorySegmentData` to take a `BinaryenDataSegmentRef`
instead of a name.
- Add `module.getDataSegment`, `module.getDataSegmentByIndex` to the JS
API, which allows looking up a data segment by name or index.
- Convert `module.getMemorySegmentInfo` to take a data segment reference
instead of a name, and return the name as part of the info.
- Add support for non-nullable table types and initialization
expressions for
tables. This comes with a breaking change to C API: `BinaryenAddTable`
takes
an additional `BinaryenExpressionRef` parameter to provide an
initialization
expression. This may be set to NULL for tables without an initializer.
In JS
this parameter is optional and so is not breaking.
([#&#8203;8405](https://redirect.github.com/WebAssembly/binaryen/issues/8405))
- \[multibyte] Add multibyte array store and load instructions.
([#&#8203;8059](https://redirect.github.com/WebAssembly/binaryen/issues/8059),
[#&#8203;8504](https://redirect.github.com/WebAssembly/binaryen/issues/8504))
- MinifyImportsAndExports now has a new output format using JSON. This
was
changed while fixing bugs with colliding module names (to avoid two
breaking
changes to the output).
([#&#8203;8550](https://redirect.github.com/WebAssembly/binaryen/issues/8550))
- Update from C++17 to C++20
([#&#8203;8218](https://redirect.github.com/WebAssembly/binaryen/issues/8218))

###
[`v128`](https://redirect.github.com/WebAssembly/binaryen/blob/HEAD/CHANGELOG.md#v128)

- (bugfix release)

###
[`v127`](https://redirect.github.com/WebAssembly/binaryen/blob/HEAD/CHANGELOG.md#v127)

- Implement the Custom Page Sizes proposal.
([#&#8203;8307](https://redirect.github.com/WebAssembly/binaryen/issues/8307))
- New intrinsic: `@binaryen.idempotent`.
([#&#8203;8354](https://redirect.github.com/WebAssembly/binaryen/issues/8354))
- Add --strip-debug option to wasm-split
([#&#8203;8432](https://redirect.github.com/WebAssembly/binaryen/issues/8432))
- The emscripten build of binaryen no longer targets pure JS (via
wasm2js) by
default. This allows us to enable WASM\_BIGINT and other features that
wasm2js does not support. There is now just a single binaryen\_js
target. It
should still be possible to inject `-sWASM=0` as a linker flag but this
is
not officially supported.
([#&#8203;7995](https://redirect.github.com/WebAssembly/binaryen/issues/7995))
- As part of enabling the `WASM_BIGINT` in the emscripten build the JS
API for
manipulating 64-bit values was changed. These APIs, such as `i64.const`
and `setValueI64`, previously took a hi/low pair but now take a single
value
which can be bigint or a number. Passing two values to these APIs will
now
trigger an assertion.
([#&#8203;7984](https://redirect.github.com/WebAssembly/binaryen/issues/7984))

###
[`v126`](https://redirect.github.com/WebAssembly/binaryen/blob/HEAD/CHANGELOG.md#v126)

- New intrinsic: `@binaryen.removable.if.unused`.
([#&#8203;8268](https://redirect.github.com/WebAssembly/binaryen/issues/8268))
- New intrinsic: `@binaryen.js.called`.
([#&#8203;8324](https://redirect.github.com/WebAssembly/binaryen/issues/8324))
- Add a pass to remove toolchain annotations,
`--strip-toolchain-annotations`,
for the above two intrinsics and future ones.
([#&#8203;8301](https://redirect.github.com/WebAssembly/binaryen/issues/8301))
- Add a pass to remove relaxed SIMD instructions,
`--remove-relaxed-simd`

([#&#8203;8300](https://redirect.github.com/WebAssembly/binaryen/issues/8300))
- JS API: Throw useful exceptions on parse errors in binaryen.js, rather
than
fatally error and shut down the entire process.
([#&#8203;8264](https://redirect.github.com/WebAssembly/binaryen/issues/8264))
- Implement function-level inlining hints (previously we only supported
this
annotation on calls, not functions themselves).
([#&#8203;8265](https://redirect.github.com/WebAssembly/binaryen/issues/8265))
- Update C and JS libraries with relaxed atomics support
([#&#8203;8248](https://redirect.github.com/WebAssembly/binaryen/issues/8248))
- wasm-split: Export/Import only necessary elements, avoiding bloat.
([#&#8203;8221](https://redirect.github.com/WebAssembly/binaryen/issues/8221))
- Use `std::quick_exit` in `wasm-opt` etc. tools, to skip cleanup.
([#&#8203;8212](https://redirect.github.com/WebAssembly/binaryen/issues/8212))
- The C API now has separate functions for `CallRef` and `ReturnCallRef`
matching the semantics of `Call` and `ReturnCall`
([#&#8203;8121](https://redirect.github.com/WebAssembly/binaryen/issues/8121)).
- Breaking changes to the C and JS APIs related to atomic operations, in
order
to support the relaxed atomics proposal (currently a part of the [shared
everything threads
proposal](https://redirect.github.com/WebAssembly/shared-everything-threads))
([#&#8203;8248](https://redirect.github.com/WebAssembly/binaryen/issues/8248)).
- `setAtomic` on atomic loads/stores is removed in favor of
`setMemoryOrder`.
`BinaryenLoadSetAtomic(expr, false)` / `load.setAtomic(false)` may be
    replaced with `BinaryenLoadSetMemoryOrder(expr,
BinaryenMemoryOrderUnordered())`, `BinaryenLoadSetAtomic(expr, true)` /
    `load.setAtomic(true)` may be replaced with
    `BinaryenLoadSetMemoryOrder(expr, BinaryenMemoryOrderSeqCst())`, and
likewise for `Store`s. In addition to Unordered and SeqCst, these
functions
    support AcqRel which implements acquire/release semantics.
- Likewise `BinaryenAtomicLoad`, `BinaryenAtomicStore`,
`BinaryenAtomicRMW`,
    and `BinaryenAtomicCmpxchg` are updated with an additional
    `BinaryenMemoryOrder` param. The functions formerly implicitly used
`BinaryenMemoryOrderSeqCst()`. In JS this param is optional and thus not
    breaking.

</details>

---

### Configuration

📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM, only on
Monday ( * 0-3 * * 1 ) (UTC), 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.

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/alecthomas/chroma).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMDIuMTEiLCJ1cGRhdGVkSW5WZXIiOiI0My4xMDIuMTEiLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIiLCJsYWJlbHMiOltdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2026-05-02 08:54:15 +10:00

Symbolic link
1 line
17 B
Plaintext