# versioning Published articles for versioning. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Symfony 7.4.19 released DevFeed: [Symfony 7.4.19 released]() Original publisher: [Read original article]() Author: Fabien Potencier Published: 2026-09-15T07:12:11Z Content type: release Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [bug](), [Amazon Simple Queue Service (SQS)]() Tags: [bug](), [release](), [symfony](), [versioning]() ### AI overview Symfony 7.4.19 has been released with security-related updates and bug fixes across components including Messenger, Form, HttpFoundation, Console, Finder, Mailer, and others. ### Source excerpt Symfony 7.4.19 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your project. Tip... ## Symfony 6.4.46 released DevFeed: [Symfony 6.4.46 released]() Original publisher: [Read original article]() Author: Fabien Potencier Published: 2026-09-15T07:08:49Z Content type: release Language: en Sources: [Symfony Blog]() Topics: [Symfony](), [Security](), [OpenID connect (OIDC)](), [Cache]() Tags: [bug](), [cache](), [oidc](), [release](), [security](), [symfony](), [upgrade](), [versioning]() ### AI overview Symfony 6.4.46 is released with security, bug, translation, and component updates across the framework, including changes to Messenger, Form, HttpFoundation, OIDC handling, Cache, and other components. ### Source excerpt Symfony 6.4.46 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your project. Tip... ## From dedicated Workers to Serverless Workers: Migrating Temporal Workflows to AWS Lambda DevFeed: [From dedicated Workers to Serverless Workers: Migrating Temporal Workflows to AWS Lambda]() Original publisher: [Read original article]() Author: Garima Gupta Published: 2026-09-09T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [AWS Lambda](), [Serverless](), [Amazon Web Services](), [Deployment](), [Testing](), [SDKs]() Tags: [aws](), [aws-lambda](), [deployment](), [go](), [java](), [kubernetes](), [net](), [python](), [serverless](), [temporal](), [temporal-voices](), [testing](), [typescript](), [versioning]() ### AI overview This guide explains how to migrate Temporal Workers from long-lived processes on Kubernetes to Temporal Cloud Serverless Workers running on AWS Lambda. It focuses on AWS Lambda with Python examples and covers lifecycle changes, invocation scaling, deployment, versioning, and testing. ### Source excerpt Learn to migrate Temporal Workers from dedicated infrastructure to AWS Lambda with Serverless Workers, with guidance on deployment, versioning, and testing. ## Versioned Builds Are Back, With Master Builds For Fast Verification DevFeed: [Versioned Builds Are Back, With Master Builds For Fast Verification]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-07T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [releases](), [Development](), [Maven](), [Maven Central](), [Framework]() Tags: [enterprise](), [master](), [production](), [speed](), [verification](), [versioning]() ### AI overview Codename One reintroduces versioned cloud builds, allowing developers to pin builds to a specific published release or build against the current development head. The article explains use cases including production stabilization, regression diagnosis, and reproducing older customer environments, while noting that master builds are intended for verification rather than production shipping and that older versions are limited by account level because of support costs. ### Source excerpt Versioned builds return with a Maven-era model: pin a cloud build to a release, or build against master to verify the current development head. ## Temporal as a control plane for production agentic AI systems DevFeed: [Temporal as a control plane for production agentic AI systems]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2026-04-23T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Orchestration](), [Artificial Intelligence](), [control-plane](), [Architecture & Design]() Tags: [agentic](), [agentic-ai](), [ai](), [cost](), [enterprise](), [guardrails](), [observability](), [orchestration](), [temporal-voices](), [versioning]() ### AI overview The article explains how Temporal can help turn agentic AI prototypes into production systems. It describes agent patterns including conversational agents and event stream processors, and discusses orchestration, guardrails, observability, versioning, and cost controls. ### Source excerpt Learn how Temporal bridges the gap between agentic AI demos and production-ready systems -- with guardrails, observability, versioning, and cost controls built in. ## Safe deployments with Temporal Worker Versioning on Kubernetes DevFeed: [Safe deployments with Temporal Worker Versioning on Kubernetes]() Original publisher: [Read original article]() Author: Michael Jones Published: 2026-04-22T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Kubernetes](), [Deployment](), [Docker](), [kubectl](), [Command-line interface](), [Python]() Tags: [deployments](), [docker](), [how-to](), [kubernetes](), [temporal](), [versioning]() ### AI overview This tutorial demonstrates how Temporal Worker Versioning on Kubernetes can safely deploy Workflow code changes while preserving in-flight Workflows. It uses a research agent Workflow with expensive LLM calls to illustrate the risks of naive deployments and the deployment pattern that addresses them. ### Source excerpt Non-determinism errors killing your in-flight Workflows? Michael Jones shows how Temporal's Worker Versioning lets old and new Workers run side by side, so nothing gets lost on deploy. ## EU AI Act Compliance: Requirements, Risks, and What to Document DevFeed: [EU AI Act Compliance: Requirements, Risks, and What to Document]() Original publisher: [Read original article]() Author: info@goteleport.com (Kayne McGladrey, CISSP) Published: 2026-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Artificial Intelligence](), [Requirements](), [Documentation](), [audit](), [data-governance](), [Logging](), [Monitoring](), [Deployment](), [data]() Tags: [ai](), [compliance](), [cybersecurity](), [data](), [data-governance](), [dataset](), [deployment](), [development](), [documentation](), [eu](), [iso-27001](), [lifecycle](), [logging](), [monitoring](), [nist](), [real-time](), [reproducibility](), [soc-2](), [versioning]() ### AI overview A practical guide to EU AI Act compliance covering requirements, risks, technical documentation, logging, data governance, lifecycle evidence, traceability, monitoring, and human oversight. It outlines key compliance milestones from August 2025 through August 2027. ### Source excerpt Cut through EU AI Act complexity with practical guidance on requirements, risks, and documentation. ## Kubeflow Community Distribution 26.03.1 Release Announcement DevFeed: [Kubeflow Community Distribution 26.03.1 Release Announcement]() Original publisher: [Read original article]() Author: Kubeflow 26.03 Release Team Published: 2026-04-11T05:00:00Z Content type: release Language: en Sources: [Kubeflow]() Topics: [releases](), [Kubernetes](), [MinIO](), [istio](), [OpenID connect (OIDC)](), [kubectl]() Tags: [announcement](), [authentication](), [authorization](), [catalog](), [ci](), [istio](), [kubectl](), [kubernetes](), [minio](), [network](), [oidc](), [parallel](), [release](), [storage](), [ui](), [updates](), [versioning]() ### AI overview The Kubeflow Community Distribution 26.03.1 release introduces calendar-based versioning and updates components including Kubernetes, Kubeflow Pipelines, KServe, Trainer, notebooks, the dashboard, Istio, and related dependencies. It also adds native OIDC support, conditional and parallel Local Runner control flows, SeaweedFS storage support, and completes MinIO deprecation. ### Source excerpt The release versioning is now calendar-based (Year.Month.Patch). Around two base releases are planned per year with optional patch releases. The best-effort only community support is roughly 6 months and there is commercial support available from multiple vendors. Please update regularly as explained in our upgrading and extending section to benefit also from security and performance improvements. Release details: 26.03 and 26.03.1. ## Safe, versioned Worker Deployments on Kubernetes: Now with autoscaling! DevFeed: [Safe, versioned Worker Deployments on Kubernetes: Now with autoscaling!]() Original publisher: [Read original article]() Author: Brandon Chavis Published: 2026-03-30T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [autoscaling](), [Kubernetes](), [Deployment](), [Open Source]() Tags: [autoscaling](), [deployments](), [kubernetes](), [kubernetes-operator](), [kubernetes-scaling](), [metrics](), [product-news](), [versioning]() ### AI overview Temporal's open-source Worker Controller now supports attaching Kubernetes resources such as Horizontal Pod Autoscalers and PodDisruptionBudgets to versioned worker deployments. Worker versions can be scaled independently using version-specific backlog metrics. ### Source excerpt Automate Temporal Worker autoscaling on Kubernetes. Learn how the new WorkerResourceTemplate attaches HPAs to versioned deployments for independent scaling. ## Announcing GA for Worker Versioning and Public Preview for Upgrade on Continue-as-New DevFeed: [Announcing GA for Worker Versioning and Public Preview for Upgrade on Continue-as-New]() Original publisher: [Read original article]() Author: Brandon Chavis Published: 2026-03-30T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [version](), [Deployment](), [patches](), [configuration](), [upgrade]() Tags: [deployment](), [long-running](), [patches](), [preview](), [product-news](), [upgrade](), [versioning](), [workflow]() ### AI overview Temporal announces General Availability for Worker Versioning and a Public Preview of Upgrade on Continue-as-New. The article explains how versioning can replace workflow patches and how long-running Workflows can upgrade at Continue-as-New boundaries. ### Source excerpt Today, we're announcing the General Availability of Worker Versioning and a Public Preview of Upgrade on Continue-as-New, a new capability that eliminates patching for many long-running Workflow patterns. ## The New Apollo Kotlin Normalized Cache DevFeed: [The New Apollo Kotlin Normalized Cache]() Original publisher: [Read original article]() Author: Benoit Lubek Published: 2026-03-09T01:00:13Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [Caching](), [Kotlin](), [Android](), [client library](), [GraphQL](), [Library]() Tags: [android](), [announcement](), [caching](), [client-library](), [graphql](), [kotlin](), [library](), [versioning]() ### AI overview Apollo released version 1 of a new normalized cache library for Apollo Kotlin, the GraphQL client library for Android and Kotlin. It adds pagination support, expiration, partial cache reads, garbage collection and trimming, configurable key scopes, and improved SQL cache performance. ### Source excerpt Today, we're releasing the new cache library for Apollo Kotlin, the GraphQL client library for Android and Kotlin. Historically, caching has generated the most questions, tickets, and feedback, and we knew it was an area that deserved significant attention. To do that efficiently, we decided early on to create a new repository with its own independent name, artifacts, and versioning. This allowed us to iterate on this new version without disrupting the existing stable library. ## Amazon S3 Versioning and Multipart Uploads Can Create Hidden Storage Costs DevFeed: [Amazon S3 Versioning and Multipart Uploads Can Create Hidden Storage Costs]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2026-02-28T00:00:00Z Content type: opinion Language: en Sources: [Artur Dryomov]() Topics: [Amazon S3](), [API](), [cloud-infrastructure]() Tags: [amazon](), [amazon-s3](), [api](), [cli](), [cost](), [monitoring](), [reporting](), [s3](), [storage](), [uploads](), [versioning]() ### AI overview This article examines Amazon S3 caveats involving object versioning and multipart uploads. It explains that implicit usage metrics and incomplete uploads can leave data stored indefinitely, creating unexpected storage costs, and discusses expiration and monitoring as preventive measures. ### Source excerpt Amazon Simple Storage Service became not so simple over time. Not surprising at all -- a lot has happened since 2006. The API reference has more than 100 actions and Amazon itself puts S3 features into a couple dozen of categories. It's a good tool for countless applications -- naturally, it has caveats. Fortunately or not, it's also a product. As such, caveats become problems and problems become unpleasant and surprising bills. ## Building observable AI agents: Temporal now integrates with Braintrust DevFeed: [Building observable AI agents: Temporal now integrates with Braintrust]() Original publisher: [Read original article]() Author: Ornella Altunyan Published: 2026-01-20T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [agent observability](), [ai observability](), [tracing](), [prompt](), [Large Language Model](), [Artificial Intelligence]() Tags: [agents](), [ai](), [ai-agents](), [announce](), [announcements](), [evals](), [execution](), [integration](), [latency](), [llm](), [observable](), [release](), [temporal](), [tracing](), [versioning]() ### AI overview Temporal announces an integration with Braintrust that combines Temporal's durable workflow execution with Braintrust's LLM observability. The integration is intended to help teams monitor and debug AI agents in production using tracing, prompt versioning, evaluations, and cost and latency metrics. ### Source excerpt Build observable AI agents with Temporal's new Braintrust integration -- combine durable workflow execution with LLM tracing, prompt versioning, evals, and cost/latency metrics so you can ship reliable, debuggable agents in production. ## Adyen API Diff Tool DevFeed: [Adyen API Diff Tool]() Original publisher: [Read original article]() Author: Adyen Published: 2025-08-19T08:33:01Z Content type: article Language: en Sources: [Adyen Tech]() Topics: [API](), [Tool](), [User Experience](), [Developer experience](), [HTTP]() Tags: [adyen](), [api](), [changelog](), [design](), [developer-experience](), [developers](), [features](), [http](), [integration](), [open-api](), [tool](), [versioning]() ### AI overview Adyen introduces an API Diff Tool that helps developers compare API versions, inspect changes by version, endpoint, and HTTP method, identify breaking changes, and navigate to related API reference details. ### Source excerpt Track new features, recent updates and breaking changes APIs evolve quickly with new features, design changes, and deprecations, making it challenging for consumers to keep up. This impact can be significant: developers might miss valuable improvements, misunderstand the behavior of new features, delay the adoption of critical compliance updates. This is why we have put passion and effort in the Adyen API Diff Tool, a new tool designed to help developers and technical users easily track and compare changes between API versions. Whether you're maintaining an existing integration or building something new, staying on top of API changes is critical. Previously, this information was scattered across various sources like product announcements, documentation, release notes, and GitHub, resulting in a suboptimal user experience. This changes today with our new powerful API Diff Tool. Features Our goal is simple: to make it easy to understand what's changed in the Adyen APIs between any two versions. The Diff Tool includes built-in filters to: Compare API versions View changes by version, endpoint and HTTP method Group changes by endpoint Spot quickly what's new, changed, or removed Focus on Breaking Changes only Labels, colors, and accordions provide a clean and effective way to visualize the changes. It is embedded directly in the API Explorer. From any specific change in the log, you can easily navigate to the relevant API reference or endpoint details. Benefits for Developers and other Users The API Diff Tool is designed to remove uncertainty when working with Adyen APIs. Whether you're integrating for the first time or upgrading to a new version, it is a valuable tool to: Understand what changed: compare any two API versions and see exactly what's been added, removed, or modified. Spot breaking changes early: identify changes that could impact your integration, so you can plan ahead. Evolve faster and safer: stay up-to-date with the latest API releases to integrate the ## Durable Digest: July 2025 DevFeed: [Durable Digest: July 2025]() Original publisher: [Read original article]() Author: Temporal Technologies Published: 2025-07-29T00:00:00Z Content type: news Language: en Sources: [Temporal Blog]() Topics: [releases](), [SDKs](), [distributed-systems](), [Model Context Protocol](), [Artificial Intelligence]() Tags: [2025](), [ai](), [announcements](), [community](), [events](), [pre-release](), [releases](), [ruby](), [sdk](), [temporal](), [update](), [versioning]() ### AI overview Temporal's July 2025 update covers product improvements including Nexus updates, Update-With-Start, Worker Versioning, and Task Queue Priority. It also lists Go, Java, TypeScript, PHP, and Ruby SDK updates, plus tutorials, community content, and upcoming events. ### Source excerpt Temporal's July 2025 update: Worker Versioning, Update-With-Start, SDK releases, AI tutorials, Ruby preview, community highlights, and upcoming events. Stay current! ## Announcing new Temporal capabilities from Replay 2025 DevFeed: [Announcing new Temporal capabilities from Replay 2025]() Original publisher: [Read original article]() Author: Meagan Speare Published: 2025-03-04T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [SDKs](), [Ruby](), [Framework](), [Development](), [Cloud](), [Kubernetes]() Tags: [2025](), [cloud](), [kubernetes](), [product-news](), [sdk](), [temporal](), [updates](), [versioning]() ### AI overview Temporal announced new capabilities at Replay 2025, including a pre-release Ruby SDK, general availability for Temporal Nexus, pre-release Worker Versioning APIs and Deployments, and updates for optimizing live Workflows, Activities, and Workers. ### Source excerpt Discover Temporal's latest updates: Ruby SDK, Nexus GA, Worker Versioning, Cloud HA features, and the new Code Exchange. Build reliable systems faster. ## Docusaurus 3.3 DevFeed: [Docusaurus 3.3]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2024-05-03T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [React](), [Development]() Tags: [changelog](), [react](), [release](), [upgrade](), [versioning]() ### AI overview Docusaurus 3.3 is announced as a minor release. It prepares Docusaurus for React 19 by addressing React 18.3 warnings, adds a flexible sitemap plugin hook, improves the pages plugin APIs, and includes other configuration, plugin, rendering, and navigation changes. ### Source excerpt We are happy to announce Docusaurus 3.3. ## Learn Temporal Workflow Versioning with free hands-on training DevFeed: [Learn Temporal Workflow Versioning with free hands-on training]() Original publisher: [Read original article]() Author: Tom Wheeler Published: 2024-03-28T06:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Deployment](), [Code](), [SDKs]() Tags: [apis](), [courses](), [deployment](), [free](), [how-to](), [sdk](), [training](), [versioning]() ### AI overview Temporal announces four free hands-on training courses about Workflow Versioning, each using a specific SDK. The courses explain when versioning is needed, demonstrate incompatible application changes and non-deterministic errors, and cover Workflow Type Versioning and the GetVersion / Patching APIs. ### Source excerpt Today we're excited to announce the immediate availability of four new hands-on training courses. ## Mintlify product update February 2024 DevFeed: [Mintlify product update February 2024]() Original publisher: [Read original article]() Author: Joshua Kim Published: 2024-03-08T00:00:00Z Content type: release Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Search engine optimization (SEO)](), [dashboards](), [configuration](), [Command-line interface](), [Parsing](), [Support]() Tags: [announce](), [announcements](), [cli](), [configuration](), [parsing](), [product](), [product-updates](), [seo](), [update](), [versioning]() ### AI overview Mintlify's February 2024 product update introduced wildcard redirects, an upgraded dashboard with navigation and update logs, tab versioning for API documentation, improved CLI detection of frontmatter errors, and streamlined project management features. ### Source excerpt In February, we shipped wildcard redirects and upgraded our dashboard, tab versioning setup, and more. ## Versioning and Releasing Packages in a Monorepo DevFeed: [Versioning and Releasing Packages in a Monorepo]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2024-02-09T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [monorepo](), [npm packages](), [releases](), [Git](), [npm]() Tags: [automated](), [changelog](), [git](), [monorepo](), [npm](), [nx](), [nx-cloud](), [packages](), [pnpm](), [release](), [releases](), [versioning]() ### AI overview A tutorial on using Nx Release to version and publish packages in a monorepo. It covers conventional commits, automated changelog generation, dry runs, package and lockfile updates, Git staging, commits, and tags. ### Source excerpt Learn how to use Nx Release to version and publish packages in your monorepo with conventional commits and automated changelog generation. ## Docusaurus 3.1 DevFeed: [Docusaurus 3.1]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2024-01-05T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [changelog](), [Documentation](), [Command-line interface](), [MDX]() Tags: [changelog](), [changes](), [cli](), [cobol](), [configuration](), [mdx](), [release](), [upgrade](), [versioning]() ### AI overview Docusaurus 3.1 adds broken-anchor detection to the built-in broken links checker and introduces a new function hook for front matter transformations and integrations. The release also includes MDX and code-block improvements, CLI port configuration through an environment variable, and completed Brazilian Portuguese translations. ### Source excerpt We are happy to announce Docusaurus 3.1. ## Replay Rewind publishes conference talks on Temporal Cloud, workflow execution, and product updates DevFeed: [Replay Rewind publishes conference talks on Temporal Cloud, workflow execution, and product updates]() Original publisher: [Read original article]() Author: Jim Walker Published: 2023-10-20T06:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [execution](), [Persistence](), [versioning](), [Cloud]() Tags: [announcements](), [cloud](), [community](), [conference](), [execution](), [persistence](), [temporal](), [versioning](), [videos]() ### AI overview Replay Rewind has published an initial set of twenty conference talks, with more expected in the following weeks. The talks cover Temporal Cloud's custom persistence layer, versioning, schedules, workflow updates, multi-region cloud, durable execution, and other product updates. ### Source excerpt Last month, we held our second annual conference in beautiful Bellevue, Washington and were thankful for 450+ people that helped make it an amazing event! ## dbdev: PostgreSQL Package Manager DevFeed: [dbdev: PostgreSQL Package Manager]() Original publisher: [Read original article]() Author: Oliver Rice; John Dalton Published: 2023-04-14T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [Package manager](), [PostgreSQL](), [SQL](), [Deployment](), [Tooling]() Tags: [ascii](), [bug-fixes](), [deployment](), [ecosystem](), [features](), [postgresql](), [sql](), [versioning]() ### AI overview Supabase is publicly previewing dbdev, a PostgreSQL package manager with a read-only registry initially populated with example packages. It is designed to support publishing, discovering, and repeatedly deploying SQL libraries and applications, with initial compatibility for new Supabase projects and PostgreSQL instances. ### Source excerpt We're publicly previewing dbdev, a PostgreSQL package manager. ## Doximity Mobile Releases Streamlined with Automation DevFeed: [Doximity Mobile Releases Streamlined with Automation]() Original publisher: [Read original article]() Author: Doximity Published: 2023-04-12T14:19:00Z Content type: article Language: en Sources: [Doximity]() Topics: [Automation](), [Mobile](), [releases](), [Deployment]() Tags: [automation](), [continuous-deployment](), [deployment](), [devops](), [efficiency](), [mobile](), [mobile-apps](), [performance](), [production](), [releases](), [versioning]() ### AI overview This article describes how Doximity's mobile team automated its release process to move from a three-week cycle to weekly releases. The team achieved the weekly cadence in November 2021, and weekly releases later required zero developer overhead while QA controlled the process. ### Source excerpt Releasing mobile apps to the store is inherently slower than web updates due to manual process overhead, such as versioning, packaging, and submitting to the App Store for review. While web developers have long enjoyed full buzzword-compliant Continuous Deployment, mobile teams generally use a defined release cadence, typically 2-4 weeks. The DORA metric, which stands for DevOps Research and Assessment, evaluates performance using four key metrics: Deployment Frequency (DF), Lead Time for Changes (LT), Mean Time To Recover (MTTR), and Change Failure Rate (CFR). These metrics are commonly used to gauge an organization's agility, efficiency, and ability to implement changes quickly. Organizations that excel in these areas tend to perform smaller, more frequent deployments. A few years ago, our mobile team was classified as a medium performer for deployment frequency and reported 47% for change rate failure, which should be from 0% to 15%. We knew we could do better. Doximity mobile teams historically used a three-week release cycle. However, the pace wasn't fast enough to quickly get new features out the door. As a result, almost every release would be delayed due to some "very important thing" that had to get in. We also had to do more patch releases to fix issues introduced in production, which were even harder to debug with so many changes in a single version. One of the essential features that forced us to accelerate our release cycle was the Dialer Video product. We launched Dialer Video soon after the beginning of the pandemic. We wanted to get something out and to iterate quickly to meet the needs of our doctors while they were going through a difficult time and learning to work remotely. In April 2020, we attempted to shift to a weekly release cycle to meet this demand. While some automation was in place, there was also a lot of overhead with each release, and the developers spent a significant amount of time just managing the process. We compromised on a two- [Next page]()