Overview - Ping-javascript-sdk

ping-javascript-sdk

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
832ce898 fix(journey-client): create JourneyLoginFailure step, handle Login Failure case * fix(journey-client): create JourneyLoginFailure step, handle Login Failure case * refactor(journey-client): use Either for response parsing in start and next
by Vatsal Parikh
Succeeded
main
832ce898 fix(journey-client): create JourneyLoginFailure step, handle Login Failure case * fix(journey-client): create JourneyLoginFailure step, handle Login Failure case * refactor(journey-client): use Either for response parsing in start and next
by Vatsal Parikh
Succeeded
670
348a6368 refactor(journey-client): use Either for response parsing in start and next
by Vatsal Parikh
Succeeded
670
6a2eea60 refactor(journey-client): use Either for response parsing in start and next
by Vatsal Parikh
Succeeded
682
98f1e5c7 feat(oidc-client): add oidc session check with response type of id_token and none
by Vatsal Parikh
Succeeded
682
e1b4cd2f feat(oidc-client): add oidc session check with response type of id_token and none
by Vatsal Parikh
Failed
682
Fix ready→
ed9b2941 feat(oidc-client): add oidc session check with response type of id_token and none
by Vatsal Parikh
Failed
682
e899781f feat(oidc-client): add oidc session check with response type of id_token and none
by Vatsal Parikh
Succeeded
670
7bac6f35 refactor(journey-client): use Either for response parsing in start and next
by Vatsal Parikh
Failed
670
Fix ready→
e5badbe4 refactor(journey-client): use Either for response parsing in start and next
by Vatsal Parikh
Succeeded
574
091667c2 fix(journey-client): create JourneyLoginFailure step, handle Login Failure case
by Vatsal Parikh
Succeeded
574
c4672169 fix(journey-client): use Effect Either to handle journey response in start and next
by Vatsal Parikh
Succeeded
574
0eb8a3bc fix(journey-client): use Effect Either to handle journey response in start and next
by Vatsal Parikh
Succeeded
574
3ac02ea5 fix(journey-client): use Effect Either to handle journey response in start and next
by Vatsal Parikh
Succeeded
test/pin-npm-10
49d1f347 test(ci): drop registry-url from setup-node so OIDC wins over placeholder token When setup-node is given registry-url, it writes an .npmrc with _authToken=${NODE_AUTH_TOKEN} and exports an empty NODE_AUTH_TOKEN. Recent npm CLI versions prefer that placeholder over OIDC trusted publishing, so the publish PUT is rejected as 404 even though provenance signing succeeds. The workspace-level .npmrc already sets the registry, so removing this is safe.
by Vatsal Parikh
Succeeded
test/pin-npm-10
f37cfd94 test(ci): revert npm@10 pin to isolate provenance test Reverts the npm version pin so the next dispatch tests NPM_CONFIG_PROVENANCE in isolation. Pinning npm did not fix the 404 in the previous run, and keeping it would muddy the result.
by Vatsal Parikh
Succeeded
test/pin-npm-10
96544017 test(ci): pin npm to v10 to verify OIDC publish regression Reproduces a beta publish from this branch with npm 10.x to test whether npm 11.x is responsible for the recent E404 / OIDC failures on the snapshot publish step.
by Vatsal Parikh
Succeeded
main
5f55b08b docs(journey-client): fix FRDevice mapping, export PolicyParams, improve migration guide (#630)
by Vatsal Parikh
Succeeded
630
d60e979e docs(journey-client): fix FRDevice mapping, export PolicyParams, improve migration guide
by Vatsal Parikh
Succeeded
630
d60e979e docs(journey-client): fix FRDevice mapping, export PolicyParams, improve migration guide
by Vatsal Parikh