chore(repo): update nx to 22.1.0-beta.2

[FrozenPandaz]

Updating Nx from 22.1.0-beta.0 to 22.1.0-beta.2

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 8716e84

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e-ci,ty...	✅ Succeeded	6m 22s	View ↗
nx-cloud record -- yarn nx sync:check	✅ Succeeded	4s	View ↗
nx-cloud record -- yarn nx run-many -t ktfmtFormat	✅ Succeeded	4m 55s	View ↗
nx run-many -t ktfmtFormat	✅ Succeeded	4m 51s	View ↗
nx-cloud record -- yarn nx format:check --verbose	✅ Succeeded	7s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-10-30 14:08:19 UTC

[nx-cloud]

Nx Cloud has identified a possible root cause for your failed CI:

The failure was classified as 'environment_state' rather than 'code_change' for the following reasons:

1. No Direct Link Between Changes and Failure
   The PR only updates Nx package versions in package.json from 22.1.0-beta.0 to 22.1.0-beta.2. The terminal output does not show any errors that directly reference these changes, such as compilation errors, type mismatches, or API breaking changes that would be expected from a dependency update.

2. High-Level Orchestration Failure
   The error message "CI execution '18889624054-1-linux' failed. Reason: One or more workflows failed" is a generic Nx Cloud distributed execution failure. This occurs at the orchestration layer, not during the actual execution of the ktfmtFormat task itself. No specific workflow failure details or task-level errors are provided.

3. Absence of Task-Specific Errors
   The output does not contain:

   • Kotlin formatting violations that would fail ktfmtFormat
   • Syntax or compilation errors
   • Failed test assertions
   • Missing dependencies or import errors

   These types of errors would be expected if the Nx version update introduced breaking changes.

4. Only Warnings Present
   The warnings shown ("Was not able to require.resolve module" marked as "This may be expected" and the url.parse() deprecation warning) are not critical failures and do not correlate with the package version changes made in the PR.

5. Environmental Bias Applied
   Per the classification guidelines, when a failure involves external service orchestration (Nx Cloud) and lacks explicit evidence linking code changes to the failure, the default classification should be 'environment_state' rather than 'code_change'. The distributed execution system failure suggests an infrastructure or service-level issue.

A code change would likely not resolve this issue, so no action was taken.

View in Nx Cloud ↗

_{🎓 To learn more about Self Healing CI, please visit nx.dev}