chore: bump @friggframework/* deps to 2.0.0-next.83#97
Merged
Conversation
Pulls in Frigg PR #583 (fix(core): repoint entity credentialId when re-auth produces a different credential) — follow-up to #582. Found via dev validation: re-auth against a different Pipedrive workspace left the entity pointing at the prior credential row while the freshly-issued tokens landed on a different credential. fix repoints existing entity's credentialId to the just-upserted credential when they differ. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump
@friggframework/*deps from2.0.0-next.82→2.0.0-next.83. Pulls in Frigg PR #583 — follow-up to next.82's #582.Why
Validating next.82 in dev surfaced a second bug: when a user re-authenticates against a different workspace/account of the same provider (the user has multiple Pipedrive workspaces and authenticates against them interchangeably),
upsertCredentialmatches a different credential row than the entity was previously linked to.Concrete sequence observed in dev (Pipedrive integration 136, user 16):
23384438).24952048→ matched existing credential 188 (a separate cred for that workspace).{credentialId: 188, entityId: 159}, but the DB-level FK on entity 159 still pointed to credential 166.In other words, the "fix" in next.82 wrote the new tokens to the right credential row, but the entity wasn't repointed to use them.
What's in next.83
findOrCreateEntitynow repointsexistingEntity.credentialIdto the just-upsertedcredentialIdviamoduleRepository.updateEntitywhenever they differ.[Frigg] Repointing entity X credentialId Y -> Z after re-authwhenever it fires — surfaces this scenario in CloudWatch.Test plan
npm installresolves cleanly with the new versionsRepointing entity ...log line appears AND that the entity'scredentialIdforeign key in the DB updates to point at the freshly-persisted credentialRepointinglog line (no-op path)🤖 Generated with Claude Code