v0.8.0 — World-class SDK Upgrade #1
Triggered via release
March 29, 2026 18:10
karlwaldman
published
v0.8.0
Status
Failure
Total duration
2m 42s
Artifacts
–
Annotations
10 errors and 1 warning
|
tests/historical.test.ts > Historical Prices > getHistoricalPrices() > Date Parameter Handling > should handle year-spanning date ranges:
tests/historical.test.ts#L199
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/historical.test.ts:199:7
|
|
tests/historical.test.ts > Historical Prices > getHistoricalPrices() > Date Parameter Handling > should pass both start_date and end_date for custom ranges:
tests/historical.test.ts#L174
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/historical.test.ts:174:7
|
|
tests/historical.test.ts > Historical Prices > getHistoricalPrices() > Date Parameter Handling > should pass end_date parameter correctly:
tests/historical.test.ts#L153
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/historical.test.ts:153:7
|
|
tests/historical.test.ts > Historical Prices > getHistoricalPrices() > Date Parameter Handling > should pass start_date parameter correctly:
tests/historical.test.ts#L132
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/historical.test.ts:132:7
|
|
tests/historical.test.ts > Historical Prices > getHistoricalPrices() > Endpoint Selection (BUG FIX CRITICAL) > should use past_year endpoint even for period queries:
tests/historical.test.ts#L108
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/historical.test.ts:108:7
|
|
tests/historical.test.ts > Historical Prices > getHistoricalPrices() > Endpoint Selection (BUG FIX CRITICAL) > should NOT use /v1/prices endpoint (broken endpoint):
tests/historical.test.ts#L82
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/historical.test.ts:82:7
|
|
tests/historical.test.ts > Historical Prices > getHistoricalPrices() > Endpoint Selection (BUG FIX CRITICAL) > should use /v1/prices/past_year endpoint for date range queries:
tests/historical.test.ts#L38
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/historical.test.ts:38:7
|
|
tests/error-handling.test.ts > Error Handling > Timeout Handling > should pass abort signal to fetch:
src/client.ts#L413
OilPriceAPIError: Request failed after 3 attempts: response.text is not a function
❯ OilPriceAPI.request src/client.ts:413:19
❯ tests/error-handling.test.ts:280:7
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { statusCode: undefined, code: 'NETWORK_ERROR' }
|
|
tests/error-handling.test.ts > Error Handling > Server Errors (5xx) > should retry on server errors:
src/client.ts#L413
OilPriceAPIError: Request failed after 3 attempts: response.text is not a function
❯ OilPriceAPI.request src/client.ts:413:19
❯ tests/error-handling.test.ts:224:22
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { statusCode: undefined, code: 'NETWORK_ERROR' }
|
|
tests/client.test.ts > OilPriceAPI > should throw error if API key is missing:
tests/client.test.ts#L8
AssertionError: expected [Function] to throw error including 'API key is required' but got 'API key required. Set OILPRICEAPI_KEY…'
Expected: "API key is required"
Received: "API key required. Set OILPRICEAPI_KEY env var or pass apiKey in config."
❯ tests/client.test.ts:8:8
|
|
Publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/
|