# rollback Published articles for rollback. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## I moved my laptop to a rolling-release distro and the snapshots did the heavy lifting DevFeed: [I moved my laptop to a rolling-release distro and the snapshots did the heavy lifting]() Original publisher: [Read original article]() Author: Shed Stack Published: 2026-09-06T18:00:00Z Content type: opinion Language: en Sources: [Shed Stack]() Topics: [btrfs](), [Kernel](), [Hardware]() Tags: [boot](), [bootloader](), [btrfs](), [driver](), [laptop](), [packages](), [rollback](), [snapshots](), [update]() ### AI overview The author describes moving a laptop to CachyOS, a rolling-release distribution, to obtain newer kernels and packages. Automatic Btrfs snapshots managed with snapper provide rollback protection when updates affect boot components, drivers, or the desktop. ### Source excerpt CachyOS, snapper, and the DPTF fix. What a rolling release is actually like when you keep a parachute. ## Mintlify introduces instant rollbacks for Enterprise deployments DevFeed: [Mintlify introduces instant rollbacks for Enterprise deployments]() Original publisher: [Read original article]() Author: David Isquick Published: 2026-08-31T00:00:00Z Content type: release Language: en Sources: [Mintlify Blog]() Topics: [Deployment](), [audit](), [Pull Request](), [GitHub](), [GitLab](), [bitbucket]() Tags: [access-control](), [announcements](), [audit](), [configuration](), [deployment](), [pull-request](), [rollback]() ### AI overview Mintlify has introduced instant rollbacks for Enterprise customers, allowing them to restore one of their last 10 successful builds from the dashboard in seconds. Rollbacks are recorded in audit logs and currently support non-authenticated pages. ### Source excerpt Instant rollbacks are now live for Mintlify Enterprise customers. You can roll back to a known good deployment in seconds, without waiting on a full rebuild. ## How to migrate from a custom auth system to a third-party provider DevFeed: [How to migrate from a custom auth system to a third-party provider]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-26T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [migration](), [passwords](), [Single sign-on (SSO)](), [saml]() Tags: [auth](), [how-to](), [migration](), [password](), [rollback](), [saml](), [sso](), [third-party]() ### AI overview A guide to moving from a custom authentication system to a third-party provider. It explains how password-hash portability, SSO callback control, and an inventory of existing authentication components determine the migration strategy and cutover plan. ### Source excerpt What is actually portable, how to import password hashes without forcing a reset, and how to cut over with a rollback you can trust. ## Add the dependency graph to a Kotlin K2 migration checklist DevFeed: [Add the dependency graph to a Kotlin K2 migration checklist]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Kotlin](), [migration](), [Dependency injection](), [Graphs](), [Compiler](), [toolchain](), [Android Gradle Plugin](), [Compose]() Tags: [android-gradle-plugin](), [compiler](), [compose](), [dependency-injection](), [graph](), [kotlin](), [migration](), [rollback](), [toolchain](), [verification]() ### AI overview A practical checklist for Kotlin K2 migrations in projects that generate or validate dependency wiring. It recommends mapping the compiler and build toolchain, upgrading from a known compatibility matrix, cleaning and inspecting generated output, verifying dependency graphs across flavors and targets, testing runtime slices, and keeping rollback changes coherent. ### Source excerpt A K2 migration is usually planned around source compatibility and compiler diagnostics. Projects that generate or validate dependency wiring need another checklist: compiler plugin versions, generated sources, metadata compatibility, and graph verification on every target. Map the toolchain first Record the Kotlin plugin, Compose compiler plugin, KSP or annotation tooling, dependency-injection compiler plugin, Android Gradle plugin, and target libraries. Upgrade from a known matrix instead of selecting each latest version independently. ## Migrating Live Enterprise SCIM Directories to WorkOS with SCIM Bridge DevFeed: [Migrating Live Enterprise SCIM Directories to WorkOS with SCIM Bridge]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-14T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [migration](), [Provisioning]() Tags: [architecture](), [bridge](), [database](), [migration](), [okta](), [provisioning](), [proxy](), [rollback]() ### AI overview The article presents SCIM Bridge, a reversible migration proxy for moving live enterprise directories from a home-grown SCIM endpoint to WorkOS Directory Sync. It describes dual-writing, backfilling, verification, staged authority, and rollback before final cutover. ### Source excerpt How SCIM Bridge moves live enterprise directories onto WorkOS Directory Sync with zero downtime, staged authority, and lossless rollback until the last step. ## Software Delivery Platform: Key Features & How to Evaluate DevFeed: [Software Delivery Platform: Key Features & How to Evaluate]() Original publisher: [Read original article]() Author: Eric Minick Published: 2026-08-11T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Software](), [CI/CD](), [Continuous Delivery (CD)](), [Continuous integration]() Tags: [audit](), [automation](), [blog](), [ci-cd](), [ci-cd-pipeline](), [governance](), [how-to](), [progressive-delivery](), [rollback](), [scalability](), [security](), [software-delivery](), [visibility]() ### AI overview This article explains how a software delivery platform differs from a standalone CI/CD tool. It describes a platform as an integrated system covering the full after-code lifecycle, including continuous integration, continuous delivery, security, governance, insights, coordination, and rollback, then outlines criteria for evaluating vendors. ### Source excerpt A software delivery platform isn't just a CI/CD tool. Get the must-have feature checklist and the demo questions to use when evaluating vendors. | Blog ## How to Build an A/B Testing Framework for Modern CI/CD Pipelines DevFeed: [How to Build an A/B Testing Framework for Modern CI/CD Pipelines]() Original publisher: [Read original article]() Author: Aaron Newcomb Published: 2026-08-10T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [A/B Testing](), [CI/CD](), [CI/CD Pipeline](), [feature flags](), [progressive delivery](), [Monitoring]() Tags: [a-b-testing](), [ci-cd](), [feature-flags](), [how-to](), [monitoring](), [progressive-delivery](), [rollback](), [verification]() ### AI overview This tutorial explains how to integrate A/B testing into CI/CD pipelines using feature flags, progressive delivery, real-time metrics, automated verification, and rollback controls. It argues that deployment should be decoupled from release so teams can validate changes before full rollout. ### Source excerpt Learn how to build an A/B testing framework in your CI/CD pipeline. Accelerate software delivery, reduce risk, and boost innovation. Start now! | Blog ## Blue Green and Canary Deployments Explained DevFeed: [Blue Green and Canary Deployments Explained]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-09T16:30:08Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [Deployment](), [Software](), [Database]() Tags: [argo-rollouts](), [automation](), [blue-green-and-canary-deployments](), [ci-cd](), [ci-cd-pipeline](), [cloud](), [database](), [deployment](), [deployment-strategies](), [devops](), [dora-change-failure-rate](), [expand-and-contract-migration](), [feature-flags](), [guide](), [kubernetes](), [progressive-delivery](), [release-management](), [rollback](), [rolling-update](), [schema](), [sre](), [traffic-splitting](), [zero-downtime-deployment]() ### AI overview This guide explains blue-green and canary deployment strategies for replacing running software versions. It emphasizes that effective rollback depends on detecting problems with reliable metrics and that database schema changes can limit reversibility. ### Source excerpt Both strategies buy you the same thing, which is a cheap way to be wrong. The mechanism is the easy part, and the two hard parts are noticing you are wrong and dealing with the database. ## GitHub agentic workflows and Renovate DevFeed: [GitHub agentic workflows and Renovate]() Original publisher: [Read original article]() Author: Nicolas Fränkel Published: 2026-08-02T00:00:00Z Content type: tutorial Language: en Sources: [Nicolas Fränkel]() Topics: [GitHub](), [GitHub Actions]() Tags: [agentic-workflow](), [dependencies](), [github](), [github-actions](), [github-agentic-workflows](), [pull-requests](), [renovate](), [rollback](), [technical]() ### AI overview This article explains how Renovate dependency updates can break GitHub agentic workflows by changing an action SHA without updating the matching generated scripts. It also describes a failed recompilation workflow that rolled back an unrelated Node.js update, then identifies the need to keep the generated lock file synchronized with its release. ### Source excerpt I've been a big fan of Renovate for a couple of years already. Renovate scans your repositories, detects outdated package versions, and opens pull requests to automatically bump them. It's similar to Dependabot in that it keeps your dependencies up to date. If I had to compare them in one sentence, I'd say Renovate is less integrated in the GitHub ecosystem, but handles more ecosystems and, more importantly, is extensible. ## Safe Database Rollback Starts Before Deployment DevFeed: [Safe Database Rollback Starts Before Deployment]() Original publisher: [Read original article]() Author: Raul Junco Published: 2026-07-25T12:00:54Z Content type: tutorial Language: en Sources: [System Design Classroom]() Topics: [Database](), [Deployment](), [migration](), [feature flags]() Tags: [database](), [deployment](), [feature-flags](), [migrations](), [production](), [recovery](), [rollback](), [schema]() ### AI overview This article explains why rolling back application code does not automatically roll back database schema or production data. It presents backward-compatible schema changes, staged migrations, feature flags, and targeted recovery as ways to prepare for deployment failures and reduce the risk of data loss. ### Source excerpt Learn why safe database rollback starts before deployment, and how backward-compatible schema changes, staged migrations, feature flags, and targeted recovery keep production failures from turning into data loss. ## A Step-by-Step Guide to Feature Flag Implementation in CI/CD DevFeed: [A Step-by-Step Guide to Feature Flag Implementation in CI/CD]() Original publisher: [Read original article]() Author: Aaron Newcomb Published: 2026-07-23T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [CI/CD](), [feature flags](), [GitOps](), [Automation](), [Microservices](), [Deployment]() Tags: [automation](), [ci-cd](), [deployment](), [feature-flags](), [gitops](), [governance](), [guide](), [microservices](), [pipelines](), [policy-as-code](), [rollback]() ### AI overview A step-by-step tutorial on implementing feature flags in enterprise CI/CD pipelines. It explains how governance, policy as code, GitOps workflows, automation, verification, gradual rollouts, and rollback capabilities can help teams manage releases across many services while maintaining control and compliance. ### Source excerpt Discover how to implement Feature Flags in CI/CD pipelines using governance, automation, and AI-driven delivery. Speed up your releases while keeping them safe. | Blog ## Software Release Management: A Practical Guide in 2026 DevFeed: [Software Release Management: A Practical Guide in 2026]() Original publisher: [Read original article]() Author: Eric Minick Published: 2026-07-20T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [Software](), [releases](), [Development](), [Deployment](), [Testing](), [CI/CD](), [feature flags]() Tags: [best-practices](), [ci-cd](), [deployment](), [feature-flags](), [guide](), [pipelines](), [release](), [release-management](), [rollback](), [software]() ### AI overview A practical guide to software release management, covering how code moves through testing, approval, deployment, monitoring, verification, and rollback. It explains the distinction between deployment and release and discusses feature flags, automated safety gates, and progressive delivery. ### Source excerpt Master software release management best practices. Learn how to reduce risk, speed up release pipelines, and ship faster with confidence in 2026. | Blog ## Harness AI Verification and Rollback for Argo CD: Limitations of Static Thresholds DevFeed: [Harness AI Verification and Rollback for Argo CD: Limitations of Static Thresholds]() Original publisher: [Read original article]() Author: Prasad Satam Akshit Madan Shubhendu Patidar Published: 2026-06-17T00:00:00Z Content type: opinion Language: en Sources: [Harness Blog]() Topics: [argo-cd](), [GitOps](), [Kubernetes](), [Artificial Intelligence](), [Prometheus]() Tags: [ai](), [argo-cd](), [gitops](), [harness](), [kubernetes](), [machine-learning](), [maintenance](), [progressive-delivery](), [prometheus](), [rollback](), [software-delivery](), [statistical-significance]() ### AI overview This vendor commentary argues that Argo Rollouts Analysis Templates can be difficult to maintain because they rely on manually defined static thresholds. It presents Harness AI Verification and Rollback as a context-aware alternative that uses unsupervised machine learning and service health trajectories to assess deviations and support rollbacks. ### Source excerpt Stop the maintenance nightmare of static thresholds. Learn how Harness AI Verification and Rollback provides context-aware safety for Argo CD. | Blog ## Five Deployment Strategies for Safer Software Releases DevFeed: [Five Deployment Strategies for Safer Software Releases]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-05-12T07:05:17Z Content type: article Language: en Sources: [System Design Codex]() Topics: [Deployment Strategies](), [Deployment](), [progressive delivery](), [App]() Tags: [blue-green-deployment](), [deployment-strategies](), [downtime](), [load-balancer](), [progressive-delivery](), [rollback]() ### AI overview This article discusses deployment strategies for reducing release risk, downtime, and user impact. It explains blue/green deployment and canary deployment, including their workflows, benefits, tradeoffs, and suitable use cases, and introduces A/B testing as part of a release process. ### Source excerpt Every developer should know these ## Git sync & workspace forks: your entire workspace, version controlled DevFeed: [Git sync & workspace forks: your entire workspace, version controlled]() Original publisher: [Read original article]() Author: Tristan Lécuyer Published: 2026-04-02T00:00:00Z Content type: release Language: en Sources: [Windmill Blog]() Topics: [Git](), [version-control](), [CI/CD](), [GitLab](), [GitHub]() Tags: [azure](), [bitbucket](), [ci-cd](), [fork](), [git](), [gitlab](), [launch-week](), [merge](), [pipelines](), [repository](), [review](), [rollback](), [sync]() ### AI overview Windmill introduces redesigned bidirectional Git sync and workspace forks. Git sync commits and pushes deployed items to a configured repository and can pull updates from Git, while forks provide isolated feature-development workspaces with deployment, merge, and Git-based workflows. ### Source excerpt Introducing improved Git sync and workspace forks: sync workspaces to Git, fork for feature development, and deploy via CI/CD. ## System Migration: Minimize Downtime, Maximize Efficiency DevFeed: [System Migration: Minimize Downtime, Maximize Efficiency]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-16T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [migration](), [systems](), [async](), [client](), [event driven](), [Kafka](), [API]() Tags: [apache-kafka](), [api](), [architecture](), [async](), [bridge-layer](), [data-pipelines](), [downtime](), [event-driven-architecture](), [metrics](), [migration](), [observability](), [production](), [reliability](), [rollback](), [system-migration](), [traffic-leakage]() ### AI overview A practical guide to migrating an existing system with minimal disruption. It recommends isolated-environment testing, load testing, adapters for incompatible contracts, synchronized asynchronous pipelines, a Kafka-based shared stream, a bridge layer, staged traffic switching, monitoring, and rollback preparation. ### Source excerpt Migrate behind a bridge layer that routes all client traffic and supports three modes: old-only, dual, and new-only. Run dual mode to compare responses without user impact, keep a back-sync pipeline so the old system stays current for rollback, and shift traffic in stages while watching metrics at each step. ## What Happens to an SQL Query? DevFeed: [What Happens to an SQL Query?]() Original publisher: [Read original article]() Author: Saurabh Dashora Published: 2026-03-04T03:14:28Z Content type: tutorial Language: en Sources: [System Design Codex]() Topics: [SQL](), [Databases](), [Parser](), [syntax]() Tags: [database](), [diagram](), [errors](), [execution](), [locks](), [rollback](), [sql](), [syntax]() ### AI overview This tutorial explains how an SQL query moves through a database. It covers transport and access checks, parsing and optimization into an execution plan, execution through the storage engine, and supporting components such as transactions, locks, buffering, and recovery. ### Source excerpt The Journey Through the DB ## Build Checkpoints For Your Agent Using Neon Snapshots DevFeed: [Build Checkpoints For Your Agent Using Neon Snapshots]() Original publisher: [Read original article]() Author: Andre Landgraf Published: 2025-09-16T22:52:22Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [API](), [Database](), [data](), [Serverless](), [Vibe coding](), [Database Migration]() Tags: [agent](), [agentic](), [agents](), [api](), [app](), [architecture](), [backups](), [code](), [coding](), [compare](), [database](), [disaster-recovery](), [feature](), [product](), [rollback](), [serverless](), [snapshots](), [storage](), [vibe-coding]() ### AI overview The article explains how Neon snapshots can provide checkpoints for agent-built applications. Because each checkpoint preserves the application code together with the corresponding database schema and data, users can compare versions and roll back to a consistent state. Neon's API, serverless Postgres architecture, and copy-on-write storage make this approach practical and cost-effective. ### Source excerpt You can now create Neon snapshots via API. This new capability isn't just useful for backups or disaster recovery, but also serves as a powerful building block for one of the most requested features in agentic platforms: versioning (or checkpoints). Neon's snapshots, built on our... ## App Hosting updates: rollbacks, SDK auto-configuration, and more DevFeed: [App Hosting updates: rollbacks, SDK auto-configuration, and more]() Original publisher: [Read original article]() Author: Julia Reid; Jeff Huleatt Published: 2025-03-11T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [hosting](), [Firebase](), [web applications](), [SDKs](), [configuration]() Tags: [app-hosting](), [config](), [feature](), [firebase](), [hosting](), [javascript](), [rollback](), [sdk](), [updates](), [web](), [web-apps]() ### AI overview Firebase's March update for App Hosting introduces instant rollbacks that restore a previous container image without rebuilding, along with automatic initialization of Firebase SDKs for web apps. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Firebase introduces a real-time Release Monitoring dashboard powered by Crashlytics DevFeed: [Firebase introduces a real-time Release Monitoring dashboard powered by Crashlytics]() Original publisher: [Read original article]() Author: Ryan McMorrow; Rosário Fernandes Published: 2024-02-22T00:00:00Z Content type: article Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [monitor](), [Mobile](), [Crashlytics](), [dashboards](), [real-time](), [benchmarking]() Tags: [android](), [app-quality](), [benchmarking](), [crashlytics](), [features](), [firebase](), [ios](), [launch](), [mobile](), [monitoring](), [real-time](), [release](), [rollback]() ### AI overview Firebase introduces a beta Release Monitoring dashboard in the Firebase console. Powered by Crashlytics, it provides real-time release metrics, crash-free session data, comparisons with up to two previous builds, and a table of new issues to support release decisions. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Next.js App Router Update DevFeed: [Next.js App Router Update]() Original publisher: [Read original article]() Author: Lee Robinson Published: 2023-06-22T14:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [App](), [React](), [Developer experience](), [migration]() Tags: [app](), [developer-experience](), [migration](), [next-js](), [performance](), [releases](), [rollback](), [routing]() ### AI overview The Next.js team outlines its priorities for the App Router, focusing on performance, stability, and developer education. The article explains its React-based architecture and supports incremental migration from the Pages Router, including per-route adoption and rollback. ### Source excerpt The Next.js team is focused on performance, stability, and developer experience for the upcoming months. ## Saga compensating actions design pattern DevFeed: [Saga compensating actions design pattern]() Original publisher: [Read original article]() Author: Emily Fortuna Published: 2023-05-02T07:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [distributed-systems](), [Microservice](), [Go Language](), [Java](), [Python](), [TypeScript]() Tags: [consistency](), [distributed-systems](), [go](), [how-to](), [java](), [long-running](), [microservices](), [python](), [rollback](), [typescript]() ### AI overview This tutorial explains the compensating actions design pattern for handling failures in distributed systems. It describes how services can perform forward operations and, when a later step fails, execute application-defined compensating actions to undo earlier state changes without restoring an entire database snapshot. It also explains how to implement the pattern in Temporal using Go, Java, Python, or TypeScript. ### Source excerpt An explanation of the Compensating Actions design pattern and how to implement it in Temporal using Go, Java, Python, or TypeScript. ## Updated Pluralsight Course - Managing Kubernetes Controllers and Deployments DevFeed: [Updated Pluralsight Course - Managing Kubernetes Controllers and Deployments]() Original publisher: [Read original article]() Author: Anthony Nocentino Published: 2021-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Kubernetes on Anthony Nocentino's Blog]() Topics: [Kubernetes](), [Pluralsight]() Tags: [administration](), [commands](), [configuration](), [containers](), [controllers](), [deployment](), [kubernetes](), [pluralsight](), [rollback](), [scale](), [techniques](), [training]() ### AI overview An updated Pluralsight course teaches how to select, deploy, and maintain applications with Kubernetes Controllers. It covers Deployments, ReplicaSets, DaemonSets, CronJobs, and Jobs, including updating, rolling back, and scaling deployments. ### Source excerpt My updated course "Managing Kubernetes Controllers and Deployments" is now available on Pluralsight here! If you want to learn about the course, check out the trailer here or if you want to dive right in check it out here! Learn how to deploy and maintain applications using Kubernetes Controllers. In this course you'll learn how to select a Controller for your workload, deploy it, and maintain your container-based applications in your Kubernetes cluster. ## Understanding the Concept of Virtual Time Using the Time Warp Algorithm DevFeed: [Understanding the Concept of Virtual Time Using the Time Warp Algorithm]() Original publisher: [Read original article]() Published: 2021-04-10T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Warp](), [distributed-systems](), [Algorithm](), [systems]() Tags: [algorithm](), [distributed-systems](), [rollback](), [synchronization](), [warp]() ### AI overview This tutorial explains virtual time in distributed systems and focuses on the lookahead-rollback approach used by the Time Warp algorithm. It describes virtual clocks, message timestamps, event ordering, causality, and how Time Warp relates to Lamport's logical clock. ### Source excerpt What is virtual time and why do we need it. As distributed systems have progressed and been adopted over the last decade, there have been numerous technologies in different segments like databases, caches, message queues, etc which are built on top of other frameworks which abstract away the difficulty of managing distributed systems... [Next page]()