nxNx
GitHubNxWorkspace
GitHub
  • 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-cloud record -- pnpm nx-cloud conformance:check
Succeeded
Linux
4 CPU cores
5c5244b036378

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools