Closed austinborn closed 3 months ago
Latest commit: 8ada2c86d1334f47a8eb0811614e9748c8e80581
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
Single test failing:
FAIL packages/sources/cryptocompare/test/integration/adapter.test.ts (5.554 s)
● execute › crypto api › should return success
expect(received).toBe(expected) // Object.is equality
Expected: 200
Received: 504
40 | mockCryptoSuccess()
41 | const response = await testAdapter.request(data)
> 42 | expect(response.statusCode).toBe(200)
| ^
43 | expect(response.json()).toMatchSnapshot()
44 | })
45 |
at Object.toBe (packages/sources/cryptocompare/test/integration/adapter.test.ts:42:35)
We are bumping a lot of things at the same time, have we considered like a more phased rollout or that is not really necessary here
We are bumping a lot of things at the same time, have we considered like a more phased rollout or that is not really necessary here
Historically it's been practice to bump all EAs at once for framework updates, but we can certainly revisit that. The main concern is that if framework versions diverge then it isn't clear what capabilities a given package supports.
Description
WS_ENABLED=true
Steps to Test
TBD
Quality Assurance
infra-k8s
configuration file.adapter-secrets
configuration file or update the soak testing blacklist.test-payload.json
file with relevant requests.feature/x
,chore/x
,release/x
,hotfix/x
,fix/x
) or is created from Jira.