Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/bump-frigg-next-82-oauth-token-persist.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'quo-integrations-frigg': patch
---

Bump `@friggframework/*` deps from `2.0.0-next.81` → `2.0.0-next.82`. Pulls in Frigg PR #582 (`fix(core): explicitly persist tokens on OAuth2 re-auth`), which fixes a silent token-persistence bug in `ProcessAuthorizationCallback` that left re-authenticated entities with stale OAuth tokens. Diagnosed against Pipedrive in prod: re-installs created new Integration rows pointing at a 3-month-old credential whose tokens had been retired by Pipedrive during the OAuth flow but never replaced in our DB; downstream webhook setup then 401'd and flipped integrations to `ERROR`. Fix bootstraps the Module with the existing entity on re-auth, explicitly upserts the credential after `getToken` (no longer relying solely on the `DLGT_TOKEN_UPDATE` notification chain), and adds diagnostic logging to `/api/authorize` and `processAuthorizationCallback.execute()` so future re-auth bugs surface in CloudWatch instead of running silently. Affected prod integrations: 12378, 12379 (Pipedrive, user 10).
Loading
Loading