Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 5, 2025

This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.

github-actions bot and others added 2 commits December 5, 2025 18:11
* feat(docs): add security questionnaire trust center documentation

* fix(docs): update format handling in security questionnaire example

* refactor(docs): restructure trust access and security questionnaire documentation

* feat(docs): add images to trust access and security questionnaire sections

---------

Co-authored-by: Tofik Hasanov <[email protected]>
Co-authored-by: Mariano Fuentes <[email protected]>
@vercel
Copy link

vercel bot commented Dec 5, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
app (staging) Ready Ready Preview Comment Dec 5, 2025 11:27pm
portal (staging) Ready Ready Preview Comment Dec 5, 2025 11:27pm

@cursor
Copy link

cursor bot commented Dec 5, 2025

PR Summary

Introduces a new Trust section (Access & Grants, Portal Settings), refactors trust portal actions/paths with improved autosave and domain checks, updates portal auth/login and error handling, and adds Trust documentation including the security questionnaire API.

  • App (Trust area):
    • Add /[orgId]/trust layout and pages (Access & Grants, Portal Settings); remove legacy settings/trust-portal entry and loading.
    • Update titles/labels (e.g., "Access & Grants").
  • Portal Settings UX:
    • TrustPortalSwitch: safer autosave (field-scoped, concurrency guards, refs), longer debounces, robust friendly URL availability checks, and streamlined UI structure.
    • Add/adjust TrustPortalDomain with DNS verification UI; enhance actions to revalidate /${orgId}/trust paths.
  • Server actions:
    • Update revalidate targets from settings/trust-portal to trust routes across domain/portal actions.
  • Portal app:
    • Auth config upgraded (better-auth 1.4.5; advanced.database.generateId nesting); login action sends headers and uses asResponse; org home page error handling/redirects simplified.
  • Docs:
    • Restructure Guides with Trust group; add security-questionnaire-trust-center guide; rename Trust Access page to "Access" and expand content.
  • Deps:

Written by Cursor Bugbot for commit e86a2c2. This will update automatically on new commits. Configure here.

…ugs in fields (#1867)

Co-authored-by: Tofik Hasanov <[email protected]>
Co-authored-by: Mariano Fuentes <[email protected]>
@vercel vercel bot temporarily deployed to staging – portal December 5, 2025 21:24 Inactive
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@graphite-app
Copy link

graphite-app bot commented Dec 5, 2025

Graphite Automations

"Auto-assign PRs to Author" took an action on this PR • (12/05/25)

1 assignee was added to this PR based on Mariano Fuentes's automation.

@vercel vercel bot temporarily deployed to staging – app December 5, 2025 23:25 Inactive
@Marfuen Marfuen merged commit 451238d into release Dec 5, 2025
12 of 14 checks passed
@claudfuen
Copy link
Contributor

🎉 This PR is included in version 1.68.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

email: parsedInput.email,
otp: parsedInput.otp,
},
asResponse: true,
Copy link

Choose a reason for hiding this comment

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

Bug: Login response cookies discarded causing failed session

The signInEmailOTP call with asResponse: true returns a Response object containing Set-Cookie headers needed to establish the user session. However, this response is simply awaited and discarded without forwarding the cookies. Unlike route handlers where the Response can be returned directly, server actions require explicit cookie handling. The session cookie will not be set on the client, causing authentication to fail even after a successful OTP verification.

Fix in Cursor Fix in Web

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants