nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Current execution
Failed
ss-bearer-token-log-e9d15dac
Runs and Agents
Timeline
Beta
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
fix(release): redact the token in the GitHub and GitLab release error output - The API-error output printed `Token Header Data: [object Object]`. It never leaked a token, but it read as a formatting bug and the obvious fix (`JSON.stringify`, as the adjacent `Body:` line does) would have written the bearer token to CI logs. - Print the header name with the value redacted instead, or `none` when no token was configured, so a failing release still shows which credential source was used. - Add specs for both clients asserting the token never appears in the output. Flagged by the Socket gptSecurity analysis of nx 23.1.2.
nx-cloud record -- nx sync:check
⌘K
Succeeded
nx-cloud record -- nx sync:check
Click to copy
Linux
4 CPU cores
294433cc
36852
GitHub
Nx
Workspace