Skip to content

Codex/fix atlas authorization expiry - #260

Open
iblmediaconsultancy wants to merge 42 commits into
trycompai:mainfrom
iblmediaconsultancy:codex/fix-atlas-authorization-expiry
Open

iblmediaconsultancy wants to merge 42 commits into
trycompai:mainfrom
iblmediaconsultancy:codex/fix-atlas-authorization-expiry

Conversation

@iblmediaconsultancy

Copy link
Copy Markdown

No description provided.

iblmediaconsultancy and others added 30 commits September 28, 2026 00:47
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.
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.
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
@vercel

vercel Bot commented Oct 26, 2026

Copy link
Copy Markdown

@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.

@tripwire-sh tripwire-sh Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

View on Tripwire

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.

@github-actions
github-actions Bot changed the base branch from release to main October 26, 2026 17:14
@github-actions

Copy link
Copy Markdown
Contributor

Retargeted this onto main.

release is the default branch so that a plain clone runs the last tagged release, but nothing merges into it — it is fast-forwarded onto the tag by the Release workflow and that is all. Changes go to main, and reach release when a release is cut.

Nothing is wrong with your branch. If the diff now shows commits that are already on main, rebase and force-push:

git fetch origin main
git rebase origin/main
git push --force-with-lease

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant