Keep Hundreds of Repositories Secure, Reliable, and Current

Code doesn’t stay done. Dependencies age, vulnerabilities emerge, and new standards need to reach repositories owned by different teams. In this engineering roundtable, leaders from Keller Williams, TrueLayer, and Zapier discussed how they prioritize, roll out, and track changes at scale.

What it takes to make change stick

• Win agreement before writing code. Keller Williams brings maintenance work into quarterly planning, documents the change, sets a timeline, and asks teams to try it on one service early.
• Match oversight to risk. TrueLayer tests changes on a small set of repositories first and is working on canary deployments and automated rollback. Human review remains part of its process.
• Make progress visible. Zapier uses campaigns with automated checks, upgrade instructions, and reminders to track adoption across teams.

The takeaway: AI can help produce and review changes faster, but cross-team coordination, repository-specific standards, and human judgment still matter - especially for changes with complex dependencies.

Watch the roundtable to hear how these teams approach repository maintenance at scale.

‍