fix(deps): upgrade is-in-ci 1.0.0 → 2.0.0

[megadave19]

What

Upgrades is-in-ci from 1.0.0 to 2.0.0.

Why

Functionality related to CI detection may fail, leading to potential false positives, and projects running on Node.js versions lower than 20 will be incompatible, posing a high risk for CI/CD pipelines.

🟡 Confidence: 60/100 (medium) — calibrated

Signals: changelog parsing + semantic API diffing (dts, 0% coverage)

Opened as Draft because the score is below your configured threshold — please review and mark ready when validated.

Per-symbol breakdown:

• CI_ prefix detection — 60/100 · incomplete analysis
• Node.js version requirement — 60/100 · incomplete analysis

Evidence

• CI_ prefix detection (behavior-changed): The package no longer detects the 'CI_' prefix as an indicator of CI, which may lead to false-positives in CI detection.
• Node.js version requirement (removed): The package now requires Node.js version 20 or higher, which may cause compatibility issues with older Node.js versions.

Changes

• package.json: Bumped is-in-ci from 1.0.0 to ^2.0.0

Verification Results

• ✅ TypeScript check passed in isolated Docker sandbox (--network=none)

⚠ Not Analyzed

• Full runtime behavior: changelog-parsing-only analysis. Semantic API diffing not available.

---

Generated by Mendel v1.5. Open as Draft — mark ready for review when you have validated.