Skip to content

fix: added verification check if data token is not changed #190

fix: added verification check if data token is not changed

fix: added verification check if data token is not changed #190

Triggered via push January 16, 2025 08:26
Status Failure
Total duration 52s
Artifacts

release.yml

on: push
Lint codebase
9s
Lint codebase
Matrix: build
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 2 warnings
packages/core/src/jwt.test.ts > PublicFederatedToken > createAccessJWT: packages/core/src/jwt.test.ts#L47
AssertionError: expected {} to strictly equal { value1: 'exampleValue1', …(1) } - Expected + Received - Object { - "value1": "exampleValue1", - "value2": "exampleValue2", - } + Object {} ❯ packages/core/src/jwt.test.ts:47:27
packages/core/src/jwt.test.ts > PublicFederatedToken > createAccessJWT with TokenSigner create hook: packages/core/src/jwt.test.ts#L77
AssertionError: expected {} to strictly equal { value1: 'exampleValue1', …(1) } - Expected + Received - Object { - "value1": "exampleValue1", - "value2": "exampleValue2", - } + Object {} ❯ packages/core/src/jwt.test.ts:77:27
packages/core/src/jwt.test.ts > PublicFederatedToken > loadAccessJWT: packages/core/src/jwt.test.ts#L112
AssertionError: expected {} to strictly equal { value1: 'exampleValue1', …(1) } - Expected + Received - Object { - "value1": "exampleValue1", - "value2": "exampleValue2", - } + Object {} ❯ packages/core/src/jwt.test.ts:112:24
Build, and test on Node 22.x and ubuntu-latest
Process completed with exit code 1.
Build, and test on Node 18.x and ubuntu-latest
The job was canceled because "_22_x_ubuntu-latest" failed.
packages/core/src/jwt.test.ts > PublicFederatedToken > createAccessJWT: packages/core/src/jwt.test.ts#L47
AssertionError: expected {} to strictly equal { value1: 'exampleValue1', …(1) } - Expected + Received - Object { - "value1": "exampleValue1", - "value2": "exampleValue2", - } + Object {} ❯ packages/core/src/jwt.test.ts:47:27
packages/core/src/jwt.test.ts > PublicFederatedToken > createAccessJWT with TokenSigner create hook: packages/core/src/jwt.test.ts#L77
AssertionError: expected {} to strictly equal { value1: 'exampleValue1', …(1) } - Expected + Received - Object { - "value1": "exampleValue1", - "value2": "exampleValue2", - } + Object {} ❯ packages/core/src/jwt.test.ts:77:27
packages/core/src/jwt.test.ts > PublicFederatedToken > loadAccessJWT: packages/core/src/jwt.test.ts#L112
AssertionError: expected {} to strictly equal { value1: 'exampleValue1', …(1) } - Expected + Received - Object { - "value1": "exampleValue1", - "value2": "exampleValue2", - } + Object {} ❯ packages/core/src/jwt.test.ts:112:24
Build, and test on Node 18.x and ubuntu-latest
Process completed with exit code 1.
Build, and test on Node 20.x and ubuntu-latest
The job was canceled because "_22_x_ubuntu-latest" failed.
Build, and test on Node 20.x and ubuntu-latest
The operation was canceled.
Lint codebase
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build, and test on Node 22.x and ubuntu-latest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636