rest.li is deprecated and will be archived on July 22, 2026 #1178

After more than a decade, we are deprecating rest.li. The repository github.com/linkedin/rest.li will be moved to read-only (archived) on July 22, 2026.

Background. rest.li started at LinkedIn in 2012 and became the framework behind much of our service-to-service communication. Since then, LinkedIn has migrated its internal services to gRPC, and rest.li is no longer actively developed. External usage today is very limited, and we are not able to keep maintaining it publicly.

What this means:

• After July 22, 2026, the repository will be read-only. We will not accept new issues or pull requests, and there will be no further releases, bug fixes, or security patches.
• Existing artifacts on Maven Central (com.linkedin.pegasus:*) will stay published, so your current builds will keep working. Nothing breaks immediately.
• We are not providing a drop-in replacement. Internally LinkedIn moved to gRPC, but gRPC is a different model (binary RPC vs REST+JSON), not a direct migration path. If you depend on rest.li, please plan to move to a framework that fits your needs.

If you have questions, please comment here / reply to this thread before July 22, 2026.

Thank you to everyone who used and contributed to rest.li over the years.