Skip to content

Manage Jetpack Social Connections using wpcom/v2 endpoints#25449

Draft
crazytonyli wants to merge 3 commits intotrunkfrom
task/274-jetpack-social-endpoints
Draft

Manage Jetpack Social Connections using wpcom/v2 endpoints#25449
crazytonyli wants to merge 3 commits intotrunkfrom
task/274-jetpack-social-endpoints

Conversation

@crazytonyli
Copy link
Copy Markdown
Contributor

Description

Fixes https://linear.app/a8c/issue/CMM-274

Testing instructions

@dangermattic
Copy link
Copy Markdown
Collaborator

1 Warning
⚠️ This PR is larger than 500 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.
1 Message
📖 This PR is still a Draft: some checks will be skipped.

Generated by 🚫 Danger

@wpmobilebot
Copy link
Copy Markdown
Contributor

wpmobilebot commented Mar 25, 2026

🤖 Build Failure Analysis

This build has failures. Claude has analyzed them - check the build annotations for details.

Replace the dual keyringConnectionID/connectionID system with plain
connectionID throughout the publicize social sharing code. The new
wpcom/v2 endpoint no longer provides keyring_connection_id, and the
server-side skip metadata uses connectionID anyway.
Replace SharingSyncService with JetpackPublicizeService, which syncs
connections and services via wordpress-rs wpcom/v2 endpoints and adds
write operations (create, update, delete connections, fetch keyrings).
Move all publicize connection operations (create, update, delete,
fetch keyrings) from SharingService/SharingServiceRemote to
JetpackPublicizeService. Remove the legacy v1.1 API methods and
update all Obj-C callers.
@crazytonyli crazytonyli force-pushed the task/274-jetpack-social-endpoints branch from aedaeec to a9c6be6 Compare March 26, 2026 08:33
@sonarqubecloud
Copy link
Copy Markdown

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.

3 participants