Overview - Ping-javascript-sdk

ping-javascript-sdkWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

ping-javascript-sdk

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

ping-javascript-sdkWorkspace

Average execution time

3m 8s

43 CI pipeline executions

Computation time saved

20h 16m

Cache hit rate

88%

Protect cache integrity with sandboxing

Time to Green

4h 25m

Was 6h 25m, improved by 31%

Succeeded
748
2ff7b6a8 fix(oidc-client): enforce prompt=none on background-only authorize paths - Restore prompt='none' injection in createAuthorizeUrlµ (background/silent dispatch path only — iframe and fetch, never redirect) - Remove erroneous prompt='none' injection from token.get() shared path, which was causing login_required/interaction_required on redirect flows - Strip prompt from fallback redirectUrl in buildAuthorizeRedirectUrlµ so interactive redirect still works after a failed silent auth - Skip flaky PAR redirect e2e test (external ForgeBlocks AM timeout) - Bump pnpm.overrides for CVE fixes: fast-uri, brace-expansion, undici, nanoid, postcss
by Ryan Bas
Canceled
748
976a3bc7 fix(oidc-client): enforce prompt=none on background-only authorize paths - Restore prompt='none' injection in createAuthorizeUrlµ (background/silent dispatch path only — iframe and fetch, never redirect) - Remove erroneous prompt='none' injection from token.get() shared path, which was causing login_required/interaction_required on redirect flows - Strip prompt from fallback redirectUrl in buildAuthorizeRedirectUrlµ so interactive redirect still works after a failed silent auth - Skip flaky PAR redirect e2e test (external ForgeBlocks AM timeout) - Bump pnpm.overrides for CVE fixes: fast-uri, brace-expansion, undici, nanoid, postcss
by Ryan Bas
Succeeded
748
ade17d67 fix(oidc-client): always pass prompt=none on background authorize calls
by Ryan Bas
Succeeded
748
2780e7a0 fix(oidc-client): always pass prompt=none on background authorize calls
by Ryan Bas
Succeeded
748
44c35f83 fix(oidc-client): enforce prompt=none on background-only authorize paths - Restore prompt='none' injection in createAuthorizeUrlµ (background/silent dispatch path only — iframe and fetch, never redirect) - Remove erroneous prompt='none' injection from token.get() shared path, which was causing login_required/interaction_required on redirect flows - Strip prompt from fallback redirectUrl in buildAuthorizeRedirectUrlµ so interactive redirect still works after a failed silent auth - Skip flaky PAR redirect e2e test (external ForgeBlocks AM timeout) - Bump pnpm.overrides for CVE fixes: fast-uri, brace-expansion, undici, nanoid, postcss
by Ryan Bas
Succeeded
748
600589f7 fix(oidc-client): strip prompt from fallback redirectUrl on background auth failure
by Ryan Bas
Failed
748
Environment issue→
600589f7 fix(oidc-client): strip prompt from fallback redirectUrl on background auth failure
by Ryan Bas
Failed
748
15c91924 fix(oidc-client): restore prompt=none to background-only path The refactor incorrectly injected prompt=none into token.get()'s renewal pipeline, which is shared with redirect login flows. This caused login_required/interaction_required errors on interactive flows. Revert the injection from token.get() and restore prompt=none inside createAuthorizeUrlµ, which is only called on the background/silent dispatch path (iframe/fetch).
by Ryan Bas
Failed
748
15c91924 fix(oidc-client): restore prompt=none to background-only path The refactor incorrectly injected prompt=none into token.get()'s renewal pipeline, which is shared with redirect login flows. This caused login_required/interaction_required errors on interactive flows. Revert the injection from token.get() and restore prompt=none inside createAuthorizeUrlµ, which is only called on the background/silent dispatch path (iframe/fetch).
by Ryan Bas
Failed
748
Environment issue→
15c91924 fix(oidc-client): restore prompt=none to background-only path The refactor incorrectly injected prompt=none into token.get()'s renewal pipeline, which is shared with redirect login flows. This caused login_required/interaction_required errors on interactive flows. Revert the injection from token.get() and restore prompt=none inside createAuthorizeUrlµ, which is only called on the background/silent dispatch path (iframe/fetch).
by Ryan Bas
Failed
748
Environment issue→
08edab1a fix(oidc-client): always pass prompt=none on background authorize calls - bgOptions unconditionally set to spread options with prompt:none - add regression test for background() called with no arguments
by Ryan Bas
Failed
748
Environment issue→
b361bfe2 fix(oidc-client): always pass prompt=none on background authorize calls - bgOptions unconditionally set to spread options with prompt:none - add regression test for background() called with no arguments
by Ryan Bas
Failed
748
Environment issue→
2f4a9fe1 fix(oidc-client): always pass prompt=none on background authorize calls
by Ryan Bas
Succeeded
748
95b4b267 fix(oidc-client): always pass prompt=none on background authorize calls
by Ryan Bas
Succeeded
748
15f8987e fix(oidc-client): always pass prompt=none on background authorize calls Background authorize flows (both standard and PAR) must include prompt=none so the authorization server does not prompt the user for interaction. The standard flow already enforced this inside createAuthorizeUrlµ; the PAR flow was not injecting it, meaning any background PAR call without an explicit prompt option would silently omit the required parameter.
by Ryan Bas