# maintenance Acts that prevent equipment or IoT-device failure or malfunction, or restore operating capability. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot 20150208 release DevFeed: [Libreboot 20150208 release]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [maintenance]() Tags: [article](), [bios](), [canoeboot](), [coreboot](), [free-software](), [libre](), [libreboot](), [opensource](), [release](), [uefi]() ### AI overview Libreboot 20150208 is a maintenance release based on r20150126. It adds or updates support for several Lenovo ThinkPad and Apple MacBook models, removes ME/AMT on supported systems, improves documentation, and updates build and GRUB background scripts. ### Source excerpt Article: Libreboot 20150208 release Web link: https://libreboot.org/news/libreboot20150208.html ## Libreboot Build System Audit 3 DevFeed: [Libreboot Build System Audit 3]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [audit](), [maintenance](), [Error Handling](), [Shell]() Tags: [audit](), [audits](), [bios](), [bug](), [build-system](), [canoeboot](), [complexity](), [coreboot](), [efficiency](), [error-handling](), [free-software](), [integrity](), [libre](), [libreboot](), [opensource](), [safety](), [threading](), [uefi]() ### AI overview This article reports on Libreboot Build System Audit 3, focusing on the lbmk build system. It describes improved error handling, bug fixes, efficiency improvements, reduced complexity, stronger vendor-file integrity checks, and broader use of multithreading. The audit reduced the build system from 2,644 to 1,744 shell-script source lines compared with the previous audit, without reducing functionality. ### Source excerpt Article: Libreboot Build System Audit 3 Web link: https://libreboot.org/news/audit3.html ## The Autonomous Dumbledore DevFeed: [The Autonomous Dumbledore]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-04-25T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [API](), [Job](), [test](), [maintenance](), [Code]() Tags: [api](), [bugs](), [engineering](), [feature](), [fetch](), [job](), [maintenance](), [news](), [running](), [scheduled](), [test](), [tests](), [web-frontend]() ### AI overview An intern at Khan Academy describes the Autonomous Dumbledore, a system that monitors PSAT score-linking endpoints through recurring tests and automatically enables or disables the related feature based on recent results. ### Source excerpt By Evy Kassirer When I arrived at Khan Academy to start my internship on the Official SAT Practice ... Read more ## How to Build a Self-Maintaining Knowledge Base With AI Agents DevFeed: [How to Build a Self-Maintaining Knowledge Base With AI Agents]() Original publisher: [Read original article]() Author: Janeera Published: 2026-08-31T13:15:12Z Content type: tutorial Language: en Sources: [Knowledge Management Tips, Best Practices and More]() Topics: [Documentation](), [Artificial Intelligence](), [maintenance]() Tags: [agents](), [ai](), [ai-agents](), [automate](), [documentation](), [how-to](), [knowledge-base](), [knowledge-base-software](), [maintenance]() ### AI overview This tutorial explains how AI agents can help maintain a knowledge base by detecting outdated content, obsolete links, screenshot mismatches, and missing updates. It describes a self-maintaining approach in which agents automate maintenance tasks while people supervise the system and assess its results. ### Source excerpt A single update to your product means countless documents in your knowledge base ... The post How to Build a Self-Maintaining Knowledge Base With AI Agents appeared first on Document360. ## 【etcd】写入路径深读：Txn、mod revision 与 quota/alarm DevFeed: [【etcd】写入路径深读：Txn、mod revision 与 quota/alarm]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Back end](), [Raft](), [Remote Procedure Call (RPC)](), [maintenance]() Tags: [alarm](), [apiserver](), [applied-index](), [apply](), [batch](), [bbolt](), [committed-index](), [compaction](), [defrag](), [distributed](), [errcompacted](), [etcd](), [follower](), [k8s](), [kubernetes](), [mod-revision](), [nospace](), [quota](), [revision](), [txn](), [v3-5](), [v3-5-33]() ### AI overview This tutorial explains the etcd v3.5.33 write path from gRPC requests through Raft proposal, quota checks, MVCC apply, and ModRevision assignment. It also describes proposal backpressure, backend quota accounting, and how a NOSPACE alarm blocks writes while reads, deletes, and maintenance operations can continue. ### Source excerpt 走读 etcd v3.5.33 写入路径：raftRequest 背压、Txn compare/mod 与 ModRevision 分配、backend quota 与 NOSPACE alarm 如何把集群推入只读。 ## CocoaPods Deprecation Notice for OpenTelemetry Swift DevFeed: [CocoaPods Deprecation Notice for OpenTelemetry Swift]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-20T14:05:37Z Content type: release Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [cocoapods](), [Swift](), [swift-package-manager](), [migration](), [Package manager](), [maintenance](), [Maintainers]() Tags: [cocoapods](), [maintenance](), [migration](), [opentelemetry](), [release](), [releases](), [swift](), [swift-package-manager]() ### AI overview OpenTelemetry Swift maintainers plan to deprecate CocoaPods support for the opentelemetry-swift and opentelemetry-swift-core pods as CocoaPods moves into maintenance mode. Swift Package Manager is the recommended installation method, and existing CocoaPods users are encouraged to plan migration. ### Source excerpt As it was announced via CocoaPods Support Plan and via CocoaPods Spec Repository, CocoaPods is transitioning their project to maintenance mode, and cocoapods trunk is going to be read-only in a few months. The OpenTelemetry Swift maintainers are planning to deprecate CocoaPods support for all the pods published under opentelemetry-swift and opentelemetry-swift-core. Swift Package Manager (SPM) is now the recommended and preferred installation method for all new integrations. We encourage existing CocoaPods users to begin planning a migration to SPM. ## The future of the Keycloak Discourse forum DevFeed: [The future of the Keycloak Discourse forum]() Original publisher: [Read original article]() Author: GR Patil, Niko Köbler Published: 2026-07-20T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [ai-coding](), [dev-tools](), [maintenance](), [Security]() Tags: [ai](), [ai-coding](), [developer-tools](), [idm](), [kerberos](), [keycloak](), [ldap](), [maintenance](), [openid-connect](), [saml](), [security](), [sso]() ### AI overview The Keycloak project announces that it will wind down its Discourse forum. The article explains the forum's historical role, increased use of AI coding assistants and search-like developer tools, reduced forum activity, and the maintenance effort required to keep it open. ### Source excerpt The Keycloak project has always relied on open, searchable, community-owned discussion. Over the years, the Keycloak Discourse forum has been an important part of that: a place where users could ask configuration questions, share migration experiences, debug integrations, and find answers from people who had solved similar problems before. After a lot of consideration, we have decided to wind down the Keycloak Discourse forum. This is not a decision we are taking lightly. The forum contains many years of useful community knowledge, and we recognize the role it has played for Keycloak users. We also recognize that previous changes to the forum caused disruption. For that reason, we want to explain why we are making this change, how it will happen, when it will happen, and where the community should go next. Why we are making this change In June 2023, the Keycloak maintainers decided to sunset Discourse as one of the project's communication channels. That decision was met with strong feedback from the community. Many users explained that Discourse filled an important role that was not fully covered by mailing lists, GitHub Discussions, or chat. After listening to that feedback, we reactivated Discourse in October 2023. In the years since, the way developers seek help has changed. More and more Keycloak users now turn first to AI coding assistants and search-like developer tools when they need help configuring Keycloak, troubleshooting integrations, or understanding errors. Those tools have almost certainly learned from many of the public sources the community has created over the years, including the Discourse forum, GitHub Discussions, mailing lists, documentation, blog posts, and issue trackers. That shift has changed the role of a community forum. The old model depended on a steady flow of new questions, answers, corrections, and follow-up discussion. Without that activity, the forum risks becoming a stale support archive rather than a healthy community space. Keep ## How to Automate CockroachDB Operations with AI Using Cockroach University DevFeed: [How to Automate CockroachDB Operations with AI Using Cockroach University]() Original publisher: [Read original article]() Author: Nathan Zamecnik Published: 2026-07-13T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [Agent Skills](), [Artificial Intelligence](), [maintenance](), [Claude Code](), [Disaster Recovery](), [Security](), [observability]() Tags: [agent-skills](), [agents](), [ai-agents](), [claude-code](), [cockroachdb](), [disaster-recovery](), [maintenance](), [observability](), [security]() ### AI overview The article describes CockroachDB Agent Skills, a public repository of machine-executable operational workflows that AI agents such as Claude Code and Cursor can use. It also introduces three Cockroach University courses covering rolling restarts, encryption at rest, and planned node maintenance, along with a free trial of the CockroachDB Training Subscription. ### Source excerpt AI agents aren't just changing how applications interact with databases, they're changing how teams operate them. ## CTRL-OS 26.05 Released! DevFeed: [CTRL-OS 26.05 Released!]() Original publisher: [Read original article]() Author: blitz Published: 2026-07-10T12:35:43Z Content type: release Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Linux](), [maintenance](), [Security](), [cyber resilience act]() Tags: [announcements](), [cyber-resilience-act](), [infrastructure](), [linux](), [maintenance](), [release](), [sboms](), [security]() ### AI overview CTRL-OS 26.05, a downstream distribution of NixOS, has been released. The release provides a five-year lifecycle model, beginning with co-maintenance while NixOS has community support and moving to stability maintenance afterward. CTRL-OS monitors and backports security fixes for a core package set, with commercial subscriptions supporting SLAs and custom package sets. The project also describes its role in helping embedded Linux products address long-term vulnerability patching and EU Cyber Resilience Act requirements. ### Source excerpt Welcome to the latest CTRL-OS update! Find the last update from April here. If you don't know yet, CTRL-OS is a downstream distribution of NixOS designed to extend the release lifecycle to 5 years. It gives you a stable foundation with commercial support so you can build your products without having to maintain the packages you depend on. CTRL-OS 26.05 Released! The CTRL-OS 26.05 release is finally out. You can find the release blog post on our website. Or head over to our technical documentation and try it out. As long as NixOS 26.05 has community support, CTRL-OS 26.05 will be in the co-maintenance phase. In this phase, we will monitor our supported package set and contribute any security fixes back to NixOS. After community support ends, we enter the stability phase, and maintenance shifts completely to us. We've detailed this model on our blog. As of now, we support a small but useful package set. We'll share more details here soon, but our goal is to cover the usual packages you deploy on a server or embedded system, i.e., that dusty plastic box in the corner that quietly does its job for years. We actively monitor and backport CVEs for a core set of packages. To fund this work, commercial subscriptions provide SLA guarantees and cover custom package sets. While we aim to stay very close to NixOS 26.05, we will pull in important security fixes quickly to keep our SLAs. This creates a divergence that will automatically resolve itself once the security fixes make it to the NixOS release branch as well. Finally, to avoid a maintenance burden for the community, our CTRL-OS 26.05 release is lightly branded. By making it easy to identify a CTRL-OS system via nix-env -m, we ensure that bug reports originating from CTRL-OS users don't accidentally get filed against upstream NixOS, respecting the time and effort of upstream maintainers. No Cyber Resilience Act (CRA) Worries With the EU's CRA requirements taking effect this September, shipping embedded Linux products is ## Osmocom.org Servers - server outage of host3.osmocom.org DevFeed: [Osmocom.org Servers - server outage of host3.osmocom.org]() Original publisher: [Read original article]() Author: laforge Published: 2026-07-06T18:58:49Z Content type: news Language: en Sources: [Open Source Mobile Communications: News]() Topics: [servers](), [Debian](), [maintenance](), [upgrade](), [Jenkins]() Tags: [bug](), [debian](), [hosting](), [issue](), [jenkins](), [maintenance](), [outage](), [server](), [servers](), [tracker](), [update](), [upgrade]() ### AI overview Osmocom.org reports an outage affecting host3.osmocom.org during routine maintenance for a Debian upgrade. The host, which primarily serves Jenkins, downloads, and people subdomains, has fully recovered. ### Source excerpt We're currently experiencing some troubles during routine maintenance (Debian upgrade) of host3.osmocom.org, which is primarily hosting jenkins.osmocom.org, downloads.osmocom.org and people.osmocom.org. We ask for your patience while we try to resolve the situation. Update: host3 has fully recovered. ## Incremental Maintenance DevFeed: [Incremental Maintenance]() Original publisher: [Read original article]() Published: 2026-05-14T01:53:09Z Content type: opinion Language: en Sources: [Blogs on Ryan Harter]() Topics: [maintenance](), [Dependency injection](), [implementation](), [screen](), [App]() Tags: [core](), [dependencies](), [dependency-injection](), [incremental](), [maintenance](), [patterns](), [product](), [screen]() ### AI overview An opinion article about incremental maintenance in a large, aging application. It argues that small refactoring choices can reduce entrenched patterns, using dependency injection to keep feature-gating details out of a monolithic tab-host screen. ### Source excerpt I recently reviewed some code at work that made me pause. The change affected a part of the codebase that we affectionately call "The Monolith", which is some of the oldest code in our 16 year old app. While there are reasonable arguments that it's hard to tease apart this older hairball of code, there are often small choices that can either move you closer to the decoupled promised land, or further entrench you in bad patterns. ## What Happened When We Treated AI Like an Engineering Teammate DevFeed: [What Happened When We Treated AI Like an Engineering Teammate]() Original publisher: [Read original article]() Author: Global Technology Published: 2026-04-28T13:23:51Z Content type: opinion Language: en Sources: [McDonald's Technical Blog - Medium]() Topics: [Artificial Intelligence](), [AI Engineering](), [maintenance](), [Security](), [Cloud](), [test-coverage](), [Documentation](), [Framework]() Tags: [agent](), [ai](), [ai-agent](), [ai-engineering](), [autonomous](), [cloud](), [development](), [documentation](), [maintenance](), [platform-engineering](), [security](), [software-engineering](), [test-coverage](), [the-result](), [velocity]() ### AI overview The Restaurant Topology Management team used an AI-powered, agent-based engineering assistant within its development workflows to handle repetitive maintenance work, including configuration updates, security patches, framework modernization, test coverage, and documentation. The article reports 20% faster sprint velocity, security updates completed twice as fast, and modernization delivered up to 10 times faster. ### Source excerpt How an AI engineering assistant boosted sprint velocity by 20% and modernized services up to 10x faster. by: Sumedha Shenoy, Director, Engineering Tech Lead, and Kamal Jackson, Sr Manager, Engineering Tech Lead Quick Bytes: A growing backlog of essential but repetitive "glue work" was slowing the Restaurant Topology Management (RTM) team's ability to modernize and deliver new features By treating an AI engineering assistant as an autonomous teammate -- not a chatbot -- the team offloaded end-to-end maintenance tasks at scale The result was 20% faster sprint velocity, security updates completed twice as fast, and modernization work delivered up to 10x quicker without sacrificing quality In fast-moving software environments, critical but repetitive "glue work" like configuration updates, security patches, and documentation often compete with time that could be spent delivering new features. For the Restaurant Topology Management (RTM) team -- who build and maintain the cloud-based platform that enables markets to create and deploy consistent restaurant device configurations -- this maintenance workload had grown quietly over time and began to limit the team's ability to innovate. To regain momentum and address mounting operational debt, the team turned to an AI-powered, agent-based engineering assistant embedded into our standard development workflows, capable of handling complex, repetitive tasks. The challenge: The "un-fun" backlog Before piloting the AI assistant, the RTM team was managing maintenance tasks that had persisted across multiple sprints: Security updates: Enhancing automated scanning workflows to maintain a strong security posture Framework modernization: Updating services to align with the team's current application framework Test coverage improvements: Strengthening unit test consistency across services Documentation updates: Refreshing internal service documentation to support smoother onboarding and troubleshooting This maintenance work was important b ## Maintenance of Everything : A Review DevFeed: [Maintenance of Everything : A Review]() Original publisher: [Read original article]() Author: Phil Venables Published: 2026-04-18T10:45:19Z Content type: opinion Language: en Sources: [Risk and Cyber]() Topics: [maintenance](), [risk-management](), [reliability](), [Security]() Tags: [cybersecurity](), [maintenance](), [reliability](), [review](), [risk-management](), [security](), [technology]() ### AI overview A review of Stewart Brand's book Maintenance of Everything, discussing the importance of maintenance in technology risk management, security, and reliability. It also questions cybersecurity benchmarking that focuses on inputs such as budgets instead of outcomes such as control effectiveness. ### Source excerpt I haven't done a book review for a while and there's no better way to get back to this than a look at Stewart Brand's Maintenance of Everything . Stewart developed a lot of this book in an open editing process and so the final delivery of what is Part 1 of a forthcoming series was all the more anticipated. I've long been obsessed with the need for maintenance in the context of technology risk management, security and reliability. A big part of technical debt build up and the security... ## Choose Boring Technology and Innovative Practices DevFeed: [Choose Boring Technology and Innovative Practices]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-03-24T14:38:06Z Content type: opinion Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [maintenance](), [legacy](), [Software](), [The Julia Language](), [Databases]() Tags: [innovation](), [legacy](), [maintenance](), [technology](), [time]() ### AI overview The article argues that innovative technology carries unknown risks and long-term maintenance costs, while practices can be changed more easily. It recommends being conservative about business-critical software and more willing to innovate in development practices and tools. ### Source excerpt The famous article Choose Boring Technology lists two problems with using innovative technology: There are too many "unknown unknowns" in a new technology, whereas in boring technology the pitfalls are already well-known. Shiny tech has a maintenance burden that persist long after everybody has gotten bored with it. Both of these tie back to the idea that the main cost of technology is maintenance. Even if something is easy to build with, it might not be as easy to keep running. We cannot "abandon" mission-critical technology. Say my team builds a new service on Julia, and 2 years later decides it was the wrong choice. We're stuck with either the (expensive) process of migrating all our data to Postgres code to Java or the (expensive) process of keeping it running anyway. Either way, the company needs to spend resources keeping engineers trained on the tech instead of other useful things, like how to mine crypto in their heads. Tech is slow to change. Not as slow to change as, say, a bridge, but still pretty slow. Now say at the same time as Julia, we also decided to start practicing test && commit || revert (TCR). After two years, we get sick of that, too. To deal with this, we can simply... not do TCR anymore. There is no "legacy practice" we need to support, no maintenance burden to dropping a process. It is much easier to adopt and abandon practices than it is to adopt and abandon technology. This means while we should be conservative in the software we use, we can be more freely innovative in how we use it. If we get three innovation tokens for technology, we get like six or seven for practices. And we can trade in our practices to get those tokens back. (The flip side of this is that social processes are less "stable" than technology and take more work to keep running. This is why "engineering controls" are considered more effective as reducing accidents than administrative controls.) Choose Boring Material and Innovative Tools Pushing this argument further, w ## No Permanent Overrides DevFeed: [No Permanent Overrides]() Original publisher: [Read original article]() Author: Matt McKenna Published: 2026-03-24T13:00:00Z Content type: tutorial Language: en Sources: [Matt McKenna]() Topics: [Development](), [incident](), [maintenance](), [audit]() Tags: [audit](), [automatic](), [best-practices](), [feature](), [feature-flags](), [guide](), [incident](), [maintenance](), [override](), [scheduled](), [software-development](), [software-engineering]() ### AI overview This guide explains how feature flag overrides applied during incident response can accidentally become permanent, causing drift between production and staging, fragmented user experiences, and maintenance debt. It recommends scheduling automatic expiration when applying an override so users re-enter the rollout path after the underlying fix is deployed. ### Source excerpt I originally wrote this guide while working at Square to help my teams address a recurring problem: feature flag overrides applied during incident response were quietly becoming permanent, creating dr ## Modernizing the Command Line: Heroku CLI v11 DevFeed: [Modernizing the Command Line: Heroku CLI v11]() Original publisher: [Read original article]() Author: Eric Black Published: 2026-03-19T22:29:49Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Command-line interface](), [ECMAScript](), [modules](), [migration](), [maintenance](), [Usability]() Tags: [cli](), [command-line](), [heroku](), [javascript](), [legacy](), [maintainability](), [migration](), [modules](), [monorepo](), [news](), [node-js](), [npm](), [performance](), [release](), [upgrade](), [usability]() ### AI overview Heroku CLI v11 is available with a migration to ECMAScript Modules and oclif v4. The release also changes the build system from Yarn to npm, removes the monorepo structure, improves command execution and manifest caching, and adds semantic colors and theme support. ### Source excerpt Heroku CLI v11 is now available. This release represents the most significant architectural overhaul in years, completing our migration to ECMAScript Modules (ESM) and oclif v4. This modernization brings faster performance, a new semantic color system, and aligns the CLI with modern JavaScript standards. While v11 introduces breaking changes to legacy namespaces, the benefits are [...] The post Modernizing the Command Line: Heroku CLI v11 appeared first on Heroku. ## Preparing for Shorter SSL/TLS Certificate Lifetimes DevFeed: [Preparing for Shorter SSL/TLS Certificate Lifetimes]() Original publisher: [Read original article]() Author: Emily Huang Published: 2026-03-06T16:50:10Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [TLS (Transport Layer Security)](), [certificates](), [AWS Certificate Manager](), [maintenance](), [Security]() Tags: [automation](), [certificates](), [heroku](), [maintenance](), [news](), [security](), [ssl](), [tls]() ### AI overview Heroku explains that publicly trusted SSL/TLS certificates will have shorter maximum lifetimes, with a 200-day maximum beginning March 15, 2026. Users who manually manage certificates for Heroku applications will need more frequent renewals, while Heroku Automated Certificate Management handles certificate renewal automatically. ### Source excerpt The web browser and certificate authority industry is shortening the maximum allowed lifetime of TLS certificates. These changes will improve security on the Web, but you may have to change certificate maintenance practices for apps you run on Heroku. The good news is that if you're using Heroku Automated Certificate Management, no changes are required: [...] The post Preparing for Shorter SSL/TLS Certificate Lifetimes appeared first on Heroku. ## Digital Gardening DevFeed: [Digital Gardening]() Original publisher: [Read original article]() Author: Tom Published: 2026-01-21T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [Website](), [maintenance](), [Software Engineering]() Tags: [content-ownership](), [digital-gardening](), [gardening](), [hugo](), [indie-web](), [indieweb](), [maintenance](), [personal-website](), [posse](), [small-web](), [software-engineering](), [web](), [web-philosophy]() ### AI overview The article argues that software development is more like gardening than construction because software requires continuous maintenance as operating systems, dependencies, and security conditions change. It applies this idea especially to small personal websites. ### Source excerpt Treating your personal website like a garden you tend continuously, not as a finished construction, but rather cultivated, authentic fragmented of web. ## Running Renovate as a GitHub Action (and NO PAT!) DevFeed: [Running Renovate as a GitHub Action (and NO PAT!)]() Original publisher: [Read original article]() Published: 2026-01-19T00:00:00Z Content type: tutorial Language: en Sources: [Chainguard: Unchained]() Topics: [renovate](), [GitHub Actions](), [octo sts](), [github personal access token](), [Security](), [maintenance]() Tags: [chainguard-containers](), [chainguard-images](), [dependabot](), [dependencies](), [github](), [github-action](), [github-pat-alternative](), [guide](), [maintenance](), [octo-sts](), [personal-access-token](), [renovate](), [run](), [security](), [software-supply-chain-security]() ### AI overview This tutorial explains how to run Renovate as a scheduled GitHub Action to update repository dependencies without using a long-lived GitHub Personal Access Token. It presents Octo STS as the replacement for the PAT and outlines the workflow setup. ### Source excerpt Discover how you can run Renovate as a GitHub Action without needing a GitHub Personal Access Token by using Octo STS. ## End of Support for Router v1.x; Long-Term Support (LTS) Policy Update DevFeed: [End of Support for Router v1.x; Long-Term Support (LTS) Policy Update]() Original publisher: [Read original article]() Author: Shane Myrick Published: 2025-12-19T15:42:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [upgrade](), [maintenance](), [releases](), [Security]() Tags: [announcement](), [lts](), [maintenance](), [net](), [net-11-preview-7](), [security](), [upgrade]() ### AI overview Apollo announces that Router v1.x, including v1.61.x LTS, and Federation v2.9 will reach end of support on March 31, 2026. The article also introduces Router v2.10 with Federation v2.12 as the next LTS baseline and describes revised support schedules beginning in 2026. ### Source excerpt To better support upgrade planning and provide greater clarity around version lifecycles, we are refining our Router LTS policy and introducing updates to the current maintenance schedule for both Router and Federation. ## Introducing Chainguard EmeritOSS: Sustainable stewardship for mature open source DevFeed: [Introducing Chainguard EmeritOSS: Sustainable stewardship for mature open source]() Original publisher: [Read original article]() Published: 2025-12-16T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [Open Source](), [chainguard](), [maintenance](), [ingress-nginx](), [kaniko](), [kubeapps]() Tags: [chainguard](), [chainguard-containers-open-source](), [chainguard-emeritoss](), [chainguard-open-source](), [emeritoss](), [ingress-nginx](), [kaniko](), [kubeapps](), [maintenance](), [open-source](), [open-source-maintenance]() ### AI overview Chainguard announces EmeritOSS, a program for preserving and securely maintaining mature, unmaintained open source projects. The program starts with Kaniko, Kubeapps, and ingress-nginx. ### Source excerpt EmeritOSS is a stability-focused program that preserves and secures mature, unmaintained open source projects, starting with Kaniko, Kubeapps, and ingress-nginx. ## Heroku Postgres Upgrade Guide: Simplify Your Move to Version 17 DevFeed: [Heroku Postgres Upgrade Guide: Simplify Your Move to Version 17]() Original publisher: [Read original article]() Author: Kavya Premkumar Published: 2025-05-29T15:30:32Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [upgrade](), [Database](), [maintenance](), [Security](), [Availability](), [backups](), [Vulnerabilities](), [Monitoring](), [releases]() Tags: [availability](), [backups](), [bug-fixes](), [cli](), [compatibility](), [database](), [engineering](), [features](), [guide](), [heroku](), [heroku-postgres](), [performance](), [platform-updates](), [postgres](), [provisioning](), [security](), [upgrade](), [vulnerabilities]() ### AI overview This guide explains why Heroku Postgres databases should be upgraded and introduces the simplified process for moving to Postgres 17 on Heroku. It covers security updates, bug fixes, performance improvements, new features, compatibility, and Heroku's version-support lifecycle. ### Source excerpt If you've ever deployed an app on Heroku, chances are you've used Heroku Postgres -- our fully managed, reliable, and scalable Postgres database service. It's the backbone for millions of applications, from weekend side projects to enterprise-grade systems running in production. But Postgres, like all software, continues to evolve. With new versions released each year, [...] The post Heroku Postgres Upgrade Guide: Simplify Your Move to Version 17 appeared first on Heroku. ## Building Scalable Mobile Projects at Android Makers 2025 DevFeed: [Building Scalable Mobile Projects at Android Makers 2025]() Original publisher: [Read original article]() Author: Cyril Mottier Published: 2025-04-10T08:37:01Z Content type: opinion Language: en Sources: [Cyril Mottier Blog]() Topics: [Mobile](), [scaling](), [builds](), [build times](), [maintenance]() Tags: [2025](), [build-times](), [builds](), [maintenance](), [mobile](), [scaling]() ### AI overview The article introduces a keynote on scaling mobile projects as codebases, contributor counts, and complexity grow. It highlights strategies for maintaining fast build times, reusable code, clear ownership, and resilient project structure. ### Source excerpt Edit - Aug 4: adding link to the video on YouTube I recently gave a keynote called "Building Scalable Mobile Projects: Fast Builds, High Reusability and Clear Ownership" at Android Makers 2025 in Paris. Here was the abstract. Every successful project eventually faces the challenges of scaling: an ever-growing codebase, an increasing number of contributors, and rising complexity. Without proper measures, this can lead to slow build times, a cluttered codebase, maintenance difficulties, code duplication, and even dead code--ultimately jeopardizing the company's ability to deliver value. ## Migrate Apollo Federation 1.0 Supergraphs to Apollo Federation 2.0 DevFeed: [Migrate Apollo Federation 1.0 Supergraphs to Apollo Federation 2.0]() Original publisher: [Read original article]() Author: Josh Lambert Published: 2025-01-21T16:34:29Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [GraphQL](), [migration](), [upgrade](), [maintenance](), [Security](), [Architecture & Design](), [API]() Tags: [announcement](), [apollo-federation](), [graphos](), [graphql](), [memory](), [migration](), [migration-guide](), [performance](), [release](), [router](), [security](), [update](), [upgrade]() ### AI overview Apollo announces that Apollo Federation 1.0 supergraphs will no longer be supported starting with the 1.60 release of Apollo GraphOS Router and Apollo Router Core. The release introduces a native query planner designed for Federation 2.0, with reported improvements in query-planning time, CPU utilization, and memory consumption. ### Source excerpt We're announcing an important update: starting with the 1.60 release of Apollo GraphOS Router and Apollo Router Core coming in the next few weeks, Apollo Federation 1.0 supergraphs will no longer be supported. This update accompanies the introduction of a new native query planner in these Apollo Router versions, marking a significant advancement in our technology. [Next page]()