diff --git a/src/pages/blog/2024-04-29-composite-schemas-announcement.mdx b/src/pages/blog/2024-04-29-composite-schemas-announcement.mdx
index 2f1406616e..03036e3676 100644
--- a/src/pages/blog/2024-04-29-composite-schemas-announcement.mdx
+++ b/src/pages/blog/2024-04-29-composite-schemas-announcement.mdx
@@ -2,7 +2,7 @@
 title: "Announcing the Composite Schemas Working Group"
 tags: ["announcements"]
 date: 2024-04-29
-byline: Jeff Auriemma, Benjie Gillam, Michael Staib, Kamil Kisiela
+byline: Jeff Auriemma, Benjie Gillam, Michael Staib, Kamil Kisiela, Praveen Durairaju
 ---
 
 In 2019, Apollo introduced GraphQL Federation as a way of splitting the task of building a GraphQL schema along team boundaries. It proposed a compelling alternative to prior techniques such as schema stitching and delegation, focussing on addressing the collaboration problems inherent in building a coherent schema within a large organization. Federation clearly filled a need and was adopted widely by platform engineers and API developers, a compelling way to compose microservices into a single access layer while retaining service boundaries and team ownership. Solutions from other vendors arose, tackling the same problems in similar ways but with different trade-offs, and some of the world’s largest enterprises have adopted these various patterns and are betting on GraphQL to solve some of their biggest pain points.