Repository navigation
Codex/fix atlas authorization expiry - #260
iblmediaconsultancy wants to merge 42 commits into
Conversation
Preserve conversation-history guards, fail-closed execution checks, quota rollover inheritance, atomic reservations, failure release, and confirmed-send accounting.
Require stable exact recipient resolution before first-message history checks and preserve historical no-note first-touch lineage.
Release 1.5.3.
Persist verified opaque member IDs and prove LinkedIn slug equivalence across queue and execution.
Release LinkedIn profile/member identity equivalence fix.
Scope first-touch history checks to resolved LinkedIn composer surfaces
chore(main): release 1.5.5
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Harden profile identity and defer conversation matching until target composer resolution.
Release 1.5.7.
Preserve fail-closed identity matching while excluding the exact non-person LinkedIn heading.
Release metadata for LinkedIn profile identity heading fix.
…h-recovery fix(atlas): restore authenticated email authorization flow
…hes--main--components--crm chore(main): release 1.5.9
* fix(api): route LinkedIn replies through stored conversation * fix(api): normalize encoded LinkedIn thread keys * fix(ci): bootstrap workspace before fresh migration replay * fix(db): use the pinned Prisma CLI for fresh replay * fix(ci): resolve Prisma config in migration bootstrap
|
@iblmediaconsultancy is attempting to deploy a commit to the Comp AI - PoC Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
@iblmediaconsultancy, Tripwire blocked this change request.
- Honeypot paths: It changes a protected file. Undo your change to that file.
- Max files changed: It changes 300 files. Split it into smaller change requests.
- Max lines changed: Lines added is 7004.
- Require that target branch is release: Target branch is main.
How do I fix this?
Push a commit that fixes the problems. Tripwire checks every push.
If you think this is wrong, say so in a comment. A maintainer will decide.
|
Retargeted this onto
Nothing is wrong with your branch. If the diff now shows commits that are already on git fetch origin main
git rebase origin/main
git push --force-with-lease |

No description provided.