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 15s

28 CI pipeline executions

Computation time saved

15h 51m

Cache hit rate

84%

Protect cache integrity with sandboxing

Time to Green

2h 31m

Was 4h 42m, improved by 46%

Succeeded
850
dda7cf35 chore(protect): mark signals SDK migration as breaking
by Ryan Bas
R
Succeeded
850
0a8df4c0 feat(protect): migrate to npm @ping-identity/pingone-signals-web-sdk Replaces bundled signals-sdk.js with the official npm package @ping-identity/pingone-signals-web-sdk@^5.6.11. Breaking changes: - Removed Window._pingOneSignals declaration (now provided by SDK types) - Test mocks changed from ./signals-sdk.js to the npm package Changes: - Import SDK default export for type-safe access - Remove local signals-sdk.js bundle (17k lines) - Update tsconfig.lib.json: enable skipLibCheck, remove deleted file from include - Update sideEffects in package.json to false (npm package handles this) - Use optional chaining instead of non-null assertions for SDK calls
by Ryan Bas
R