Repository navigation
Conversation
Signed-off-by: reevesc88 <calum@ai1auslutions.com>
|
@reevesc88 is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Signed-off-by: reevesc88 <calum@ai1auslutions.com>
|
Verified final head: 2cc4739. Both commits have Signed-off-by trailers.
The only remaining failed check is Vercel's preview authorization. Its status explicitly says authorization is required to deploy. The connected account's request to the owning Vercel team returned 403, so a member of rohitg00's Vercel team must authorize this deployment from the Vercel check. The old #1647 CI failures were approval expirations; those historical runs did not execute tests. No history was rewritten, no source files were deleted, and the superseded unsigned branch remains preserved. #1722 is closed and points to this signed-off replacement. The seven skipped local tests and standalone live-server integration were not executed locally; the hosted release gate exercised its configured live/package checks. |
|
@rohitg00 The code and release checks on head The only remaining red status is Vercel's contributor authorization. Could a member of the owning Vercel team authorize this preview deployment? The connected account cannot access that team; its team-consent attempt returns “Team not found.” No repository change is needed to clear this gate. CI: https://github.com/rohitg00/agentmemory/actions/runs/42778921474 |
A project-filtered recall currently reads the session store even when a durable memory already carries the matching project. If that unnecessary read fails, recall rejects instead of returning the matching memory.
Read session metadata only when a directory filter needs it or project ownership must be established through the session. Preserve directory matching and fail-closed legacy ownership checks. Also assert that the failed-refill regression actually calls the ranker twice.
Addresses both follow-ups in #1647 (review). The original PR is already merged; this is a separate, small follow-up based on current main.
Validation:
The live-server integration test and seven skipped tests were not run. Both historical Actions failures on #1647 were approval expirations, not executed test failures: GitHub reports that the workflow required approval but expired first. Rerun attempts require upstream repository admin rights. A maintainer may need to approve hosted checks on this follow-up too.
Summary by CodeRabbit