pipwave-ekyc-uikit 3.8.0-beta.1 → 3.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,33 @@
1
+ # Slack drafts: pipwave-ekyc-uikit 3.8.0-beta.1 (beta to staging)
2
+
3
+ All three posts below were sent after approval.
4
+
5
+ ## #qa-staging-release: post 1 (hosted page) - SENT
6
+
7
+ https://hydron-holdings.slack.com/archives/C06C8D76203/p1789447764406379
8
+
9
+ Deploying pipwave Hosted Page
10
+ • [sc-359303] Install pipwave-ekyc-uikit 3.8.0-beta.1 @Che Chin
11
+
12
+ ---
13
+
14
+ ## #qa-staging-release: post 2 (demo) - SENT
15
+
16
+ https://hydron-holdings.slack.com/archives/C06C8D76203/p1789447769540399
17
+
18
+ Deploying pipwave Demo
19
+ • [sc-359303] Submit ID, selfie and CC images via presigned S3 upload instead of base64 @Jia Chong Ong
20
+
21
+ ---
22
+
23
+ ## Testing-request DM: group DM C0BR1KT3QQ7 (Che Chin, Jia Chong Ong, Jason (JunJie) Teo), tagging Jia Chong - SENT
24
+
25
+ https://hydron-holdings.slack.com/archives/C0BR1KT3QQ7/p1789447948968769
26
+
27
+ Hi Jia Chong, pipwave-ekyc-uikit 3.8.0-beta.1 is out on staging.
28
+
29
+ 1. What's in it: sc-359303 only, the presigned S3 upload for ID, selfie and credit card images. It pulls in pipwave-ekyc-sdk 2.3.0-beta.1 transitively, so that prerelease is on staging too. Nothing else landed this round: sc-354878 (selfie dialogs, MR !104) is still open and is not in this build.
30
+ 2. Where to test: the staging hosted page and the demo site (demo 1.6.42). Both are already deployed.
31
+ 3. What to focus on: run a full ID + selfie session and a credit card session, and confirm the images actually land in S3 and the submit goes through with the *_uri fields rather than base64. Worth checking back-side capture (the back_doc fields are only sent when a back image was taken), the cropped and full-frame pair for each image, and the failure path: a failed upload should surface the existing error and retake/retry dialogs, not a new one. Since imagesHelper and the submit flows are shared, the proof of address flow is worth a quick pass too even though it was untouched.
32
+
33
+ Could you help run through this and let me know if anything looks off? Planning to promote this to a stable 3.8.0 once it's cleared.
@@ -0,0 +1,10 @@
1
+ ## #hello-serverless: pipwave eKYC Web UI Release 3.8 is ready
2
+
3
+ pipwave eKYC Web UI Release 3.8 is ready
4
+ • MR
5
+ https://gitlab.g2g.com/pipwave-frontend/pw-ekyc-web-ui/-/merge_requests/109
6
+ • Release Notes
7
+ https://gitlab.g2g.com/pipwave-frontend/pw-ekyc-web-ui/-/wikis/**Release-3.8-Deployment-Notes#release-38
8
+ cc: @Jia Chong Ong
9
+
10
+ ---
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pipwave-ekyc-uikit",
3
- "version": "3.8.0-beta.1",
3
+ "version": "3.8.0",
4
4
  "description": "",
5
5
  "main": "dist/pw-bundle.js",
6
6
  "module": "dist/pw-bundle.mjs",
@@ -62,7 +62,7 @@
62
62
  "moment": "^2.29.4",
63
63
  "pdfjs-dist": "^4.4.168",
64
64
  "pikaday": "^1.8.2",
65
- "pipwave-ekyc-sdk": "2.3.0-beta.1",
65
+ "pipwave-ekyc-sdk": "2.3.0",
66
66
  "qr-code-styling": "^1.9.2"
67
67
  }
68
68
  }