fix: include v0 preamble in offchain message size checks #5933
mcintyre94Annotations
20 warnings
|
Build & Test on Node lts/*
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/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build & Test on Node lts/*:
packages/fixed-points/src/__tests__/parsing-test.ts#L29
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node lts/*:
packages/fixed-points/src/__tests__/rounding-test.ts#L9
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node lts/*:
packages/fixed-points/src/__tests__/binary-core-test.ts#L219
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node lts/*:
packages/fixed-points/src/__tests__/binary-core-test.ts#L211
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node lts/*:
packages/fixed-points/src/__tests__/binary-core-test.ts#L200
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node lts/*:
packages/fixed-points/src/__tests__/decimal-core-test.ts#L276
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node lts/*:
packages/fixed-points/src/__tests__/decimal-core-test.ts#L265
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node lts/*:
packages/fixed-points/src/__tests__/decimal-core-test.ts#L128
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node lts/*:
packages/fixed-points/src/__tests__/decimal-core-test.ts#L117
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node current
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/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build & Test on Node current:
packages/fixed-points/src/__tests__/parsing-test.ts#L29
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node current:
packages/fixed-points/src/__tests__/rounding-test.ts#L9
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node current:
packages/fixed-points/src/__tests__/binary-core-test.ts#L219
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node current:
packages/fixed-points/src/__tests__/binary-core-test.ts#L211
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node current:
packages/fixed-points/src/__tests__/binary-core-test.ts#L200
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node current:
packages/fixed-points/src/__tests__/decimal-core-test.ts#L276
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node current:
packages/fixed-points/src/__tests__/decimal-core-test.ts#L265
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node current:
packages/fixed-points/src/__tests__/decimal-core-test.ts#L128
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|
|
Build & Test on Node current:
packages/fixed-points/src/__tests__/decimal-core-test.ts#L117
Every test should have either `expect.assertions(<number of assertions>)` or `expect.hasAssertions()` as its first expression
|