`infisical run` suddenly demands an `.infisical.json` exist when run with `--token`

[dbsanfte]

Describe the bug

Somewhere between versions 0.36.11 and the current 0.36.17, the behaviour of infisical run has changed, such that it demands that an .infisical.json file exist, even if you are authenticating with --token.

To Reproduce

With 0.36.17:

~$ INFISICAL_DISABLE_UPDATE_CHECK=true infisical run --silent --token "$INFISICAL_TOKEN" --env "$INFISICAL_ENVIRONMENT" --path "$INFISICAL_PATH" --domain "$INFISICAL_DOMAIN" -- /bin/bash -c 'echo hello world'

error: file not found: .infisical.json
Unable to get local project details


If this issue continues, get support at https://infisical.com/slack

Expected behavior

With 0.36.11:

~$ INFISICAL_DISABLE_UPDATE_CHECK=true infisical run --silent --token "$INFISICAL_TOKEN" --env "$INFISICAL_ENVIRONMENT" --path "$INFISICAL_PATH" --domain "$INFISICAL_DOMAIN" -- /bin/bash -c 'echo hello world'

1:33PM INF Injecting 287 Infisical secrets into your application process
hello world

Platform you are having the issue on:

Ubuntu 24.04

Additional context

Undocumented change in behaviour.

[chelog]

+1

This started happening in 0.36.17. Even when setting project id with env variable or in json config, cli throws 403 http error refusing to start

Rolled back to 0.36.16 and that fixed the problem for me. There shouldn't be any breaking changes like this in a patch version, please review recent changes

[maidul98]

Hi @chelog , we are rolling out a new update. Once this is done, can you please try again on your side?

Workflow running (20 minutes): https://github.com/Infisical/infisical/actions/runs/13904308088