Skip to content

fix(repo): unblock Windows and FreeBSD publish builds after @nx/maven self-build - #37379

Open
FrozenPandaz wants to merge 3 commits into
fix/ultracache-native-node-readsfrom
fix/publish-maven-windows-freebsd
Open

FrozenPandaz wants to merge 3 commits into
fix/ultracache-native-node-readsfrom
fix/publish-maven-windows-freebsd

Conversation

@FrozenPandaz

@FrozenPandaz FrozenPandaz commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Current Behavior

Since #33412 added asdf:mise-plugins/mise-maven to mise.toml and the @nx/maven plugin to nx.json, the publish workflow fails on:

  • Windows (x64, arm64): mise can't install asdf plugins (bash scripts) on Windows, so the "Setup dev tools with mise" step fails. Past that, the published nx-maven-plugin reports project roots with backslashes, so the project graph fails with duplicate projects.
  • FreeBSD: the @nx/maven plugin runs ./mvnw while building the project graph, and the VM has no JDK (The java(1) command does not exist in PATH nor is JAVA_HOME set).

Canary has been red since 2026-10-07, and 24.0.0-beta.0 failed on Windows.

Expected Behavior

  • The asdf Maven plugin only installs on Linux and macOS (same pattern as dotnet).
  • The Windows and FreeBSD publish builds set NX_MAVEN_DISABLE=true. They only build native bindings, so they don't need the Maven graph. FreeBSD already disables Gradle and .NET this way; installing a JDK there instead left under 500 MB free after the build.

The backslash bug itself is fixed in #37383. The Windows NX_MAVEN_DISABLE can be removed once that ships in a released nx-maven-plugin and the root pom.xml is bumped.

Verified with a publish dry-run: all build jobs pass (the Publish job is blocked by the npm-registry environment rule for non-master branches, as expected).

Related Issue(s)

N/A — CI breakage introduced by #33412.


View Polygraph session ↗

@netlify

netlify Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for nx-docs ready!

Name Link
🔨 Latest commit dd74ab0
🔍 Latest deploy log https://app.netlify.com/projects/nx-docs/deploys/6acc0020d2d2e700083e5357
😎 Deploy Preview https://deploy-preview-37379--nx-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for nx-dev ready!

Name Link
🔨 Latest commit dd74ab0
🔍 Latest deploy log https://app.netlify.com/projects/nx-dev/deploys/6acc0020847b8c000844027a
😎 Deploy Preview https://deploy-preview-37379--nx-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@nx-cloud

nx-cloud Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

View your CI Pipeline Execution ↗ for commit dd74ab0

Command Status Duration Result
nx affected --targets=lint,oxlint,test,build,e2... ✅ Succeeded 52m 11s View ↗
nx run-many -t check-imports check-lock-files c... ✅ Succeeded 2s View ↗
nx-cloud record -- pnpm nx-cloud conformance:check ✅ Succeeded 37s View ↗
nx build workspace-plugin ✅ Succeeded <1s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded 27s View ↗
nx-cloud record -- nx format:check ✅ Succeeded <1s View ↗

☁️ Nx Cloud last updated this comment at 2026-10-11 22:27:50 UTC

@github-actions

Copy link
Copy Markdown
Contributor

Failed to publish a PR release of this pull request, triggered by @FrozenPandaz.
See the failed workflow run at: https://github.com/nrwl/nx/actions/runs/38016668052

nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

nx-cloud[bot]

This comment was marked as outdated.

@FrozenPandaz
FrozenPandaz marked this pull request as ready for review October 11, 2026 14:54
@FrozenPandaz
FrozenPandaz requested a review from a team as a code owner October 11, 2026 14:54
@FrozenPandaz
FrozenPandaz requested a review from lourw October 11, 2026 14:54
@FrozenPandaz
FrozenPandaz force-pushed the fix/publish-maven-windows-freebsd branch from 6019461 to 30c4708 Compare October 11, 2026 14:55
nx-cloud[bot]

This comment was marked as outdated.

@FrozenPandaz
FrozenPandaz changed the base branch from master to fix/ultracache-native-node-reads October 11, 2026 17:37
@FrozenPandaz
FrozenPandaz added this pull request to stack #37384 October 11, 2026 17:38
@FrozenPandaz
FrozenPandaz force-pushed the fix/publish-maven-windows-freebsd branch from 30c4708 to a703780 Compare October 11, 2026 17:38

@nx-cloud nx-cloud Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nx Cloud has identified a flaky task in your failed CI:

🔂 Since the failure was identified as flaky, we triggered a CI rerun by adding an empty commit to this branch.

Nx Cloud View detailed reasoning in Nx Cloud ↗


🎓 Learn more about Self-Healing CI on nx.dev

… self-build

Skip the asdf Maven plugin on Windows (mvnw.cmd is used instead) and
install a JDK in the FreeBSD VM so mvnw can build the project graph.
The published nx-maven-plugin reports Windows project roots with
backslashes, which breaks the project graph. The native builds don't
need Maven projects.
Installing a JDK for the Maven graph left under 500 MB free after the
build. Disable it like Gradle and .NET instead.
@FrozenPandaz
FrozenPandaz force-pushed the fix/publish-maven-windows-freebsd branch from a703780 to dd74ab0 Compare October 11, 2026 21:31

This branch had an error being deployed

1 failed (outdated) deployment
npm-registry — 1797a209 Deployed Oct 10, 2026 by FrozenPandaz via Publish #2799
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant