Skip to content

BAU: Bump the eslint group across 1 directory with 5 updates #2285

BAU: Bump the eslint group across 1 directory with 5 updates

BAU: Bump the eslint group across 1 directory with 5 updates #2285

Triggered via pull request January 15, 2026 03:06
Status Failure
Total duration 4m 53s
Artifacts 1

Annotations

9 errors
Run tests / API
Process completed with exit code 1.
Given there is a ./well-known/jwks with a key to encrypt claims › when key rotation is enabled and legacy fallback feature is enabled › Check HMRC CRI › and successfully receives a 201 created with a valid session id: integration-tests/api-gateway/cri-decrypt-verify/index.test.ts#L155
ValidationException: The provided key element does not match the schema at throwDefaultError (../../node_modules/@smithy/smithy-client/dist-cjs/index.js:388:20) at ../../node_modules/@smithy/smithy-client/dist-cjs/index.js:397:5 at de_CommandError (../../node_modules/@aws-sdk/client-dynamodb/dist-cjs/index.js:2297:14) at ../../node_modules/@smithy/middleware-serde/dist-cjs/index.js:36:20 at ../../node_modules/@aws-sdk/lib-dynamodb/dist-cjs/index.js:163:30 at ../../node_modules/@smithy/core/dist-cjs/index.js:193:18 at ../../node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38 at ../../node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:33:22 at async Promise.all (index 0) at Object.<anonymous> (cri-decrypt-verify/index.test.ts:155:11)
Given there is a ./well-known/jwks with a key to encrypt claims › when key rotation is enabled and legacy fallback feature is enabled › Check HMRC CRI › session endpoint is called: integration-tests/api-gateway/cri-decrypt-verify/index.test.ts#L155
ValidationException: The provided key element does not match the schema at throwDefaultError (../../node_modules/@smithy/smithy-client/dist-cjs/index.js:388:20) at ../../node_modules/@smithy/smithy-client/dist-cjs/index.js:397:5 at de_CommandError (../../node_modules/@aws-sdk/client-dynamodb/dist-cjs/index.js:2297:14) at ../../node_modules/@smithy/middleware-serde/dist-cjs/index.js:36:20 at ../../node_modules/@aws-sdk/lib-dynamodb/dist-cjs/index.js:163:30 at ../../node_modules/@smithy/core/dist-cjs/index.js:193:18 at ../../node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38 at ../../node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:33:22 at async Promise.all (index 0) at Object.<anonymous> (cri-decrypt-verify/index.test.ts:155:11)
Given there is a ./well-known/jwks with a key to encrypt claims › when key rotation is enabled and legacy fallback feature is enabled › and response is verified successfully: integration-tests/api-gateway/cri-decrypt-verify/index.test.ts#L101
expect(received).toBe(expected) // Object.is equality Expected: "ES256" Received: undefined at Object.<anonymous> (cri-decrypt-verify/index.test.ts:101:57)
Given there is a ./well-known/jwks with a key to encrypt claims › when key rotation is enabled and legacy fallback feature is enabled › then the headless core stub makes a request to the Start Endpoint: integration-tests/api-gateway/cri-decrypt-verify/index.test.ts#L62
thrown: "Exceeded timeout of 5000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at cri-decrypt-verify/index.test.ts:62:7 at cri-decrypt-verify/index.test.ts:61:5 at Array.forEach (<anonymous>) at Object.<anonymous> (cri-decrypt-verify/index.test.ts:28:3)

Artifacts

Produced during runtime
Name Size Digest
coverage
4.69 KB
sha256:4480529c4f43995f9aef8599f91ed15d6ad9270db62794c692ec4f0b7007149f