Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
master
97eb76dc docs(nx-cloud): align github app permission levels with the granted app scopes (#36741) ## Current Behavior The GitHub app permissions page heads the Checks and Workflows sections `(write)` while the app grants read and write on both. The Issues section does not mention label writes, and no conformance page documents `--printConfig`. ## Expected Behavior Heading levels match the scopes the installed app actually grants, label writes are noted, and `--printConfig` is documented. ## Related Issue(s) DOC-620 DOC-622
by Jack Hsu
Succeeded
437
81261db7 build: use precise commits to format the code
by Victor Savkin
Succeeded
master
97eb76dc docs(nx-cloud): align github app permission levels with the granted app scopes (#36741) ## Current Behavior The GitHub app permissions page heads the Checks and Workflows sections `(write)` while the app grants read and write on both. The Issues section does not mention label writes, and no conformance page documents `--printConfig`. ## Expected Behavior Heading levels match the scopes the installed app actually grants, label writes are noted, and `--printConfig` is documented. ## Related Issue(s) DOC-620 DOC-622
by Jack Hsu
Succeeded
1173
82faf3e5
by pull[bot]
Failed
2
84850abd update to latest rules
by Alex Eagle
Failed
run/nx-vite-typecheck-36744
7c0ebae6 docs(nx-cloud): align github app permission levels with the granted app scopes (#36741) ## Current Behavior The GitHub app permissions page heads the Checks and Workflows sections `(write)` while the app grants read and write on both. The Issues section does not mention label writes, and no conformance page documents `--printConfig`. ## Expected Behavior Heading levels match the scopes the installed app actually grants, label writes are noted, and `--printConfig` is documented. ## Related Issue(s) DOC-620 DOC-622
by Jack Hsu
Failed
master
f9de12d6 docs(nx-cloud): add byok docs (#36718) - Add BYOK docs --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
by Josh VanAllen
Succeeded
421
ff878e51 feat(schematics): Generate --help for every CLI function. This PR introduces the yargs package as our CLI command handler. We build up commands using yargs to take advantage of its built in --help flag formatter.
by mrmeku
Succeeded
36589
7bc19692 fix(react): correct the app schema's devServerPort deprecation note The marker claimed "the CLI aliases it", which stopped being true when the application schema's `aliases: ["devServerPort"]` was removed — that generator's CLI option has always been `--port`. A reader trusting the note would pass `--devServerPort`, match nothing, and silently get 4200: the failure this PR exists to remove. Drop the clause so all three schemas carry the same marker.
by FrozenPandaz
Failed
run/nx-vite-typecheck-36744
69916654 docs(nx-cloud): align github app permission levels with the granted app scopes (#36741) ## Current Behavior The GitHub app permissions page heads the Checks and Workflows sections `(write)` while the app grants read and write on both. The Issues section does not mention label writes, and no conformance page documents `--printConfig`. ## Expected Behavior Heading levels match the scopes the installed app actually grants, label writes are noted, and `--printConfig` is documented. ## Related Issue(s) DOC-620 DOC-622
by Jack Hsu
Succeeded
36742
450aa122 docs(nx-cloud): correct the nx-cloud cli command and flag reference ## Current Behavior Page covered 12 of 25 registered nx-cloud commands. start-agent listed a --verbose flag that does not exist. configure documented --personalAccessToken instead of the kebab form the CLI prints. start-ci-run, login, and get sandbox-reports were missing shipped flags. Commands the Nx CLI proxies were shown only in their nx-cloud form. ## Expected Behavior User-facing commands have an entry, verified against the shipped client bundle. Proxied commands show the nx form. conformance links to its own page. Adds --scheduling-constraints, --no-distribution, --targets, --status, --latest-reports-only. Drops --verbose, --runner, deprecated tasksRunnerOptions references, and internal commands. Documents NX_AGENT_NAME and NX_AGENT_INSTANCE_NAME in the environment variable reference. ## Related Issue(s) DOC-606 DOC-607 DOC-608 DOC-609
by Jack Hsu
Succeeded
23.1.x
cd254617 Revert "chore(repo): migrate to nx 23.2.0-beta.7 (#36634)" This reverts commit a3a3dd0d710843e9d09982eaeae14e92f50a9848.
by FrozenPandaz
Failed
36733
4b8ba302 chore(linter): move the eslint import rules to oxlint
by Jason Jean
Succeeded
master
97eb76dc docs(nx-cloud): align github app permission levels with the granted app scopes (#36741) ## Current Behavior The GitHub app permissions page heads the Checks and Workflows sections `(write)` while the app grants read and write on both. The Issues section does not mention label writes, and no conformance page documents `--printConfig`. ## Expected Behavior Heading levels match the scopes the installed app actually grants, label writes are noted, and `--printConfig` is documented. ## Related Issue(s) DOC-620 DOC-622
by Jack Hsu
Succeeded
master
6cafe408 docs(misc): refresh stale node and yarn versions in knowledge base examples (#36740) ## Current Behavior Knowledge base examples target EOL Node 18 and Node 21, present `yarn@3.6.1` as the current output of `yarn set version stable`, and advertise a superseded Nx major in the installation check. ## Expected Behavior Versions match the supported lines in the Nx 23 compatibility table, and the yarn snippet is genericized so it does not rot again. ## Related Issue(s) DOC-623 DOC-624 DOC-625 DOC-626
by Jack Hsu
Succeeded
master
bbe4e8c4 docs(nx-cloud): update checkout action examples and document apply-locally syntax (#36739) ## Current Behavior Three pages pin `actions/checkout` one or two majors behind the sitewide `@v7` baseline, and the self-healing CI page points at the Apply Locally button without ever giving the command syntax. ## Expected Behavior All checkout examples are on `@v7`, and the `nx-cloud apply-locally <fix-identifier>` syntax is stated inline. ## Related Issue(s) DOC-618 DOC-619 DOC-621
by Jack Hsu
Succeeded
master
8ac92bc2 docs(core): document json input type and dependsOn options (#36738) ## Current Behavior The inputs reference omits the `json` input type entirely, and the project configuration reference never mentions `dependsOn[].options`. ## Expected Behavior Both are documented, grounded in the schema, the TypeScript types, and the Rust hasher. ## Related Issue(s) DOC-614 DOC-617
by Jack Hsu
Succeeded
master
33314e88 docs(misc): correct nx.json and environment variable reference (#36737) ## Current Behavior The nx.json and environment variable reference pages name a property that does not exist (`encryptionKey`), document `captureStderr`, `skipNxCache`, and `selectivelyHashTsConfig` as root properties when they are only read under `tasksRunnerOptions`, and state the wrong default for `release.releaseTag.requireSemver`. `NX_RUNNER` is described as functional but is never read, and two live variables have no rows. ## Expected Behavior Property names, nesting, and defaults match the source. `NX_RUNNER` is marked as no longer read, and `NX_MULTI_MAJOR_MODE` and `NX_PROJECT_GRAPH_CACHE_DIRECTORY` are documented. ## Related Issue(s) DOC-610 DOC-611 DOC-612 DOC-613 DOC-615 DOC-616
by Jack Hsu
Failed
run/nx-vite-typecheck-36744
77b5439e fix(core): apply package.json updates unblocked by later package groups (#36636) ## Current Behavior `nx migrate` evaluates each `packageJsonUpdates` group's `requires` and `incompatibleWith` gates once, in package group order. A group held by its gate is never reconsidered, so an update whose gate is only satisfied by a package staged later in the same run is dropped. Reordering the groups does not solve it. The constraint graph between them has a genuine cycle, so a topological sort detects it and falls back to declared order, which is the current behavior. The miss is not recoverable on a later run either, because `filterPackageJsonUpdates` drops any group keyed below the installed owner version. A workspace that lands on a prerelease recovers on its next run, but one that lands on a stable release strands the update for good. ## Expected Behavior Held groups are re-evaluated until no further group applies, so an update whose gate is satisfied by a package staged later in the run still lands. ## Implementation Details Held groups are kept in a keyed pending set rather than discarded when the pass ends, and the gate-and-apply body of `buildPackageJsonUpdates` moved into a helper guarded by an applied-key set so a group applies at most once. After the initial pass the helper re-runs over the held entries until nothing further applies, recursing into newly staged packages so the fixed point spans the collection recursion. Termination is bounded by the applied set, which only grows. Staged versions now route through `addPackageUpdate`, so a group accepted in a later iteration cannot lower a version another group already staged. That is load-bearing: applying a group outside its declared ladder order would otherwise let an older rung overwrite a newer one. The interactive prompt needed no change. A gate-held group never consumed its prompt, a declined group stays declined through `promptAnswers`, and an accepted group is skipped by the applied-key set. ## Blast radius The old and new `Migrator` were both run over the repo's real `packages/*/migrations.json` across 10 workspace profiles (Angular 19/20/21, React + Vite on nx 21/22/23, Next, Vue/Nuxt, React Native/Expo, module federation with rspack). All 10 produce identical package updates: nothing added, changed, removed, or downgraded. Five of them genuinely reach the re-evaluation loop, so the comparison is not vacuous, and the only group newly accepted on current metadata is `@nx/vite`'s `22.2.0` rung, an obsolete step that yields no output difference because the higher staged versions win. Both new tests were checked against a copy of `master`'s `migrate.ts` and fail there. ## Related Issue(s) NXC-4788  --- <p><a href="https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/nxc-4788-87eab713">View Polygraph session ↗</a></p>  --------- Co-authored-by: FrozenPandaz <jasonjean1993@gmail.com>
by Leosvel Pé...
Succeeded
36693
8ad3d438 fix(gradle): pass the task to a dependsOn closure, and test the path splitting Two defects found reviewing the branch. A Groovy `dependsOn { … }` stores a `groovy.lang.Closure`, which implements `GroovyCallable` and so is a `Callable`. It matched the Callable arm and was invoked with no argument, while Gradle calls it with the task — so any closure using its parameter threw, was swallowed, and lost its edge. Closures are now handled ahead of Callable and receive the task. Expanding `dependsOn` also invokes user closures, and several call sites per task need that expansion, so it is memoized rather than recomputed — previously a closure could run once per caller. `resolvePathDeps` had no effective coverage: both tests passed against an implementation returning nothing, one via a short-circuiting `||` and the other vacuously. Replacing its body with `emptyList()` left the whole suite green. The tests now build real child projects and assert the resolved pairs, and both new tests fail when their fix is reverted.
by FrozenPandaz