Allow Threads text-only posts.publish on current adapter - #42
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Supersedes #25 by recovering its valid text-only Threads behavior on the current released adapter stack instead of downgrading the active manifest.
Threads
posts.publish@5now requires exact text and accepts an optional PNG attachment. Text-only posts skip rupload, use the reviewed create form, bind a locator-only durable target, and verify exact actor/text permalink readback with no image. PNG posts keep their existing upload and readback path. Threads video publication remains independently preserved throughmedia.publish@1and MP4.Contract convergence
posts.publish@5.posts.publish@4image recovery and currentmedia.publish@1video recovery.Verification
bun run typecheckbun run checkThe exact candidate also received an independent semantic audit before merge. The superseded #25 branch is retained for provenance and will be closed only after this successor is merged and its postmerge gate passes.