Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Failed
master
7f4a8eaf fix(repo): remove duplicate permissions block in publish workflow (#32868) ## Current Behavior The publish workflow has a duplicate `permissions` block incorrectly nested under a GitHub script action step, which causes a syntax error in the GitHub Actions workflow. ## Expected Behavior The workflow should run without syntax errors. The `permissions` block should only be defined at the job level, not within individual steps. ## Related Issue(s) This fixes a GitHub Actions workflow syntax issue where permissions were incorrectly nested under a step action. The `pull-requests: write` permission is already correctly defined at the job level (lines 510-513), so the duplicated permissions block under the step was unnecessary and causing errors. 🤖 Generated with [Claude Code](https://claude.ai/code)
2 days ago by pull[bot]
Failed
master
ad032add fix(core): project graph creation processes project dependencies correctly (#32784) ## Current Behavior The project graph build process incorrectly handles dependencies when workspace projects have different versions or are referenced via specific version ranges. This causes several issues: 1. NPM lockfile parser crashes when encountering symlinked nested dependencies in workspaces (which don't have versions) 2. Package.json dependencies that reference workspace projects with specific versions (e.g., "proj4": "1.0.0" when workspace has "version": "2.0.0") incorrectly resolve to the workspace project instead of the installed npm package 3. Version ranges and file references to workspace projects are not properly validated ## Expected Behavior The dependency resolution should: - Handle symlinked workspace packages in npm lockfiles without crashing - Correctly differentiate between workspace projects and npm packages when specific versions are referenced - Properly validate version ranges against workspace package versions using semver - Support file references (e.g., "file:../proj6") for workspace dependencies - Only resolve to workspace projects when the version constraint is satisfied or when using wildcards ## Notes This has inadvertently caused issues when calculating which manifest files need to be updated in the JSVersionActions / Nx Release for Npm Packages ## Related Issues Fixes #31454 --------- Co-authored-by: FrozenPandaz <jasonjean1993@gmail.com>
2 days ago by pull[bot]
Succeeded
master
6c109d2c fix(core): add env var to disable fetching migration metadata from registry (#32850) Add a new `NX_MIGRATE_SKIP_REGISTRY_FETCH` environment variable to opt out of fetching package versions and migrations metadata from the registry and instead, use package installation to get the information.
2 days ago by pull[bot]
Succeeded
master
5ea2e47a fix(core): display prettier valid errors (#32771)      ## Current Behavior When running `nx format:check`, if there is an error, it is considered as files not formatted correctly But if Prettier is throwing a real error, it is not diplayed. We just see an empty result without information For example: Format check failing with empty result ``` nx format:check ``` But when running the command, we can see the error: ``` node "/node_modules/prettier/bin/prettier.cjs" --list-different "packages/lib/.spec.swcrc" packages/lib/.spec.swcrc [error] No parser could be inferred for file "/packages/lib/.spec.swcrc". ``` ## Expected Behavior I should see the prettier error to understand why it is failing ## Related Issue(s)  Fixes #
2 days ago by pull[bot]
Succeeded
master
b6d5f386 fix(gradle): skip targets on Netlify since the Java version is too old (#32852) Building on Netlify fails. ``` 3:03:48 PM: FAILURE: Build failed with an exception. 3:03:48 PM: * What went wrong: 3:03:48 PM: A problem occurred configuring root project 'nx'. 3:03:48 PM: > Could not resolve all artifacts for configuration 'classpath'. 3:03:48 PM: > Could not resolve dev.nx.gradle:project-graph:0.1.7. 3:03:48 PM: Required by: 3:03:48 PM: root project : > dev.nx.gradle.project-graph:dev.nx.gradle.project-graph.gradle.plugin:0.1.7 3:03:48 PM: > Dependency requires at least JVM runtime version 17. This build uses a Java 8 JVM. 3:03:48 PM: > Could not resolve com.ncorti.ktfmt.gradle:plugin:0.24.0. 3:03:48 PM: Required by: 3:03:48 PM: root project : > com.ncorti.ktfmt.gradle:com.ncorti.ktfmt.gradle.gradle.plugin:0.24.0 3:03:48 PM: > Dependency requires at least JVM runtime version 17. This build uses a Java 8 JVM. 3:03:48 PM: * Try: 3:03:48 PM: > Run this build using a Java 17 or newer JVM. 3:03:48 PM: > Run with --stacktrace option to get the stack trace. 3:03:48 PM: > Run with --debug option to get more log output. 3:03:48 PM: > Run with --scan to get full insights. 3:03:48 PM: > Get more help at https://help.gradle.org. 3:03:48 PM: BUILD FAILED in 30s ``` ## Current Behavior Gradle plugin needs Java 17, but Netlify uses 8. ## Expected Behavior Skip targets on Netlify just like on Vercel. ## Related Issue(s)  Fixes #NXC-3175
3 days ago by pull[bot]
Succeeded
master
6480d3d6 chore(repo): update nx to 21.6.1-beta.4 (#32848) Updating Nx from 21.6.1-beta.3 to 21.6.1-beta.4
3 days ago by pull[bot]
Succeeded
master
c0ad4843 docs(nx-dev): small docs cleanup (#32822) - add prettier overrides for mdoc files to be treaded as markdown (along with running format) - update links to nx-commands refs to use correct header links - fix link on quickstart page to point to CI feature overview
4 days ago by pull[bot]
Succeeded
master
c9aa288d fix(core): prevent terminal pane scrolling on tasks list events (#32818) ## Current Behavior The TUI had two distinct scrolling issues: 1. **Tasks List Events Scrolling**: Any tasks list event (scrolling, arrow keys, task status changes) would cause the terminal pane to scroll down exactly 8 lines in two batches of 4 - one immediately and another after ~200ms delay. 2. **New Task Initial Positioning**: When navigating to a task for the first time, the task output would render 4 lines above the bottom position, then automatically scroll to the correct bottom position after a short delay. ## Expected Behavior 1. Tasks list navigation and events should not cause any scrolling in the terminal pane 2. Task output should appear correctly positioned at the bottom from the first render without any delayed scroll adjustments --- ## Technical Details ### Root Cause **Issue 1 - Tasks List Events Scrolling (8 lines)** - Task list events triggered `debounce_pty_resize()` calls - This caused immediate resize + 200ms delayed resize - Each resize applied 4-line scroll adjustments due to dimension recalculations - Result: 8 lines total scroll (4 immediate + 4 delayed) **Issue 2 - New Task Initial Positioning (4 lines)** - New PTY instances created with default dimensions (24×80) - Terminal panes had different calculated dimensions (e.g., 22×137) - Viewport height mismatch caused content to appear 4 lines up from bottom - Delayed resize would correct positioning, causing visible scroll-to-bottom ### Solution **Architectural Improvement**: Migrated from individual dimension fields to shared dimensions using `Arc<RwLock<(u16, u16)>>` to ensure consistency across all PTY references. **Issue 1 Fix**: Removed redundant `debounce_pty_resize()` calls during task navigation events, eliminating the double-resize pattern. **Issue 2 Fix**: Added immediate dimension correction in `render_terminal_pane_internal()` to ensure correct positioning from first render. ### Changes Made - **pty.rs**: Replaced individual `rows`/`cols` fields with shared `dimensions: Arc<RwLock<(u16, u16)>>` - **app.rs**: Added immediate resize in `render_terminal_pane_internal()` for correct initial positioning - **app.rs**: Removed redundant `debounce_pty_resize()` calls during task navigation events - Improved error handling and eliminated potential deadlock risks in resize operations ### Performance Impact - Eliminated double-resize pattern during navigation (~67% reduction in resize operations) - No more visible scrolling delays or positioning issues - Maintained all layout change functionality while removing unnecessary operations
4 days ago by pull[bot]
Failed
master
57c5c6ac docs(nx-dev): document playwright output merging w/ atomizer (#32830) fixes: DOC-208 --------- Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
4 days ago by pull[bot]
Failed
master
146f5774 chore(nx-dev): update active contributors (#32831) Increased the maximum number of active contributors mentioned in the pricing description from 30 to 50 in the `Pricing` component (`nx-dev/ui-cloud/src/lib/pricing.tsx`).
5 days ago by pull[bot]
Failed
master
9e47fed9 docs(nx-dev): mention saml is ent feature in google auth doc (#32823) fixes: DOC-228
5 days ago by pull[bot]
Succeeded
master
79ac44d0 fix(misc): remove unnecessary `bust` property from plugin hashes (#32807) Remove the manually maintained and unnecessary `bust` property from plugin hashes.
5 days ago by pull[bot]
Failed
master
ec07bfb8 docs(core): add changelogs for 21.4 and 21.5 (#32774) https://nx-dev-git-philip-september-changelogs-nrwl.vercel.app/changelog
6 days ago by pull[bot]
Succeeded
master
dbcafa0e docs(nx-dev): sync content from docs/ into astro docs (#32812) - add missing NxModuleFederationPlugin page
6 days ago by pull[bot]
Failed
master
dbcafa0e docs(nx-dev): sync content from docs/ into astro docs (#32812) - add missing NxModuleFederationPlugin page
6 days ago by pull[bot]
Failed
master
f1b00ca6 fix(nx-dev): fix client-side redirect issue for OSS cloud plan form
6 days ago by pull[bot]
Failed
master
6cf1d7a3 chore(repo): set up AGENTS.md with recommended rules (#32782)      ## Current Behavior only claude has dedicated setup in the nx repo. ## Expected Behavior Claude, Gemini and things that use AGENTS.md have dedicated setup in the nx repo.
8 days ago by pull[bot]
Failed
master
6cf1d7a3 chore(repo): set up AGENTS.md with recommended rules (#32782)      ## Current Behavior only claude has dedicated setup in the nx repo. ## Expected Behavior Claude, Gemini and things that use AGENTS.md have dedicated setup in the nx repo.
8 days ago by pull[bot]
Failed
master
369f1624 docs(nx-dev): fix AI chat streaming parse error by pinning ai package to v3.0.19 (#32792) The AI chat on nx.dev shows an error 'Failed to parse stream string. No separator found.' after successfully receiving a response from the API. The AI chat should work without showing streaming parse errors after successful responses. Also fixed tailwind pruning by including `feature-ai` in the globs to check. https://github.com/user-attachments/assets/2517d856-7a45-48f4-b71b-885f3714fb44 Fixes DOC-216
9 days ago by pull[bot]
Failed
master
4d57e62c chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`.
9 days ago by pull[bot]