nxNx
GitHubNxWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionFailed
      ss-bearer-token-log-e9d15dac
    • Runs and Agents
    • TimelineBeta
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runFailed
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
  • Sign in
    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 affected --targets=lint,oxlint,test,build,e2e,e2e-ci,format-native,lint-native,gradle:build-ci,vale,run,validate-example
Failed
read-write access token used
294433cc36852
<1%

Failed tasks

1 of 729 failed.

1%

Potential flaky tasks

9 of 729 tasks retried.

17%

Cache hits

126 of 729 tasks used cache.

97%

Distribution saved time

53m 34s instead of 31h 52m 42s.

Resource usage is collected per agent

Run-level metrics are not available for distributed runs. View CPU and memory in this CI pipeline execution’s Analysis page.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubNxWorkspace