Run details

NxWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix-react-native-migration-docs
- Runs and Agents
- Timeline
- Configuration
- Self-Healing CI
- Project Graph
- Resource Usage
- Analysis
- Conformance
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

Sign in

chore(repo): validate migration implementation paths in the markdown assets rule The rule vouched for the `prompt` and `documentation` files a migrations.json references, but not for the implementation each entry actually runs, so an entry pointing at a file the build never emits still passed. Implementations are tsc outputs rather than copied assets, so the assets pipeline cannot answer for them. The published path maps back through the package's own `rootDir`/`outDir` instead, and the source file it comes from has to exist. A package whose tsconfig declares neither is left unchecked rather than checked against a guessed layout.

nx affected -t e2e-macos-local --parallel=2 --base=00e18da50337714f2ee582cd2886e9492bc78365 --head=5c5244b04f45b4a51c51cea64150f9927dc03f41

Succeeded

3 CPU cores

5c5244b036378

3%

Cache hits

4 of 157 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

6 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools