We’ve published Devenia Autoposter for LinkedIn v1.5.12.
This release fixes a real production issue where LinkedIn posting could stop when an API version is retired.
What Happened
LinkedIn retired the previously used REST version (202501). When that happened, requests began returning 426 NONEXISTENT_VERSION, so autoposting failed even though the plugin was active and the token was still valid.
What’s Fixed in 1.5.12
- Added automatic LinkedIn API version fallback when a requested version is retired
- Persisted the first known-working API version in WordPress options (
dlap_linkedin_api_version) - Updated organization admin lookup compatibility by removing an unsupported projection parameter
- Applied the resilient request path to post publishing, image upload initialization, and organization ACL lookup
Why This Matters
With this change, the plugin no longer depends on a single hardcoded LinkedIn version. If LinkedIn sunsets one version, the plugin can recover by trying supported versions and continuing to post.
Upgrade Note
Update to v1.5.12 to get the fallback behavior. If you had missed posts during the version sunset window, publishing new posts after upgrade should resume normal LinkedIn sharing.