# deprecation Published articles for deprecation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## We Pinned Our Model Version to Stay Safe. The Provider Deprecated It Anyway. DevFeed: [We Pinned Our Model Version to Stay Safe. The Provider Deprecated It Anyway.]() Original publisher: [Read original article]() Author: Pratik Rupareliya Published: 2026-09-18T14:00:02Z Content type: opinion Language: en Sources: [Towards Data Science]() Topics: [Artificial Intelligence](), [model-deployment](), [version](), [Inference](), [Frontier Model](), [Self-hosted]() Tags: [ai](), [artificial-intelligence](), [changes](), [dependency](), [deprecation](), [engineering](), [eval](), [frontier-model](), [inference](), [llm](), [llm-applications](), [llmops](), [machine-learning](), [mlops](), [model](), [production](), [production-ai](), [self-hosted](), [testing](), [version]() ### AI overview The article argues that pinning a production AI model to a specific version prevents silent behavior drift but does not prevent provider-initiated deprecation. It frames the resulting evaluation reruns, prompt retuning, and regression testing as a recurring re-qualification cost that teams should budget for. ### Source excerpt The recurring cost of production AI is not inference. It is re-qualification: the eval reruns, prompt retuning, and regression testing you owe every time a model changes under you. Here is what that tax actually covers, and how to budget for it before it surprises you. The post We Pinned Our Model Version to Stay Safe. The Provider Deprecated It Anyway. appeared first on Towards Data Science. ## Python: fix SyntaxWarning: invalid octal escape sequence DevFeed: [Python: fix SyntaxWarning: invalid octal escape sequence]() Original publisher: [Read original article]() Author: Adam Johnson Published: 2026-08-13T23:00:00Z Content type: tutorial Language: en Sources: [Adam Johnson]() Topics: [Python](), [software-development](), [Code]() Tags: [2026](), [c](), [code](), [deprecation](), [python](), [warnings]() ### AI overview This tutorial explains why Python warns about invalid octal escape sequences in string and bytes literals. It describes the warning changes introduced in Python 3.11 and 3.12, explains how oversized octal values are interpreted, and suggests escaping the backslash or substituting the intended character. ### Source excerpt Take this code: path = "C:\477_data" If we run this with Python 3.11+ in development mode (to enable deprecation warnings), we will see: $ python3.11 -X dev example.py /.../example.py:1: DeprecationWarning: invalid octal escape sequence '\477' path = "C:\477_data" On Python 3.12+, we instead get ... ## Kubernetes 1.36 - New security features DevFeed: [Kubernetes 1.36 - New security features]() Original publisher: [Read original article]() Author: Victor Jimenez Cerrada Published: 2026-04-15T00:00:00Z Content type: article Language: en Sources: [Sysdig]() Topics: [Kubernetes](), [Security](), [kubectl](), [Authorization](), [certificates](), [configuration]() Tags: [admission-controller](), [api](), [authorization](), [certificates](), [configuration](), [credentials](), [deprecated](), [deprecation](), [dynamic-resource-allocation-kubernetes](), [exploits](), [kubectl](), [kubernetes](), [kubernetes-1-36](), [kubernetes-1-36-enhancements](), [kubernetes-1-36-release](), [kubernetes-1-36-security-changes](), [kubernetes-admission-control-changes](), [kubernetes-deprecations-1-36](), [kubernetes-dra](), [kubernetes-externalips-deprecation](), [kubernetes-security-best-practices](), [kubernetes-security-features-2026](), [kubernetes-upgrade-1-36](), [man-in-the-middle](), [security]() ### AI overview An overview of security changes planned for Kubernetes 1.36, including the deprecation of externalIPs, separation of kubectl user preferences from cluster configuration, and changes to pod certificate fields. ### Source excerpt Kubernetes 1.36 will be released soon, bringing 60 enhancements. Of particular note is the effort made to improve dynamic resource allocation (DRA).In terms of security, there are 22 changes spanning admission control configurations, certificate handling, and more.Let's dig in! ## VyOS 1.4.4 released: syslog over TLS, AWS GLB support, and 50+ bug fixes DevFeed: [VyOS 1.4.4 released: syslog over TLS, AWS GLB support, and 50+ bug fixes]() Original publisher: [Read original article]() Author: daniil@sentrium.io (Daniil Baturin) Published: 2025-12-19T09:22:24Z Content type: release Language: en Sources: [VyOS]() Topics: [releases](), [TLS (Transport Layer Security)](), [Amazon Web Services](), [OpenSSH](), [ssh](), [BGP](), [multicast](), [nginx]() Tags: [1-4](), [aws](), [bgp](), [bug](), [deprecation](), [gateway-load-balancer](), [linux](), [multicast](), [network](), [openssh](), [press-release](), [releases](), [ssh](), [syslog](), [tls]() ### AI overview VyOS 1.4.4 adds syslog over TLS, AWS Gateway Load Balancer tunnel-handler support, BGP route-map matching for prefix origin validation extended communities, and validation against manually assigned multicast addresses. The release also fixes more than 50 bugs and deprecates SSH DSA keys ahead of their removal after VyOS 1.5. ### Source excerpt Hello, Community! Customers and holders of contributor subscriptions can now download VyOS 1.4.4 release images and the corresponding source tarball. This release adds TLS support for syslog, support for AWS gateway load balancer tunnel handler (on AWS only), an option to match BGP prefix origin validation extended communities in route maps, and more. It also fixes over fifty bugs. Additionally, there's now a proper validation to prevent manually assigned multicast addresses, which may break some old malformed configs, so pay attention to it. Last but not least, there's a deprecation warning for SSH DSA keys that will stop working in VyOS releases after 1.5 due to changes in OpenSSH, so make sure to update your user accounts to more secure algorithm keys while you still have the time. ## Moving Towards a Stable JavaScript API (New Changes in 0.80) DevFeed: [Moving Towards a Stable JavaScript API (New Changes in 0.80)]() Original publisher: [Read original article]() Author: Alex Hunt; Iwo Plaza; Jakub Piasecki; Dawid Małecki Published: 2025-06-12T16:00:00Z Content type: release Language: en Sources: [React Native Blog]() Topics: [React Native](), [TypeScript](), [API](), [JavaScript](), [Developer Tools]() Tags: [announcement](), [api](), [deprecation](), [eslint](), [import](), [javascript](), [maintenance](), [react-native](), [type-safety](), [typescript]() ### AI overview React Native 0.80 deprecates deep JavaScript imports and introduces an opt-in Strict TypeScript API. The changes aim to define a more stable public API, improve type accuracy, and provide stronger type safety, with deep-import removal targeted for version 0.82. ### Source excerpt In React Native 0.80, we're introducing two significant changes to React Native's JavaScript API -- the deprecation of deep imports, and our new Strict TypeScript API. These are part of an ongoing effort to accurately define our API and offer dependable type safety to users and frameworks. ## AlmaLinux Azure Image Deprecation and Azure Marketplace Update DevFeed: [AlmaLinux Azure Image Deprecation and Azure Marketplace Update]() Original publisher: [Read original article]() Author: Elkhan Mammadli AlmaLinux OS Cloud engineer Published: 2024-10-09T00:00:00Z Content type: release Language: en Sources: [AlmaLinux]() Topics: [Azure](), [azure marketplace](), [x86](), [Deployment](), [Cloud](), [virtualization](), [help]() Tags: [azure](), [azure-marketplace](), [deployments](), [deprecated](), [deprecation](), [microsoft](), [updates](), [upgrade](), [virtual-machine](), [virtualization](), [x86-64]() ### AI overview AlmaLinux announces that its original Azure x86_64 image will be deprecated and removed from the Azure Marketplace on 30 December 2024. Existing VM instances will continue receiving updates, but new VM and VM scale set deployments using the deprecated offers will no longer be possible, and existing VMSS deployments cannot scale out. ### Source excerpt Hello Community! We'd like to share a quick update for our AlmaLinux Azure users. If you've been using the original AlmaLinux Azure image for x86_64 architecture (VM Image URN: almalinux:almalinux:*), you may have gotten an email like this: Your Workloads are running on images that will be deprecated soon You're receiving this email because you have virtual machine and/or virtual machine scale set deployments that are running on images scheduled for deprecation. ## Introducing the Sail Operator: a new way to manage Istio DevFeed: [Introducing the Sail Operator: a new way to manage Istio]() Original publisher: [Read original article]() Author: Francisco Herrera - Red Hat Published: 2024-08-19T00:00:00Z Content type: article Language: en Sources: [Istio]() Topics: [istio](), [control-plane](), [Deployment](), [configuration](), [upgrade](), [Helm charts](), [version]() Tags: [configuration](), [control-plane](), [deploy](), [deployments](), [deprecation](), [helm-charts](), [incluster](), [istio](), [mesh](), [microservices](), [operator](), [revision](), [sail](), [services](), [update](), [upgrade]() ### AI overview The Sail Operator is a Kubernetes operator for managing the lifecycle of Istio control planes and Istio CNI. It uses Istio Helm chart APIs and provides in-place and revision-based strategies for upgrading control planes. ### Source excerpt With the recent announcement of the In-Cluster IstioOperator deprecation in Istio 1.23 and its subsequent deletion for Istio 1.24, we want to build awareness of a new operator that the team at Red Hat have been developing to manage Istio as part of the istio-ecosystem organization. The Sail Operator manages the lifecycle of Istio control planes, making it easier and more efficient for cluster administrators to deploy, configure and upgrade Istio in large scale production environments. Instead of creating a new configuration schema and reinventing the wheel, the Sail Operator APIs are built around Istio's Helm chart APIs. All installation and configuration options that are exposed by Istio's Helm charts are available through the Sail Operator CRDs' values fields. This means that you can easily manage and customize Istio using familiar configurations without adding additional items to learn. The Sail Operator has 3 main resource concepts: Istio: used to manage the Istio control planes. Istio Revision: represents a revision of that control plane, which is an instance of Istio with a specific version and revision name. Istio CNI: used to manage the resource and lifecycle of Istio's CNI plugin. To install the Istio CNI Plugin, you create an IstioCNI resource. Currently, the main feature of the Sail Operator is the Update Strategy. The operator provides an interface that manages the upgrade of Istio control plane(s). It currently supports two update strategies: In Place: with the InPlace strategy, the existing Istio control plane is replaced with a new version, and the workload sidecars immediately connect to the new control plane. This way, workloads don't need to be moved from one control plane instance to another. Revision Based: with the RevisionBased strategy, a new Istio control plane instance is created for every change to the Istio.spec.version field. The old control plane remains in place until all workloads have been moved to the new control plane instance. Opti ## Istio has deprecated its In-Cluster Operator DevFeed: [Istio has deprecated its In-Cluster Operator]() Original publisher: [Read original article]() Author: Mitch Connors (Microsoft), for the Istio Technical Oversight Committee Published: 2024-08-14T00:00:00Z Content type: release Language: en Sources: [Istio]() Topics: [istio](), [migration](), [Helm charts](), [Platform Engineering](), [Deployment](), [GitOps](), [kubectl](), [YAML]() Tags: [argo-cd](), [deployment](), [deprecation](), [flux](), [gitops](), [helm](), [istio](), [kubectl](), [mesh](), [microservices](), [operator](), [platform-engineering](), [services](), [yaml]() ### AI overview Istio deprecated its In-Cluster Operator in version 1.23. Users relying on it must migrate to another installation and upgrade mechanism to move beyond Istio 1.23, with Helm recommended for most users and istioctl, GitOps tools, and alternative operator projects also supported. ### Source excerpt Istio's In-Cluster Operator has been deprecated in Istio 1.23. Users leveraging the operator -- which we estimate to be fewer than 10% of our user base -- will need to migrate to other install and upgrade mechanisms in order to upgrade to Istio 1.24 or above. Read on to learn why we are making this change, and what operator users need to do. Does this affect you? This deprecation only affects users of the In-Cluster Operator. Users who install Istio with the istioctl install command and an IstioOperator YAML file are not affected. To determine if you are affected, run kubectl get deployment -n istio-system istio-operator and kubectl get IstioOperator. If both commands return non-empty values, your cluster will be affected. Based on recent polls, we expect that this will affect fewer than 10% of Istio users. Operator-based Installations of Istio will continue to run indefinitely, but cannot be upgraded past 1.23.x. When do I need to migrate? In keeping with Istio's deprecation policy for Beta features, the Istio In-Cluster Operator will be removed with the release of Istio 1.24, roughly three months from this announcement. Istio 1.23 will be supported through March 2025, at which time operator users will need to migrate to another install mechanism to retain support. How do I migrate? The Istio project will continue to support installation and upgrade via the istioctl command, as well as with Helm. Because of Helm's popularity within the platform engineering ecosystem, we recommend most users migrate to Helm. istioctl install is based on Helm templates, and future versions may integrate deeper with Helm. Helm installs can also be managed with GitOps tools like Flux or Argo CD. Users who prefer the operator pattern for running Istio can migrate to either of two new Istio Ecosystem projects, the Classic Operator Controller, or the Sail Operator. Migrating to Helm Helm migration requires translating your IstioOperator YAML into Helm values. Istio 1.24 and above includes a ## Deprecating spatie/data-transfer-object DevFeed: [Deprecating spatie/data-transfer-object]() Original publisher: [Read original article]() Author: Brent Published: 2022-11-01T00:00:00Z Content type: article Language: en Sources: [Stitcher]() Topics: [PHP](), [Code](), [class](), [Livewire](), [Symfony]() Tags: [code](), [deprecation](), [laravel](), [php](), [spatie](), [symfony]() ### AI overview The author announces the deprecation of spatie/data-transfer-object. The package originally provided runtime type checks for PHP class properties, but PHP's evolving type system and stronger static-analysis approaches reduced the need for that functionality. The author also points to Laravel Data, Valinor, and Symfony Serializer as alternatives and says the deprecated code remains available for the near future. ### Source excerpt Read the full post on https://stitcher.io/blog/deprecating-spatie-dto ## re: re: A letter to the PHP team DevFeed: [re: re: A letter to the PHP team]() Original publisher: [Read original article]() Author: Brent Published: 2019-08-29T00:00:00Z Content type: opinion Language: en Sources: [Stitcher]() Topics: [PHP](), [Programming]() Tags: [deprecate](), [deprecation](), [developers](), [php](), [process]() ### AI overview A response to Joe's letter about PHP's internal decision-making, arguing that PHP's RFC discussions and governance processes are outdated, inefficient, and in need of a more modern and formal approach to deprecation and other changes. ### Source excerpt Read the full post on https://stitcher.io/blog/a-letter-to-the-php-team-reply-to-joe