Skip to content

fix: migrate LinkedIn comment API from deprecated v2 to REST#1332

Open
swaraj017 wants to merge 9 commits into
gitroomhq:mainfrom
swaraj017:fix/linkedin-comment-api
Open

fix: migrate LinkedIn comment API from deprecated v2 to REST#1332
swaraj017 wants to merge 9 commits into
gitroomhq:mainfrom
swaraj017:fix/linkedin-comment-api

Conversation

@swaraj017

@swaraj017 swaraj017 commented Mar 23, 2026

Copy link
Copy Markdown
Contributor

What kind of change does this PR introduce?

Bug fix

Why was this change needed?

Fixes #1319.

LinkedIn comment creation was still using deprecated v2 endpoints, causing comments and threaded replies to fail. Main post publishing had already been migrated, but the comment flow was missed.

This change updates the comment endpoints to the REST API and adds the required headers for successful requests.

Other information:

Tested against the LinkedIn REST API and verified both comment creation and threaded replies.

Checklist:

  • I have read the CONTRIBUTING guide.
  • I have signed the Contributor License Agreement (CLA).
  • I confirm I have not used AI to submit this PR or generate code for it.
  • I checked that there were no similar issues or PRs already open for this.
  • This PR fixes just ONE issue.

@vercel

vercel Bot commented Mar 23, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the Listinai Team on Vercel.

A member of the Team first needs to authorize it.

Comment thread libraries/nestjs-libraries/src/integrations/social/linkedin.provider.ts Outdated
@creyD

creyD commented Mar 27, 2026

Copy link
Copy Markdown

@nevo-david Could this bugfix be merged? @swaraj017 You tested this right?

@swaraj017

Copy link
Copy Markdown
Contributor Author

@nevo-david Could this bugfix be merged? @swaraj017 You tested this right?

Yes, I tested it

The issue raised earlier was valid, and I have updated the implementation to correctly parse the comment ID from the x-restli-id response header.

Tested with the LinkedIn REST API — comment creation and threading are working as expected.

@postiz-agent

postiz-agent Bot commented Apr 6, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@jorgedanisc

Copy link
Copy Markdown

Will we see this patch in the next update?

@swaraj017

Copy link
Copy Markdown
Contributor Author

Will we see this patch in the next update?

Thanks for the interest @jorgedanisc 🙌

The fix has been implemented and tested against the LinkedIn REST API — comment creation and threading are working as expected.

@nevo-david @creyD
Could you please take a look when you get a chance? Happy to make any further adjustments if needed.

Also, let me know if any additional validation or edge cases should be covered before merging.

@creyD

creyD commented Apr 21, 2026

Copy link
Copy Markdown

Thanks @github Screenshot 2026-04-21 at 22 42 36

@creyD

creyD commented Apr 21, 2026

Copy link
Copy Markdown

@nevo-david Would this be able to be merged?

@swaraj017

swaraj017 commented May 2, 2026

Copy link
Copy Markdown
Contributor Author

Hi @nevo-david, gentle ping
All checks are passing and this has been reviewed by @creyD.
Would appreciate your review when you have time. Happy to make any changes if needed.

@egelhaus egelhaus added the contribution:evaluate Evaluate the PR again label May 4, 2026
@postiz-contribution

Copy link
Copy Markdown

Hi @swaraj017! Thanks for the PR. Contributions to Postiz are gated behind an application. Please apply at https://contribute.postiz.com/p/postiz and we'll reopen this PR once you're approved.

@postiz-contribution postiz-contribution Bot added contribution:pending Awaiting application review and removed contribution:evaluate Evaluate the PR again labels May 4, 2026
@postiz-contribution

Copy link
Copy Markdown

Contribution-checker quality warning
Heuristic score: 0/100 (low). This is a non-blocking warning surfaced by the project's quality settings.

Heuristics that flagged:

  • Excessive inline code references — 9 inline refs (>3)
  • PR doesn't use the repo's PR template — No template headings or checklist items in body
  • Author mismatch across commits — 2 distinct authors
  • Conventional Commits format — 5 non-conv commits
  • No public email

If this is a genuine contribution, please add detail to your PR description and tighten the diff scope before reviewers look at it.

@postiz-contribution postiz-contribution Bot added contribution:evaluate Evaluate the PR again contribution:denied Application denied and removed contribution:pending Awaiting application review contribution:evaluate Evaluate the PR again labels May 8, 2026
@postiz-contribution

Copy link
Copy Markdown

Contribution-checker quality warning
Heuristic score: 0/100 (low). This is a non-blocking warning surfaced by the project's quality settings.

Heuristics that flagged:

  • Excessive inline code references — 9 inline refs (>3)
  • PR doesn't use the repo's PR template — 4 required checkbox items missing (max 1, match ≥80%)
  • Body adds too many extra headers beyond the template — 4 extra headers (>1)
  • Author mismatch across commits — 2 distinct authors
  • Conventional Commits format — 5 non-conv commits
  • No public email

If this is a genuine contribution, please add detail to your PR description and tighten the diff scope before reviewers look at it.

@postiz-contribution postiz-contribution Bot reopened this Jun 22, 2026
@postiz-contribution

Copy link
Copy Markdown

@swaraj017's application for Postiz was approved. Reopening this PR.

@postiz-contribution postiz-contribution Bot added contribution:approved Approved contributor and removed contribution:denied Application denied labels Jun 22, 2026
@postiz-contribution

Copy link
Copy Markdown

Contribution-checker quality warning
Heuristic score: 0/100 (low). This is a non-blocking warning surfaced by the project's quality settings.

Heuristics that flagged:

  • Excessive inline code references: 9 inline refs (>3)
  • PR doesn't use the repo's PR template: 5 required checkbox items missing (max 1, match ≥80%)
  • Body adds too many extra headers beyond the template: 4 extra headers (>1)
  • Author mismatch across commits: 2 distinct authors
  • Conventional Commits format: 5 non-conv commits
  • No public email

If this is a genuine contribution, please add detail to your PR description and tighten the diff scope before reviewers look at it.

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

Labels

contribution:approved Approved contributor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Linkedin Comments are not working

4 participants