fix(fractional): support nested JSON Logic, boolean names, negative weight clamping, null key error #43
aepfliwasm-staleness.yml
on: pull_request
Check WASM Binary Staleness
22s
Annotations
6 warnings
|
Check WASM Binary Staleness
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Check WASM Binary Staleness
The release-please workflow will update all copies on the release PR.
|
|
Check WASM Binary Staleness
Some language directory WASM copies are out of sync with the root binary.
|
|
Check WASM Binary Staleness
go/flagd_evaluator.wasm does not match root flagd_evaluator.wasm
|
|
Check WASM Binary Staleness
This is expected during development. The release-please workflow will rebuild and commit the binary on the release PR.
|
|
Check WASM Binary Staleness
The committed flagd_evaluator.wasm is stale — it does not match the WASM built from the current Rust source.
|