Auto-detect non-interactive mode in CI / non-TTY environments

[EvanBacon]

Why

eas build -p android prompts for keystore generation and fails in CI or non-TTY environments:

Input is required, but stdin is not readable. Failed to display prompt: Generate a new Android Keystore?

Passing --non-interactive works around this, but it should be auto-detected when CI=1 or stdin is not a TTY.

How

Set a default function on both --non-interactive flag definitions (EasNonInteractiveAndJsonFlags and EASNonInteractiveFlag) in packages/eas-cli/src/commandUtils/flags.ts. The default checks CI env var (via boolish from getenv) and process.stdin.isTTY.

• oclif evaluates default only when the user does NOT pass --non-interactive on CLI
• noCacheDefault: true prevents baking the developer's environment into oclif.manifest.json
• All ~60 commands using these flag definitions automatically get CI/TTY auto-detection with no other changes needed

Test Plan

• Added 5 unit tests for isNonInteractiveByDefault() covering: TTY without CI (false), CI=1 (true), CI=true (true), non-TTY stdin (true), both CI and non-TTY (true)
• All existing resolveNonInteractiveAndJsonFlags tests pass unchanged
• yarn typecheck passes
• yarn lint passes (0 errors)

PASS src/commandUtils/__tests__/flags-test.ts
  isNonInteractiveByDefault
    ✓ returns false when stdin is a TTY and CI is not set
    ✓ returns true when CI=1
    ✓ returns true when CI=true
    ✓ returns true when stdin is not a TTY
    ✓ returns true when both CI is set and stdin is not a TTY
  resolveNonInteractiveAndJsonFlags
    ✓ returns both false when no flags are set
    ✓ --json implies --non-interactive
    ✓ --non-interactive alone does not enable json
    ✓ both flags explicitly set
    ✓ both flags explicitly false
    ✓ --json false with --non-interactive true

Test Suites: 1 passed, 1 total
Tests:       11 passed, 11 total

🤖 Generated with Claude Code

[github-actions]

Subscribed to pull request

File Patterns	Mentions
**/*	@douglowder

Generated by CodeMention

[douglowder]

@EvanBacon I fixed merge conflicts, and found a change was needed in Jest setup to fix failing tests.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.58%. Comparing base (d5a3fc0) to head (55b3248).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3486      +/-   ##
==========================================
+ Coverage   53.56%   53.58%   +0.02%     
==========================================
  Files         815      815              
  Lines       34566    34572       +6     
  Branches     7175     7176       +1     
==========================================
+ Hits        18513    18521       +8     
+ Misses      15971    15969       -2     
  Partials       82       82              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[brentvatne]

should we use detectAgent()? https://www.npmjs.com/package/@vercel/detect-agent

[douglowder]

That's a good suggestion for the future -- Claude also suggested taking a look at https://www.npmjs.com/package/ci-info for this check.

[github-actions]

✅ Thank you for adding the changelog entry!