# Upgrades Published articles for Upgrades. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Ubuntu 26.10 Set To Deliver Better Performance For Intel Core 3 Wildcat Lake DevFeed: [Ubuntu 26.10 Set To Deliver Better Performance For Intel Core 3 Wildcat Lake]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-15T15:34:07Z Content type: comparison Language: en Sources: [Phoronix]() Topics: [Ubuntu](), [Intel Core](), [intel](), [Hardware](), [Linux](), [SOC]() Tags: [comparison](), [core](), [desktop-linux](), [graphics](), [hardware](), [intel-core](), [kernel](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [nvme](), [open-source-graphics](), [performance](), [phoronix](), [phoronix-test-suite](), [release](), [soc](), [software](), [ubuntu](), [ubuntu-benchmarks](), [ubuntu-hardware](), [updates](), [upgrade](), [upgrades](), [wildcat-lake]() ### AI overview The article compares Ubuntu 26.04 LTS with Ubuntu 26.10 in development on a CHUWI UniBook equipped with an Intel Core 3 304 SoC, 8GB of RAM, and a 256GB NVMe SSD. It reports that Ubuntu 26.10's newer Linux kernel, Mesa graphics stack, and other software upgrades are expected to improve performance on Intel Wildcat Lake hardware. ### Source excerpt While Ubuntu 26.04 LTS is working fine out-of-the-box on new Intel Core 3 "Wildcat Lake" laptops like the CHUWI UniBook, next month's release of Ubuntu 26.10 will help deliver better performance out of these low-cost laptop options. ## Join Us: EF Protocol Reddit AMA - September 16th, 2026 DevFeed: [Join Us: EF Protocol Reddit AMA - September 16th, 2026]() Original publisher: [Read original article]() Author: Ethereum Foundation Protocol Cluster Published: 2026-09-09T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Protocol (disambiguation)](), [Formal verification]() Tags: [2026](), [community](), [development](), [ethereum](), [formal-verification](), [privacy](), [reddit](), [research-development](), [technical](), [upgrades]() ### AI overview The Ethereum Foundation announces a September 16, 2026 Reddit AMA with researchers and developers from its Protocol cluster. The discussion will cover Ethereum protocol development, including the Glamsterdam hard fork, Hegotá, post-quantum Ethereum, formal verification, privacy, client development, and related topics. ### Source excerpt Every year since January 2019, teams from the Ethereum Foundation have spent an afternoon or two on r/ethereum answering questions from the community. The format hasn't really changed: one thread, technical debates, detailed explanations, and community members asking whatever is on their mind. By now it is a tradition, and... ## Chainguard's Factory-Scale Automation for Toolchain Upgrades and Testing DevFeed: [Chainguard's Factory-Scale Automation for Toolchain Upgrades and Testing]() Original publisher: [Read original article]() Published: 2026-09-09T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [toolchain](), [Automation](), [Testing](), [Open Source](), [Go Language]() Tags: [automation](), [chainguard](), [go](), [open-source](), [security](), [testing](), [toolchain](), [upgrades]() ### AI overview Chainguard describes how its Factory uses automation to manage toolchain version selection, upgrades, builds, and testing across open source packages. The approach uses version streams and rebuilds packages with newer toolchain versions when builds and tests succeed, helping deliver updates quickly while maintaining reliability and security. ### Source excerpt See how Chainguard automates toolchain upgrades and testing to keep thousands of open source packages current, secure, and reliable at scale. ## How to Reclaim Excess SOL After Rent Reduction DevFeed: [How to Reclaim Excess SOL After Rent Reduction]() Original publisher: [Read original article]() Author: Solana Foundation Published: 2026-09-03T15:15:00Z Content type: tutorial Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Authorization](), [TypeScript]() Tags: [authorization](), [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [defi](), [developers](), [how-to](), [nfts](), [podcasts](), [solana](), [solana-ecosystem](), [technology](), [token](), [typescript](), [upgrades](), [web3]() ### AI overview This tutorial explains how to reclaim excess SOL caused by Solana rent reductions. It covers withdrawing surplus lamports from token accounts and mints with WithdrawExcessLamports, and implementing similar reclaim logic for program-owned PDAs. ### Source excerpt Rent on Solana has been Reduced. Every Account Is Now Over-Funded. Here's How to Reclaim Excess SOL. ## Closing the Governance Gap in Nutanix Kubernetes Platform Environments DevFeed: [Closing the Governance Gap in Nutanix Kubernetes Platform Environments]() Original publisher: [Read original article]() Author: Sachin Agarwal Published: 2026-08-24T18:04:51Z Content type: article Language: en Sources: [Nirmata]() Topics: [Kyverno](), [nutanix](), [Kubernetes](), [Platform Engineering]() Tags: [build](), [compliance](), [governance](), [kubernetes](), [kyverno](), [nutanix](), [other](), [platform-engineering](), [upgrades]() ### AI overview Nirmata Enterprise for Kyverno is certified to run on Nutanix Kubernetes Platform through the Nutanix Cloud Platform. The article explains how installing it from the NKP Partner Catalog integrates policy governance, enforcement, and upgrades into the platform without a separate pipeline. ### Source excerpt Kyverno on Nutanix Kubernetes Platform is now certified. Install Nirmata Enterprise for Kyverno from the NKP Partner Catalog, no separate pipeline. ## Resource and Inclusion Fee: Digging into Data DevFeed: [Resource and Inclusion Fee: Digging into Data]() Original publisher: [Read original article]() Author: Umberto Natale Published: 2026-08-21T15:34:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Transactions](), [Optimization](), [data]() Tags: [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [data](), [defi](), [nfts](), [optimization](), [podcasts](), [pricing](), [reports](), [solana](), [solana-ecosystem](), [transactions](), [upgrades](), [web3]() ### AI overview This article analyzes SGP-0003's proposed resource-aware base fee for Solana. It examines resource-request calibration, transaction fee effects across workloads, validator economics, and estimated SOL-burn changes, emphasizing that the burn figures are behavioral counterfactuals rather than forecasts. ### Source excerpt Here we dive into implications related to the SGP-0003 (namely resource and inclusion fee). ## Lowering Slot Time and Validator Economics DevFeed: [Lowering Slot Time and Validator Economics]() Original publisher: [Read original article]() Author: Umberto Natale Published: 2026-08-19T10:00:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Latency](), [Protocol (disambiguation)]() Tags: [blockchain](), [blockchain-technology](), [consensus](), [crypto-news](), [cryptocurrency](), [defi](), [infrastructure](), [latency](), [nfts](), [performance](), [podcasts](), [protocol](), [reports](), [solana](), [solana-ecosystem](), [upgrades](), [web3]() ### AI overview Solana plans to reduce slot times from 400 ms to 200 ms. The article examines possible effects on latency, arbitrage, sandwich MEV, validator rewards and costs, voting frequency, and consensus performance, while noting that some impacts require empirical mainnet monitoring. ### Source excerpt Solana will reduce its slot times from 400ms to 200ms. This change will make the protocol more competitive in terms of latency. Here we explore some possible implication on validators economic. ## v1 Transactions and the ALT Trade-off DevFeed: [v1 Transactions and the ALT Trade-off]() Original publisher: [Read original article]() Author: Umberto Natale Published: 2026-08-17T00:00:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Transactions](), [benchmarking](), [SDKs]() Tags: [blockchain](), [blockchain-technology](), [crypto-news](), [cryptocurrency](), [defi](), [nfts](), [podcasts](), [reference](), [reports](), [rpc](), [sdks](), [serialization](), [solana](), [solana-ecosystem](), [transactions](), [upgrades](), [web3]() ### AI overview Solana is introducing the v1 transaction format with a maximum serialized size of 4,096 bytes, replacing Account Lookup Table resolution with larger inline transaction capacity. The analysis finds that current workloads are broadly compatible with the new envelope, while the unchanged 64-account limit may remain a constraint for some applications. ### Source excerpt Solana is introducing a new transaction format (v1) alongside an increase of the maximum transaction size from 1232 bytes to 4096 bytes. The v1 format aims to unlock new possibilities on-chain. This is done trading-off Account Lookup Tables (ALT) usage. In this research we explore in details the current usage of ALTs, alongside implications of removing them. ## How EKS is simplifying Kubernetes cluster lifecycle management DevFeed: [How EKS is simplifying Kubernetes cluster lifecycle management]() Original publisher: [Read original article]() Author: Spyros Angelopoulos Published: 2026-08-01T15:00:00Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Amazon Elastic Kubernetes Service](), [Kubernetes](), [Availability](), [Deployment]() Tags: [availability](), [aws-marketplace](), [cloud-services](), [deployment](), [devops](), [kubernetes](), [lifecycle](), [post-contributed](), [sponsor-aws-marketplace](), [sponsored-post-contributed](), [upgrades]() ### AI overview The article describes the operational challenges of Kubernetes upgrades and EKS efforts to make cluster lifecycle management easier. It highlights Extended Support, which broadens the availability of each Kubernetes version to 26 months, giving organizations more time to validate and schedule upgrades. ### Source excerpt Kubernetes moves at a pace of three minor version releases per year, and staying current is not optional if you The post Kubernetes upgrades don't have to break things: How EKS is making cluster lifecycle management simpler and safer appeared first on The New Stack. ## Kubernetes 1.35: 10 new Alpha features DevFeed: [Kubernetes 1.35: 10 new Alpha features]() Original publisher: [Read original article]() Author: Nigel Douglas Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Kubernetes](), [autoscaling](), [Hardware](), [Release notes](), [Security]() Tags: [ai](), [autoscaling](), [hardware](), [kubernetes](), [release-notes](), [resource](), [upgrades]() ### AI overview This article examines ten new Alpha features in Kubernetes 1.35. It highlights Dynamic Resource Allocation improvements for AI-oriented workloads and hardware such as GPUs and FPGAs, along with mixed-version upgrade proxying, resource utilization improvements, and other emerging platform capabilities. ### Source excerpt Discover Kubernetes 1.35's top 10 new Alpha features, including major DRA upgrades for AI hardware, mixed-version upgrade proxying, CSI security improvements, node feature declarations, smarter autoscaling, gang scheduling, in-place vertical scaling, and new pod restart actions. ## The true cost of Kubernetes release support for Platform Engineers DevFeed: [The true cost of Kubernetes release support for Platform Engineers]() Original publisher: [Read original article]() Author: Bruce Gain Published: 2026-07-23T05:40:01Z Content type: comparison Language: en Sources: [Platform Engineering Blog]() Topics: [Kubernetes](), [Platform Engineering](), [Cloud](), [Amazon Web Services](), [Amazon EKS](), [Azure](), [rancher]() Tags: [amazon-eks](), [aws](), [azure](), [cloud](), [comparison](), [cost](), [cves](), [kubernetes](), [operational](), [platform](), [platform-engineering](), [private-cloud](), [red-hat](), [releases](), [security](), [support](), [testing](), [upgrades](), [vmware-cloud-foundation](), [vulnerabilities]() ### AI overview This article compares the operational and financial trade-offs of Kubernetes release support models. It explains that the CNCF's 14-month support window requires frequent upgrades, creating testing, coordination, maintenance, and service-disruption risks. Hyperscalers such as Amazon EKS, Google GKE, and Azure AKS offer paid extended support, while VMware Cloud Foundation provides 24 months of standard support without incremental fees and Red Hat OpenShift offers a 36-month support window. ### Source excerpt Compare the true cost and operational trade-offs of Kubernetes extended support fees from hyperscalers (AWS, GCP, Azure) versus the longer, predictable maintenance cycles of VMware VCF and other enterprise distributions. ## SpaceDeck X July devlog: upgrades, backgrounds, and more DevFeed: [SpaceDeck X July devlog: upgrades, backgrounds, and more]() Original publisher: [Read original article]() Author: Stanko Published: 2026-07-23T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [Development](), [Website]() Tags: [customization](), [game-dev](), [pixel-art](), [redesign](), [steam](), [updates](), [upgrades]() ### AI overview A July development log for SpaceDeck X describes progress toward a Steam release, including a new upgrades system and library, redesigned UI panels, ship weapon and characteristic tweaks, decorative backgrounds and shadows, run-history work, and controller-button customization. ### Source excerpt I've been developing SpaceDeck X since December last year. It started as me playing with a random framework I found fun, and it grew so much that I'm now working towards releasing it on Steam. I kept a devlog on Itch, but I feel like it is time to bring it to my own website. Especially considering that these updates are exclusive to the Steam version. I have a pretty clear vision for the release, and lately I've made amazing progress. Here are the major things I've made, in no particular order. Upgrades system # The new upgrades system was brewing in my head for a long time. Honestly, I thought it would take me longer to implement it, but once I started, I got in the zone and built a completely new system. This is the new upgrades selection screen: Compare it to the old one: Upgrades library # Upgrades got their own library, so players can inspect and learn about all of them. In two days I managed to draw 44 upgrade icons. Some of them I just winged and now I'm retrofitting them to the actual game upgrades. Redesigned UI panels # After making new upgrade cards, I got an urge to redesign some of the game's UI. I'm trying to avoid scope creep, but I had to create a way for the player to see their upgrades, so I decided to give a facelift to the deck panel as well. You can open both panels by holding Tab in the boss fight: And they show automatically in the pause menu: Ships # Ships are not brand new, but in the last few weeks I tweaked their specific weapons and characteristics. It is still a work in progress, but all ships are functional and have their own quirks. Backgrounds and shadows # These are purely decorative, but I think they elevate the experience a lot. These background objects add more visual depth. They also change every few levels, giving the player a better sense of progression. For now I created two sets of backgrounds (the gray tech-industrial one and an Aztec/Protoss-inspired one). The plan is to have four or five for the full game. These are quite ## Scale Faster with Managed Weaviate: Now in Public Preview on DigitalOcean DevFeed: [Scale Faster with Managed Weaviate: Now in Public Preview on DigitalOcean]() Original publisher: [Read original article]() Author: Waverly Swinton Published: 2026-07-09T19:08:52Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Cloud](), [Databases](), [Retrieval Augmented Generation (RAG)](), [autoscaling](), [Self-hosted](), [GraphQL](), [gRPC]() Tags: [autoscaling](), [configuration](), [database](), [databases](), [digitalocean](), [graphql](), [high-availability](), [hosting](), [infrastructure](), [preview](), [product-updates](), [real-time](), [rest](), [retrieval](), [run](), [security](), [storage](), [upgrades](), [workflows]() ### AI overview DigitalOcean has placed Managed Weaviate into public preview. The service provides fully managed Weaviate clusters with automated backups, security patching, version upgrades, high availability, and storage autoscaling, with pricing starting at $20 per month. ### Source excerpt Production Weaviate in minutes, managed by DigitalOcean. Starting at $20/month. Vector databases have become a core piece of the AI application stack. Whether you're building retrieval-augmented generation (RAG), semantic search, agentic workflows and memory, or similarity-based recommendations, you need a vector store that's reliable, fast, and doesn't require a dedicated ops engineer to keep running. Weaviate has become a critical part of that stack -- its open-source AI-native vector database powers semantic search, RAG, and agentic workflows for thousands of companies. Self-hosting Weaviate is doable but it comes at a cost. You're on the hook for backups, version upgrades, security patches, high availability configuration, and storage scaling. That's real time and real engineering capacity that isn't going toward your product. Managed alternatives from larger cloud vendors exist, but they often come with per-query fees, per-dimension surcharges, and pricing models that are difficult to predict as usage grows. Today, we're announcing that Managed Weaviate is now in public preview on DigitalOcean, offering an easy way for you to run Weaviate in production, at a price that makes sense from day one. The easiest way to run Weaviate in production Managed Weaviate on DigitalOcean handles the operational work so you don't have to. Provision a fully managed Weaviate cluster directly from the DigitalOcean control panel. From there, automated backups, security patching, version upgrades, high availability, and storage autoscaling are handled for you. Full Weaviate client compatibility via GraphQL, REST, and gRPC on port 443 means your existing code works without modification. This means you get Weaviate's full capabilities -- semantic and hybrid search, RAG pipelines, and support for agent-driven workflows -- without spending engineering time on the infrastructure beneath them. Predictable pricing, starting at $20/month We built Managed Weaviate with flat, predictable monthly ## Track customer loyalty points with durable workflows DevFeed: [Track customer loyalty points with durable workflows]() Original publisher: [Read original article]() Author: Cecil Phillip Published: 2026-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [account](), [business logic](), [Database](), [real-time](), [locking](), [retry](), [service](), [upgrade](), [Mobile]() Tags: [account](), [business-logic](), [customer](), [database](), [locking](), [loyalty](), [loyalty-points](), [mobile](), [process](), [query](), [real-time](), [retry](), [service](), [temporal](), [temporal-concepts](), [upgrades](), [workflows]() ### AI overview This article explains how to track customer loyalty points with durable Entity Workflows in Temporal. Each customer has a persistent workflow that maintains points, tier status, and activity history, while Signals handle accruals, Updates validate redemptions, and Queries read current balances. ### Source excerpt Track loyalty points with durable Entity Workflows in Temporal. See how to handle accruals, tier upgrades, and redemptions for each customer. ## Prorated Billing Explained: How Proration Works for SaaS Subscriptions DevFeed: [Prorated Billing Explained: How Proration Works for SaaS Subscriptions]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-06-01T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [stripe]() Tags: [billing](), [examples](), [implementation](), [pitfalls](), [saas](), [subscription-billing](), [subscriptions](), [upgrades]() ### AI overview A guide to prorated billing for SaaS subscriptions, explaining how partial-period charges and credits are calculated for upgrades, downgrades, seat changes, trial conversions, and cancellations. It includes calculation examples and implementation pitfalls. ### Source excerpt Prorated billing for SaaS - how proration is calculated on upgrades, downgrades, mid-cycle changes, and add-on seats, with examples and common implementation pitfalls. ## Goodbye, Ubuntu 20.04 (netlab 26.05) DevFeed: [Goodbye, Ubuntu 20.04 (netlab 26.05)]() Original publisher: [Read original article]() Published: 2026-05-18T05:43:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Ubuntu](), [Python 3.8](), [releases](), [Python 3.10](), [networking](), [qemu]() Tags: [end-of-life](), [github](), [guide](), [issue](), [netlab](), [networking](), [python-3-10](), [python-3-8](), [qemu](), [release](), [ubuntu](), [upgrade](), [upgrades]() ### AI overview The netlab 26.05 release drops support for Python 3.8 and vanilla Ubuntu 20.04, requiring Python 3.10 or newer. The article discusses compatibility with older containerlab releases and cautions that Ubuntu 24.04 upgrades may still have quirks. ### Source excerpt netlab release 26.05 is out. I'll write about its highlights tomorrow; today, I want to focus on one of its breaking changes: netlab no longer works with Python 3.8 (which reached end-of-life in October 2024), so you can no longer install it on a vanilla Ubuntu 20.04 (which reached end of standard support a year ago). We wanted to get rid of old Python versions for ages, but never did because Ubuntu 20.04 shipped with Python 3.8, and many netlab early adopters installed it on Ubuntu 20.04 (and the last thing a networking engineer wants is wasting time with upgrades, right?). Read more ... ## On-Demand Subscriptions: A Hybrid Billing Model that Works DevFeed: [On-Demand Subscriptions: A Hybrid Billing Model that Works]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-05-14T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [backends]() Tags: [add-ons](), [billing](), [how-to](), [payments](), [saas](), [subscription-billing](), [subscriptions](), [upgrades]() ### AI overview This article explains on-demand subscriptions, a hybrid billing model that combines recurring charges with optional one-off charges using the same saved payment mandate. It describes use cases including trials, upgrades, add-ons, overage, and credit top-ups, and outlines implementation on Dodo Payments. ### Source excerpt On-demand subscriptions combine recurring billing with on-demand charges so you can run trials, upsells, and tiered upgrades on a single saved payment method. ## Next.js May 2026 security release DevFeed: [Next.js May 2026 security release]() Original publisher: [Read original article]() Author: Jimmy Lai Published: 2026-05-07T13:00:00Z Content type: news Language: en Sources: [Vercel News]() Topics: [Next.js](), [Security](), [Vulnerabilities](), [React](), [Authorization](), [Caching](), [WebSocket]() Tags: [authorization](), [caching](), [next-js](), [react](), [release](), [router](), [security](), [upgrade](), [upgrades](), [vulnerabilities](), [vulnerability]() ### AI overview Vercel announces a coordinated Next.js security release addressing 13 advisories involving denial of service, middleware and proxy authorization bypasses, server-side request forgery, cache poisoning, and cross-site scripting. The release includes an upstream React Server Components vulnerability tracked as CVE-2026-23870. Affected users are advised to upgrade to patched React and Next.js versions immediately. ### Source excerpt Summary We have shipped a coordinated security release for Next.js addressing 13 advisories across denial of service, middleware and proxy bypass, server-side request forgery, cache poisoning, and cross-site scripting. One advisory addresses an upstream React Server Components vulnerability tracked as CVE-2026-23870. Recommended actions Patched versions are available for both React and Next.js, and all affected users should upgrade immediately. Impact The release addresses the following advisories: Middleware and proxy bypass Affects applications that rely on middleware.js or proxy.js for authorization. High: Auth bypass via App Router segment-prefetch URL High: App Router segment-prefetch bypass, incomplete fix follow-up High: Pages Router i18n default-locale path bypasses proxy authorization High: Bypass via dynamic route parameter injection Low: Middleware redirects can be cache-poisoned Denial of service Affects applications using Server Functions, Partial Prerendering with Cache Components, or the Image Optimization API. High: DoS in React Server Components (tracked upstream as CVE-2026-23870) High: DoS via connection exhaustion in applications using Cache Components Moderate: DoS via the Image Optimization API Server-side request forgery Affects applications that handle WebSocket upgrade requests. High: SSRF in applications using WebSocket upgrades Cache poisoning Affects applications with caching layers in front of React Server Component responses. Moderate: Cache poisoning in React Server Component responses Low: Cache poisoning via collisions in RSC cache-busting Cross-site scripting Affects applications using CSP nonces in App Router, or beforeInteractive scripts that consume untrusted input. Moderate: XSS in App Router applications using CSP nonces Moderate: XSS in beforeInteractive scripts with untrusted input Resolution These vulnerabilities are addressed by the patched releases of React and Next.js. Patching is the only complete mitigation, and all aff ## Expansion Revenue: How to Grow Without Acquiring New Customers DevFeed: [Expansion Revenue: How to Grow Without Acquiring New Customers]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-12T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [.NET Conf]() Tags: [growth](), [how-to](), [pricing](), [retention](), [saas](), [saas-metrics](), [upgrades](), [usage-based-billing]() ### AI overview This guide explains expansion revenue for SaaS businesses, including how upgrades, additional seats, higher usage, add-ons, cross-selling, and premium tiers can grow recurring revenue from existing customers. It also discusses pricing, billing infrastructure, and net revenue retention. ### Source excerpt Learn how SaaS companies increase expansion revenue through better pricing, seat growth, usage-based billing, and upgrade design without depending only on new customer acquisition. ## Cockroach Labs announces CockroachDB capabilities for AI agents DevFeed: [Cockroach Labs announces CockroachDB capabilities for AI agents]() Original publisher: [Read original article]() Author: Lakshmi Kannan Published: 2026-03-25T00:00:00Z Content type: release Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Cockroach Labs](), [MCP Server](), [Databases](), [Model Context Protocol](), [Agent Skills](), [AI research agents](), [Back end](), [Availability](), [Latency]() Tags: [agent-skills](), [agents](), [ai](), [ai-agents](), [auditability](), [backend](), [clusters](), [cockroach-labs](), [cockroachdb](), [database](), [distributed](), [mcp](), [mcp-server](), [operations](), [provisioning](), [scale](), [upgrades]() ### AI overview Cockroach Labs announces capabilities intended to make CockroachDB agent-ready, including a fully managed MCP Server, a redesigned ccloud CLI, and a public library of CockroachDB Agent Skills. The article describes requirements such as structured interfaces, scoped permissions, and auditability for agents operating across the database lifecycle. ### Source excerpt Today Cockroach Labs is announcing new capabilities that make CockroachDB agent-ready, giving AI agents a secure, structured way to work with your database. ## PostgreSQL 18 Upgrades for AI-Era Workloads and Operations DevFeed: [PostgreSQL 18 Upgrades for AI-Era Workloads and Operations]() Original publisher: [Read original article]() Author: Sebastian Insausti Published: 2026-03-20T08:00:00Z Content type: article Language: en Sources: [SeveralNines]() Topics: [PostgreSQL](), [Software as a service](), [Transactions]() Tags: [ai](), [aio](), [async](), [latency](), [maintenance](), [performance](), [postgresql](), [postgresql-18](), [replication](), [storage](), [upgrades](), [upgrades-patches]() ### AI overview This article examines PostgreSQL 18 upgrades for transaction, analytics, SaaS, event-data, and vector-search workloads. It focuses on operational improvements including asynchronous I/O, safer upgrades that retain optimizer statistics, improved multi-column indexes, UUIDv7 support, and logical replication enhancements. ### Source excerpt Today, we're asking PostgreSQL to do more and more, like handling both transactions and analytics, powering huge SaaS platforms, managing event data, and even dipping into AI-related tasks like vector search. This intense pressure highlights some pain points: slow, unpredictable reads, rigid indexing, complex setups, and risky major upgrades. PostgreSQL 18 directly addresses these real-world [...] The post PostgreSQL 18 Upgrades for AI-Era Workloads and Operations appeared first on Severalnines. ## Announcing the Platform Team at EF DevFeed: [Announcing the Platform Team at EF]() Original publisher: [Read original article]() Author: Josh Rudolf Published: 2026-02-17T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Protocol (disambiguation)](), [systems](), [Network]() Tags: [dashboards](), [development](), [ethereum](), [metrics](), [network](), [protocol](), [research-development](), [systems](), [upgrades]() ### AI overview The Ethereum Foundation announces a new Platform team focused on strengthening Ethereum as an integrated L1 and L2 system. Its responsibilities include protocol development, ecosystem-focused research, roadmap and fork planning, protocol integration, strategy, network-health metrics, and clearer public dashboards. ### Source excerpt Platform is a new team inside the EF with one goal: Deliver the strongest possible Ethereum platform, where L1 and L2s are best positioned to support users, apps, and all organizations building on Ethereum. This requires improving the L1 \ L2 relationship, so that we grow as a mutually... ## AutoCon4 Takeaway: Flock9 Announced DevFeed: [AutoCon4 Takeaway: Flock9 Announced]() Original publisher: [Read original article]() Author: Rick Donato Published: 2025-11-28T10:00:55Z Content type: release Language: en Sources: [Packet Coders - Learn Network Automation]() Topics: [Automation](), [Artificial Intelligence](), [Network](), [Model Context Protocol]() Tags: [ai](), [announcements](), [automation](), [blog](), [mcp](), [network](), [product](), [upgrades]() ### AI overview Flock9 has announced major upgrades that bring Netpicker and Slurpit together under one product catalog. The update adds AI-assisted automation, Nautobot integration, workflow automation, a multi-instance service manager, and Slurp'it MCP access to network data. ### Source excerpt One of the big announcements from AutoCon4 last week came from the team behind Netpicker and Slurpit. They have now released major upgrades, and have aligned the product catalog under the umbrella of the Flock9 platform, bringing Netpicker and Slurpit even closer together. The TL;DR Netpicker AI Assistant Netpicker ## Waiting for PostgreSQL 19 - Sequence synchronization in logical replication. DevFeed: [Waiting for PostgreSQL 19 - Sequence synchronization in logical replication.]() Original publisher: [Read original article]() Author: depesz Published: 2025-11-11T12:24:23Z Content type: tutorial Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [Replication](), [Sequences]() Tags: [benchmark](), [logical](), [pg19](), [postgresql](), [psql](), [publications](), [replication](), [sequence](), [sequences](), [synchronization](), [uncategorized](), [upgrade](), [upgrades](), [waiting]() ### AI overview This article demonstrates PostgreSQL 19's planned sequence synchronization for logical replication. It sets up source and destination databases, tests sequence synchronization, finds that resynchronization must be manually invoked, and reports that synchronizing 10,000 sequences took about one second in the author's test. ### Source excerpt First, on 9th of October 2025, Amit Kapila committed patch: Add "ALL SEQUENCES" support to publications. This patch adds support for the ALL SEQUENCES clause in publications, enabling synchronization/replication of all sequences that is useful for upgrades. Publications can now include all sequences via FOR ALL SEQUENCES. psql enhancements: \d shows publications for ... Continue reading "Waiting for PostgreSQL 19 - Sequence synchronization in logical replication." [Next page]()