# EOL Published articles for EOL. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cisco UCS Manager: Celebrating the legacy, shaping the future with Cisco Intersight DevFeed: [Cisco UCS Manager: Celebrating the legacy, shaping the future with Cisco Intersight]() Original publisher: [Read original article]() Author: Jacob Van Ewyk Published: 2026-09-15T21:00:37Z Content type: opinion Language: en Sources: [Cisco Blogs]() Topics: [Cisco](), [Server](), [Automation](), [configuration](), [API](), [legacy]() Tags: [api](), [automation](), [cisco](), [data-center](), [end-of-life](), [eol](), [infrastructure](), [legacy](), [lifecycle](), [management](), [server]() ### AI overview Cisco describes the legacy of Cisco UCS Manager and positions Cisco Intersight as the strategic platform for future Cisco UCS software management. The article also outlines announced end-of-sale and end-of-life milestones, including a planned Last Date of Support of December 31, 2030, subject to applicable contracts and service terms. ### Source excerpt Cisco UCS Manager shaped 17 years of infrastructure management. Now, with its end-of-life announced, Cisco Intersight carries that foundation forward with centralized visibility, automation, and scale. Learn the key dates for the UCS Manager EOL. ## Quick update: May 2026 DevFeed: [Quick update: May 2026]() Original publisher: [Read original article]() Author: LoRa Left-handed operational Radio authority; Obviously Published: 2026-05-18T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Home Assistant](), [lora](), [Matter](), [Pinephone](), [zigbee](), [Kernel](), [Pinephone-Pro](), [USB](), [Crystal](), [Dongle]() Tags: [2026](), [community](), [crystal](), [dongle](), [eol](), [home-assistant](), [kernel](), [lcd](), [pinedio](), [pinephone](), [pinephone-pro](), [pinetime](), [pinevoice](), [protocol](), [table](), [update](), [usb](), [zigbee]() ### AI overview Pine64's May 2026 update covers the PineVoice Home Assistant speaker, PineTime and PineTime Pro hardware, PineDio USB LoRa development, and recent PineTab2, PinePhone, PinePhone Pro, and PineTab-V software updates. It also reports instability in the PineDio adapter caused by an overheating crystal oscillator. ### Source excerpt Table of contents Whats been going on recently? PineVoice PineTime/PineTime Pro LoRa? (Left-handed operational Radio authority, obviously) Important recent community updates: Do you have something to share? Contact Community PineStore Whats been going on recently? Hello everyone, we wanted to do a quick update on what's been happening recently. Life has been pretty busy but there's lots of nice things happening in the background that we'd like to share. PineVoice The PineVoice Home Assistant speaker (formally PineVox) is in its final stages. Production begins. Further on this, there will be limited bundle with this device which will include a PineVoice, Zigbee dongle, power supply and two matter modules. Pair it with a SBC of choice and run your Home Assistant instance locally! PineTime/PineTime Pro The current PineTime LCD is EOL and a new one is replacing it, though it is essentially the same display. These will be shipping in the next PineTime batch. New PineTime Pro samples have been received by developers. Shiny! LoRa? (Left-handed operational Radio authority, obviously) The PineDio USB LoRa Adapter is at the focus of a new effort to begin progress on potential new LoRa devices. MeshCore is the current protocol target for the USB LoRa Adapter along with help from the pyMC_core library project. The current problem with the device is that the crystal oscillator is heating up too much and can cause clock frequency drifting instability. In a nutshell that means your messages come out garbled. This may eventually be fixed with a TXCO (Temperature-Compensated Crystal Oscillator) to maintain a stable clock frequency. Important recent community updates: DanctNIX PineTab2 updates (including factory image) Adam Piggz: PinePhone, PinePhone Pro, PineTab2 all updated to kernel 7.0, and improved USB config. Zypper ref and dup to update. machaddr@mastodon.sdf.org: with their new Gentoo PineTab-V image Do you have something to share? Do you have news to share with the communit ## Build, Customize, Sustain: Exposing the Chainguard Factory for Every Customer DevFeed: [Build, Customize, Sustain: Exposing the Chainguard Factory for Every Customer]() Original publisher: [Read original article]() Published: 2025-05-29T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [EOL Grace period](), [Containers](), [Automation](), [Security](), [Open Source]() Tags: [apk-repositories](), [automation](), [chainguard](), [chainguard-containers](), [container-images](), [custom-assembly](), [end-of-life](), [eol](), [eol-grace-period](), [packages](), [private-apks](), [security](), [supply-chain]() ### AI overview Chainguard announces that all Chainguard Containers customers receive access to EOL Grace Period, Private APK Repositories, and Custom Assembly. These capabilities expose more of the Chainguard Factory, enabling customers to customize containers, build with Chainguard APKs, and migrate software on their own timelines. EOL Grace Period supports rebuilding end-of-life container images and remediating CVEs in non-primary packages for up to six months after the initial EOL date. ### Source excerpt EOL Grace Period, Private APK Repositories, and Custom Assembly features are now included for all Chainguard Containers customers. ## Announcing Chainguard EOL Grace Period: Time and Flexibility for Updating Software DevFeed: [Announcing Chainguard EOL Grace Period: Time and Flexibility for Updating Software]() Original publisher: [Read original article]() Published: 2025-02-27T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [container images](), [supply-chain-security](), [Vulnerabilities](), [migration](), [Open Source]() Tags: [blog-post](), [chainguard](), [chainguard-images](), [container-images](), [customers](), [cves](), [end-of-life](), [eol](), [eol-grace-period](), [migration](), [open-source](), [software-supply-chain](), [supply-chain-security]() ### AI overview Chainguard announces the beta of EOL Grace Period, a product for container images that supports customers transitioning away from end-of-life software. Chainguard will remediate CVEs and rebuild EOL images for up to six months after the initial EOL date, giving engineering teams more time to plan and execute migrations. ### Source excerpt Chainguard EOL Grace Period is a product that is designed to support Chainguard Images customers as they transition off end-of-life software. ## Please refrain from installing WASP-OS on new PineTimes for the moment DevFeed: [Please refrain from installing WASP-OS on new PineTimes for the moment]() Original publisher: [Read original article]() Published: 2024-12-29T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [Software](), [Hardware](), [GitHub](), [Documentation]() Tags: [bootloader](), [documentation](), [end-of-life](), [eol](), [github](), [hardware](), [infinitime](), [pinetime](), [version]() ### AI overview The article warns users not to install WASP-OS on PineTime devices with factory bootloader v1.0.1 because the reloader tool does not yet support a replacement flash chip, which can soft-brick the device when reverting to InfiniTime. ### Source excerpt In July 2024, PineStore notified the community that a small hardware change was needed on the PineTime: the current flash chip was end of life (EoL) and needed to be replaced by a new one. From the software point of view, the new chip behaves exactly like the old on so very few code changes were required to support it. The new chip exposes different identifiers (manufacturer ID, for example) than the previous one. Which means that if the software checks those IDs, it would need to be updated to take the new ones into account. No change was needed in InfiniTime, but we however added a new field in the SystemInfo app to display the IDs of the chip. We figure this could be useful in the future. The bootloader does check against those IDs so we released a new version of the bootloader (v1.0.1) as well. We provided the new software to PineStore so they could test them and use them to flash the new batch of PineTimes at the factory. Everything went well and PineTimes equipped with the new memory chip and software are being delivered to happy users. Everything? Well, not really: a few users reported soft-bricked PineTimes after switching to WASP-OS and then reverting to InfiniTime again. This is a bummer: the "reloader" tool that reinstalls the InfiniTime bootloader also needed to be upgraded to support the new memory chip! An issue has already been opened on the WASP-OS GitHub repo and a new reloader tool will hopefully be released soon to tackle this issue. We also added a big red warning on the documentation page that explains how to switch to and from InfiniTime and WASP-OS to ensure that users won't try to switch OS until the issue is fixed and the documentation updated. Warning In the meantime, do not try to install WASP-OS on your PineTime if it's running bootloader v1.0.1 from the factory (unless you know exactly what you are doing), this WILL brick your PineTime! Be sure that the community will try to fix this as soon as possible, but please remember that develope ## Nuxt 2 End-of-Life (EOL) DevFeed: [Nuxt 2 End-of-Life (EOL)]() Original publisher: [Read original article]() Published: 2024-06-14T00:00:00Z Content type: release Language: en Sources: [The Nuxt Blog]() Topics: [Nuxt.js](), [migration](), [Vue.js](), [npm](), [Server-side rendering](), [TypeScript](), [Vite](), [Serverless](), [Single-page application (SPA)](), [AWS Lambda](), [Cloudflare Workers](), [Deno]() Tags: [announcement](), [aws-lambda](), [cloudflare-workers](), [end-of-life](), [eol](), [migration](), [npm](), [nuxt](), [security](), [serverless](), [ssr](), [typescript](), [vite](), [vue]() ### AI overview Nuxt 2 reached end of life on June 30, 2024. It remains available through npm but will no longer receive updates, including security and browser compatibility fixes. The article recommends migrating to Nuxt 3 and describes its rendering, serverless, TypeScript, Vite, API, and developer-experience features. For applications that cannot migrate, Nuxt 2 Never-Ending Support from HeroDevs provides ongoing security and compatibility patches. ### Source excerpt Nuxt 2 will reach End of Life (EOL) on June 30th, 2024. We've partnered with HeroDevs on offering Never-Ending Support (NES). ## Why end-of-life software means 400+ CVEs per year DevFeed: [Why end-of-life software means 400+ CVEs per year]() Original publisher: [Read original article]() Published: 2024-03-28T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Security](), [Vulnerabilities](), [container images](), [Docker](), [Cloud]() Tags: [container-images](), [cve](), [cves](), [docker](), [end-of-life](), [end-of-life-software](), [eol](), [eol-software](), [security](), [updates](), [vulnerabilities]() ### AI overview The article examines how vulnerabilities accumulate in end-of-life software and official EOL Docker images. Based on nearly 40 software projects, it reports an average accumulation of 218 CVEs every six months after end of life, with 98.4% occurring in image components, 1.4% in application dependencies, and 0.2% directly in the application. ### Source excerpt Discover why End-of-Life software poses a high security risk with over 400 CVEs annually, emphasizing the importance of timely updates and secure practices. ## Vue 2 is Approaching End Of Life DevFeed: [Vue 2 is Approaching End Of Life]() Original publisher: [Read original article]() Published: 2023-12-15T00:00:00Z Content type: article Language: en Sources: [The Vue Point]() Topics: [Vue.js](), [Framework](), [migration](), [npm]() Tags: [deprecated](), [end-of-life](), [eol](), [framework](), [maintenance](), [migration](), [npm](), [vue]() ### AI overview The Vue team announces that Vue 2 reached End of Life on December 31, 2023, ending new features, updates, and fixes. Vue 2 remains available through existing distribution channels, but users are encouraged to migrate to Vue 3, which offers performance, TypeScript, reactivity, built-in component, and tooling improvements. ### Source excerpt With 2024 almost upon us, we would like to take this opportunity to remind the Vue community that Vue 2 will reach End of Life (EOL) on December 31st, 2023. Vue 2.0 was released more than 7 years ago in 2016. It was a major milestone in Vue's journey of becoming a mainstream framework. Many current Vue users started using Vue during the Vue 2 era, and many great things have been built with it. However, active maintenance of two major versions in parallel isn't sustainable for us. As Vue 3 and its ecosystem have matured, it is time for the team to move on and focus our energy on the latest major version. ## The future of Keycloak Operator CRs DevFeed: [The future of Keycloak Operator CRs]() Original publisher: [Read original article]() Author: Václav Muzikář Published: 2022-09-02T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Quarkus](), [Cloud](), [Git]() Tags: [critical](), [declarative](), [deprecated](), [eol](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [operator](), [quarkus](), [rest-api](), [saml](), [source-of-truth](), [sso](), [ui]() ### AI overview The article describes Keycloak's new Operator, rewritten for the Quarkus distribution and available as a preview. It explains that Custom Resource Definitions for managing Keycloak resources are not yet available because supporting features, including file storage and read-only interfaces, are still being developed. The CRDs were expected to be added with support anticipated in Keycloak 21. ### Source excerpt A while back, we have announced a new Operator rewritten from scratch to provide the best experience for the Quarkus distribution. While the legacy Operator is now deprecated and will reach EOL with Keycloak 20, the new one is already available as a preview, see the installation guide. One of the most common concerns around the new Operator is the current lack of the CRDs for managing Keycloak resources, such as realm, users and clients, in a cloud-native way. One of the key aspects of the new Operator will be redesign of managing these Keycloak resources via CRs and git-ops. This new approach will leverage the new storage architecture and future immutability options, making the CRs the declarative single source of truth. In comparison to the legacy Operator, this will bring high robustness, reliability, and predictability to the whole solution. Before we would consider operator ready for leveraging CRs, we expect completing several features including but not limited to: File store (expected in Keycloak 20) to persist data in a file instead of DB. Read-only possibilities for administration REST API, UI Console and other interfaces. This is required for the new immutability concept which will be used to ensure any data coming from the CRs (and subsequently from the file store) are read-only from all interfaces. All of this is critical to proper CRs implementation, hence the new Operator is currently missing the CRDs for managing Keycloak resources. The missing CRDs will be added once Keycloak has the necessary support for it, which is currently expected in Keycloak 21. We have prepared a few options to alleviate the situation with missing CRDs in this repository. ## Bringing forward the End-of-Life Date for Node.js 16 DevFeed: [Bringing forward the End-of-Life Date for Node.js 16]() Original publisher: [Read original article]() Published: 2022-06-08T16:00:00Z Content type: news Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [Open Source](), [releases](), [cross-platform]() Tags: [cross-platform](), [end-of-life](), [eol](), [javascript](), [node-js](), [open-source](), [vulnerabilities]() ### AI overview Node.js is moving Node.js 16's End-of-Life date forward to September 11, 2023, aligning it with the end of support for OpenSSL 1.1.1. The decision avoids riskier in-release OpenSSL changes that could cause application compatibility problems. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Official CentOS 8 Stream Docker Image Is Available on quay.io DevFeed: [Official CentOS 8 Stream Docker Image Is Available on quay.io]() Original publisher: [Read original article]() Author: Tom Published: 2021-07-25T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [Docker Image](), [centos](), [Docker]() Tags: [base-images](), [centos](), [centos-8-stream-docker-image](), [centos-docker-image-updates](), [centos-stream](), [centos-stream-9](), [docker](), [docker-hub](), [docker-hub-to-quay-io-transition](), [docker-image](), [docker-image-management](), [end-of-life](), [eol](), [official-docker-images](), [upgrade]() ### AI overview The article discusses the availability of an official CentOS 8 Stream Docker image on quay.io after its transition from Docker Hub. It also notes the lack of updates for older images and recommends considering CentOS Stream 9 as CentOS Stream 8 approaches archival. ### Source excerpt Discover the availability of the official CentOS 8 Stream Docker image on quay.io, and learn about the transition from Docker Hub and its implications. ## Announcing EOL support for Cadence DevFeed: [Announcing EOL support for Cadence]() Original publisher: [Read original article]() Author: Ryland Goldstein Published: 2021-04-01T04:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [reliability](), [version]() Tags: [end-of-life](), [eol](), [product-news](), [release](), [support]() ### AI overview Temporal announces that it will end support for all versions of Cadence after September 29, 2021. The decision is attributed to increasing code differences, support costs, and reliability concerns. ### Source excerpt For the last year we have been happy to provide free support to Cadence users. After September 29th 2021, we will no longer be providing support for any version of Cadence. ## Sunsetting Louketo Project DevFeed: [Sunsetting Louketo Project]() Original publisher: [Read original article]() Author: Bruno Oliveira Published: 2020-08-21T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [proxy](), [OAuth 2.0](), [OpenID connect (OIDC)](), [Keycloak]() Tags: [bug-fixes](), [eol](), [idm](), [kerberos](), [ldap](), [oauth](), [oauth2](), [oidc](), [openid-connect](), [proxy](), [replacement](), [saml](), [sso]() ### AI overview Keycloak announces that it is sunsetting the Louketo project and beginning its end-of-life process. Only critical bug fixes and security fixes will be provided for three months, while OAuth2 Proxy is recommended as a replacement with high-level migration guidance. ### Source excerpt After careful consideration, we have decided to pull the plug on Louketo and start the EOL procedure. The plan is during the next 3 months to fix only critical bugs and security issues. Everyone interested in capabilities provided by Louketo Proxy should look at OAuth2 Proxy project which is providing a similar set of capabilities and has a healthy and active community. A few months ago, the Keycloak team started Louketo -- a joint effort to build a generic OAuth2 Proxy and possibly also begin an umbrella project for a set of OIDC related integration libraries. The initial set of goals has not worked out. Keycloak Gatekeeper and OAuth2 Proxy projects hoped to merge and join efforts but for various reasons, this has not worked out. With Louketo and OAuth2 proxy providing similar features, OAuth Proxy being a more popular project with a bigger community we reached a conclusion there's no reason to put more effort into Louketo, when we can just contribute there. What does it mean in practice? FAQ Will Louketo Proxy be no longer maintained? Will there be no new releases? Critical bug fixes will be merged and micro releases provided for the next 3 months. It is up to community members to step up and take over maintaining and driving this project further if they wish to do so. Please comment on the GitHub issue or contact the Keycloak team on the mailing list. Are there any alternatives I should use instead? OAuth2 Proxy is very close in a set of capabilities to Louketo Proxy and we highly suggest you investigate it as a replacement. How do I migrate to OAuth2 Proxy? We'll provide high-level guidance on how to migrate. Although unfortunately there is no comprehensive guide nor magical script. Some corner cases, specific configurations, and capabilities may not be fully covered or addressed in exactly the same way. Why are you abandoning Louketo Proxy as a project? Initial goals failed. Which were merging with OAuth2 Proxy and creating a wider set of OAuth2/OIDC integration ## PineTab production update: LCD driver change, shipping timeline, certifications, and adapter testing DevFeed: [PineTab production update: LCD driver change, shipping timeline, certifications, and adapter testing]() Original publisher: [Read original article]() Published: 2020-07-24T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Hardware](), [systems](), [Software]() Tags: [battery](), [certificates](), [drivers](), [eol](), [hardware](), [lcd](), [lora](), [news](), [pine64](), [pinetab](), [production](), [ssd](), [ubports](), [update]() ### AI overview This PineTab update reports that production is about one week behind schedule because the LCD panel driver was changed after the original driver reached end of life. It also gives an expected shipping window, confirms finalized CE, FCC, and RoHS certifications, describes the 6000mAh lithium-ion battery, and notes testing of LTE/SSD and LoRa adapter samples. ### Source excerpt This is a supplementary post to this month's Community Update - if you haven't read this month's news, then I suggest you go back and have a read since we've had a handful of interesting announcements. Regarding the PineTab, I am happy to let you know that production is well under way and we are mostly on schedule with the manufacturing and shipping processes. To be precise, we are just a week behind the original schedule; the cause of the delay is our decision to change the LCD panel driver (or perhaps more accurately, we were convinced to exchange the panel driver by the vendor) as the driver we originally chose is reaching end of life (EoL). We ultimately decided that a week's delay is worth it. The alternative scenario would likely result in developers supporting multiple LCD drivers in their operating systems, which is not ideal. Here are the details of the current timeline. Finished PCBAs will be released to us from the factory on the 27th and, granted we're happy with them, fully assembled tablets should be dispatched from the production line on August 6th or 7th. The PineTabs will make their way to Hong Kong soon after and I expect that shipping will commence the week of August 17-21. Closer to the shipping date, sometime early next month, I'll open a shipping thread on the forum which you'll be able to follow. I am also pleased to announce that CE, FCC and RoHS certifications for the PineTab have already been finalized and the reports are now being written up. All reports will be completed in time for shipping and relevant certificates will be submitted to Wiki as soon as they are made available to us. As I mentioned in the past, we have significantly improved the battery from earlier hardware iterations. The PineTab ships with a 6000mAh Cobalt in lithium-ion battery, which not only provides a long battery life for the tablet but also superior discharge-cycle battery longevity. Investing into core components such as the battery is part of our commitment to ## June 2020 Security Releases DevFeed: [June 2020 Security Releases]() Original publisher: [Read original article]() Published: 2020-06-02T12:00:00Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [releases](), [Security](), [HTTP](), [C++]() Tags: [c](), [c-plus-plus](), [eol](), [http](), [lts](), [node-js](), [release](), [releases](), [security]() ### AI overview Node.js announces June 2020 security releases for all supported release lines. The updates address session event authorization, excessive CPU use from large HTTP/2 SETTINGS frames, a native add-on buffer overrun issue, and an ICU integer overflow affecting some versions. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Node.js 14.0.0 (Current) DevFeed: [Node.js 14.0.0 (Current)]() Original publisher: [Read original article]() Published: 2020-04-22T10:20:16Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [ECMAScript](), [JavaScript](), [V8](), [Web]() Tags: [cross-platform](), [deprecated](), [eol](), [javascript](), [node-js](), [open-source](), [release](), [v8](), [wasm]() ### AI overview Node.js 14.0.0 is a current release introducing semver-major changes, deprecations, removals, and updates to cryptography, filesystem handling, HTTP, operating-system APIs, streams, WebAssembly checks, and V8 ArrayBuffer support. It also removes the experimental-modules warning while keeping the ECMAScript Modules implementation experimental. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Native Logging and Certificate Wizard Downtime DevFeed: [Native Logging and Certificate Wizard Downtime]() Original publisher: [Read original article]() Author: Shai Almog Published: 2018-06-18T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Logging](), [Library](), [Extension](), [Provisioning]() Tags: [apple](), [certificates](), [eol](), [jdk](), [library](), [logging](), [logs](), [native](), [on-device](), [provisioning]() ### AI overview The article introduces the NativeLogsReader cn1lib for viewing native device output through the Codename One log without physical access to a device. It also discusses certificate wizard downtime caused by Apple's undocumented and changing certificate-generation system, a book update, and postponement of Codename One 5.0 to September while newer JDK compatibility issues are addressed. ### Source excerpt I've been so busy with the book I completely missed a lot of things I should have blogged about and one such thing is the NativeLogsReader cn1lib which has been in the extension manager for a while now. The NativeLogsReader cn1lib was created by Francesco Galgani to include native logging into the Codename One log. A lot of times we get on device failures that are really hard to track. In those cases we ask users to connect cables and try to view the native logs to search for clues. With this library you can see native output even without physical access to the device!