feat(nx-cloud): set up nx workspace#1
Merged
ThePlenkov merged 1 commit intomainfrom Aug 15, 2025
Merged
Conversation
This commit sets up Nx Cloud for your Nx workspace, enabling distributed caching and the Nx Cloud GitHub integration for fast CI and improved developer experience. You can access your Nx Cloud workspace by going to https://cloud.nx.app/orgs/671be43c6487b4030d8b8333/workspaces/689f2325a9081eb8eb04b58d **Note:** This commit attempts to maintain formatting of the nx.json file, however you may need to correct formatting by running an nx format command and committing the changes.
Contributor
|
| Command | Status | Duration | Result |
|---|---|---|---|
nx affected -t lint test build e2e-ci |
❌ Failed | 1m 2s | View ↗ |
nx-cloud record -- nx format:check |
✅ Succeeded | 1s | View ↗ |
☁️ Nx Cloud last updated this comment at 2025-08-15 12:10:18 UTC
ThePlenkov
added a commit
to ThePlenkov/js
that referenced
this pull request
Feb 27, 2026
feat(nx-cloud): set up nx workspace
ThePlenkov
added a commit
that referenced
this pull request
Apr 20, 2026
Two fixes at the source after the first real npmjs publish attempt: 1. nx.json: flip cli.packageManager from "bun" to "npm". Nx 22's @nx/js:release-publish honours that and was invoking `bun publish`, which has no OIDC trusted-publishing support — it just errored with `missing authentication` for every one of the 30 packages. Confirmed via deepwiki: detectPackageManager() in nx reads cli.packageManager before any lockfile-based fallback, so this is the canonical knob. The monorepo still uses bun for `bun install`, lockfile, and local dev — nx's cli.packageManager only controls what nx itself invokes (nx add, nx release publish, etc.). 2. .github/workflows/publish.yml: upgrade npm to ^11.10.0 before `nx release publish`. Node 24 ships with npm 11.0.x; OIDC trusted publishing discovery (no NPM_TOKEN, picks up the GitHub Actions id-token automatically) only landed in npm 11.5.1 and stabilised in 11.10. Without the bump, publishes returned `Not Found - PUT /<pkg>` because npm never attempted the OIDC flow — it treated the request as anonymous and npmjs 404'd it. Drop the previous job-local nx.json patch step (covered by fix #1). The 30 trusted-publisher entries registered via `npm-trust-check --prepare` should now actually be used on the next release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat(nx-cloud): setup nx cloud workspace
This commit sets up Nx Cloud for your Nx workspace, enabling distributed caching and the Nx Cloud GitHub integration for fast CI and improved developer experience.
You can access your Nx Cloud workspace by going to
https://cloud.nx.app/orgs/671be43c6487b4030d8b8333/workspaces/689f2325a9081eb8eb04b58d
Note: This commit attempts to maintain formatting of the nx.json file, however you may need to correct formatting by running an nx format command and committing the changes.