v2.0.29

2.0.29 (2026-08-01)

Bug Fixes

• start the server instead of throwing on APIFY_LOG_LEVEL (d4953bd)

  Setting APIFY_LOG_LEVEL to the string 'OFF' made every startup throw
  'Options "level" must be one of log.LEVELS enum!' before the server could
  serve anything, so the binary has been unusable since the variable was
  introduced in c5ab6b0.

  @apify/log resolves level names with a truthiness check, and LogLevel.OFF
  is 0, so 'OFF' falls through to Number('OFF') = NaN, which the Log it
  constructs at import time rejects. The same logic is present in the
  @apify/log version current at c5ab6b0, so this was never a dependency
  regression. Setting the numeric level silences the logger as intended.

  The variable is still needed: crawlee applies its own logLevel lazily, so
  without this the level is INFO from import until index.ts calls setLevel,
  and @apify/log writes INFO to stdout, which carries the JSON-RPC channel.

  • Add a regression test that loads the real @apify/log in a child process;
    index.test.ts mocks crawlee wholesale, which is why the suite stayed
    green while the binary could not start