The following deprecations are in process. You may want to track them until they go into effect (when they will then move to the relevant product deprecation table).
Product | What is being deprecated? | Timeframe | Deprecation process and next steps | What has to be done? |
|---|---|---|---|---|
Artifactory | Composer 1.x | December 2026 | Packagist has deprecated Composer 1.x as of September 1, 2025. If upgrading to Composer 2.0 is not possible, Artifactory will provide extended support for Composer 1.x in local repositories only. For more information, see the deprecation notice from Packagist. | Upgrade to Composer 2.0 |
Artifactory | The Helm Chart will no longer support setting the | End of Q3-2025 | The setting This enables all microservices to run in different containers in a single pod (by default, it is | You must change the setting to |
Artifactory | Artifactory HA Helm Chart - Member Nodes | End of Q3-2025 | Artifactory HA Helm Chart released after September 2025 will no longer include the Member Node StatefulSet. This chart will support only Cloud-Native (Masterless) High Availability, similar to Artifactory Helm Chart. | Redeploy Artifactory HA Helm Chart only with primary nodes. |
Artifactory | Artifactory Microsoft SQL Server 2016 / 2017 Support | End of Q3-2025 | Artifactory Self-Hosted versions released after September 2025 will no longer include support for MSSQL 2016 and MSSQL 2017. | Upgrade to a newer database version. |
Artifactory | Hugging Face Repositories Legacy Layout | For all Hugging Face repositories created prior to Artifactory 7.111.1, the Hugging Face repositories legacy layout will be deprecated in September 2025 and all repositories with the legacy layout will be automatically upgraded to the Machine Learning layout. | The process is automated and no steps need to be taken by Artifactory users. | No steps need to be taken. However, users with the legacy layout can initiate the upgrade from the legacy layout to the Machine Learning layout at any point in time prior to the automatic migration by following the migration instructions here. |
Pipelines | Pipelines | Pipelines will reach end-of-life on May 1, 2026. | For Cloud and Self-hosted customerCs, Pipelines will be deprecated as of May 1, 2026. Please note the following:
| Users must find an alternative CI/CD solution and complete their migration before the sunset period ends. NoteWe recommend and offer a strategic integration with GitHub Actions to replace JFrog Pipelines as a CI/CD solution. For JFrog Platform automation, please explore our new Workers solution, REST APIs, and the JFrog CLI. |
Insight | Insight | JFrog Insight is in sunset mode and will reach end-of-life in February 2025 for Cloud customers, end of Q2 2025 for Self-Hosted customers. This product will no longer receive feature updates during the sunset and will be unavailable as of the EoL date. | JFrog will provide alternatives using APIs. For more information see Insight Alternatives. | |
Artifactory | Use of CocoaPods Git configuration using the | This feature will reach end-of-life in July 2025. | Enable CocoaPods CDN for your CocoaPods repositories. For more information, see Use CocoaPods CDN. | |
Artifactory | Cargo Git Indexing | This feature will reach end-of-life at the end of Q2, 2024. | Starting July 1, 2024, all upcoming JFrog Artifactory versions will exclusively feature the Sparse Index Protocol by default, and the use of Git indexing will be discontinued. | Enable Sparse indexing for your Cargo client: for more information, see Transitioning from Cargo Git to Sparse Index Protocol |
Artifactory | Support for Helm client versions under 3.0.0 | This feature will reach end-of-life on January 1st, 2024. | Starting November 1st, 2024, all upcoming JFrog Artifactory versions will use Helm Relative URL for indexing Helm charts, and remove the support for all Helm client versions under 3.0.0 | For more information about migrating Helm v2 to v3 see: How to migrate from Helm v2 to Helm v3 |
Artifactory | RubyGems | As announced in the Artifactory 7.58.1 release notes, RubyGems has deprecated their support of the Dependency REST API, and JFrog is removing the support to align with RubyGems. For more information, please read this blog post by RubyGems: RubyGems.org Dependency API Deprecation This feature will reach end-of-life at the end of Q1, 2024. | On March 1st, 2024, Artifactory will remove the support of the Dependencies REST APIs for local repositories. We extended the date to March 1st, 2024, to allow our customers to upgrade. | Use the RubyGems Compact Index REST API instead of the deprecated REST API. For more information about local repositories, see: ARTIFACTORY: RubyGems.org Local Repositories Dependency API Deprecation For more information about remote repositories, see: ARTIFACTORY: RubyGems.org Dependency API Deprecation |
Artifactory | API Key | As notified in Artifactory 7.47.10, support for API Key was removed in a future release. To ease customer migration to reference tokens, which replaces API key, we disabled the ability to create new API keys at the end of Q3 2024. The ability to use API keys was removed at the end of Q4 2024. For more information, see JFrog API Key Deprecation Process. | The deprecation process of the API Keys is follows:
|
|