docs: cover gchat verification, linear token encryption, shared crypto helpers#445
Merged
docs: cover gchat verification, linear token encryption, shared crypto helpers#445
Conversation
…o helpers The adapter hardening pass in #441 made gchat JWT verification required, added optional at-rest encryption for Linear OAuth tokens, and promoted the AES-256-GCM helpers into @chat-adapter/shared. Update the affected package READMEs and the adapter-authoring guide to match.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
dancer
approved these changes
May 4, 2026
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
2 participants
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.
Follow-up docs for #441. That PR made Google Chat JWT verification required at construction time (one of
googleChatProjectNumber,pubsubAudience, or the newdisableSignatureVerificationflag), added optional at-rest encryption for Linear's stored OAuth tokens viaencryptionKey/LINEAR_ENCRYPTION_KEY, and promoted the AES-256-GCM helpers into@chat-adapter/sharedso other adapters can reuse them. None of that is currently reflected in the docs.This PR updates the gchat and Linear package READMEs to document the new config and env vars (and removes the gchat README line that still says verification is opt-in), adds the new exports to the
@chat-adapter/sharedREADME, and mirrors the Token encryption guidance into the adapter-authoring guide so community adapter authors land on it. Docs-only — no changeset.