Deprecations in Process

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	Release Lifecycle Management (RLM)	RLM will reach end-of-life on January 31, 2028.	RLM feature development, patches, and security fixes (except for critical security fixes) will cease after July 31, 2026. For more information, see JFrog Release Lifecycle Management Deprecation - End of Life.	Users are encouraged to migrate to JFrog AppTrust for lifecycle management.
Artifactory	Artifactory security REST APIs	SaaS: 30 January 2027 Self-managed: January version (disabled), April version (removed)	As notified in Artifactory 7.161.5, Artifactory User, Groups, Token, and Permissions management REST API endpoints are being deprecated and replaced with Access REST API endpoints to improve security. This update may require changes to your automations to ensure continued functionality. For more information and migration steps to the new access endpoints, see the migration steps provided in Deprecated JFrog APIs. SaaS users: The endpoints are deprecated and will be removed on 30 January 2027, after which they will no longer be usable. Self-Managed users: In the January Self-Managed Artifactory version, the endpoints will be disabled via a feature flag. This begins a grace period of 90 days for you to manage the migration to the new endpoints. In the April Self-Managed Artifactory version, the endpoints will be removed and will no longer be usable. The following endpoints are affected: Expire Password for a Single User Expire Password for All Users Save Security Configuration Get Permission Targets Delete Group Get Tokens Revoke Token Delete Permission Target Get Security Configuration Change Password Unlock Locked Out User Set Password Expiration Policy	For more information and migration steps to the new access endpoints, see the migration steps provided in Deprecated JFrog APIs.
Artifactory	Artifact Sync Download REST API	SaaS: 26 April 2028 Self-managed: April 2028 Self-Managed minor Artifactory version	The Artifactory Artifact Sync Download REST API is being deprecated and replaced with the Retrieve Artifact REST API, which might require changes to your automations. SaaS Users: This endpoint will reach end-of-life on 26 April 2028. On that date, it will be disabled by default. Self-Managed Users: in the April 2028 Self-Managed Artifactory version, this endpoint will be disabled by default. For more information, see Deprecated JFrog APIs.	Check whether you are using the deprecated REST API and switch to the new Retrieve Artifact API. For more information, see Deprecated JFrog APIs.
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	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	Artifactory PostgreSQL 13 and 14 Support	Vendor end of life: PostgreSQL 13: November 13, 2025 PostgreSQL 14: November 12, 2026	Artifactory Self-Managed support is deprecated for: PostgreSQL 13, which has reached vendor end of life PostgreSQL 14, which will reach vendor end of life on the date shown	Upgrade to a supported PostgreSQL version, 15.x to 17.x. For more information, see Artifactory Database Requirements.
Artifactory	Artifactory MySQL 8.0 Support	MySQL 8.0 vendor end of life: April 2026.	Artifactory Self-Managed support for MySQL 8.0 is deprecated. MySQL 8.0 has reached vendor end of life.	Upgrade to MySQL 8.4 LTS. For more information, see Artifactory Database Requirements.
Artifactory	Artifactory MariaDB 10.5 and 10.6 Support	Vendor end of life: MariaDB 10.5 Community: June 24, 2025 MariaDB 10.5 Enterprise: July 16, 2025 MariaDB 10.6 Community: July 6, 2026	Artifactory Self-Managed support is deprecated for: MariaDB 10.5, which has reached vendor end of life MariaDB 10.6 Community, which has reached vendor end of life	Upgrade to MariaDB 10.11.x or 11.4.x. For more information, see Artifactory Database Requirements.
Artifactory	Hugging Face Repositories Legacy Layout	As of June 2026, the Hugging Face repository layout will be deprecated. All new local and remote Hugging Face repositories use the new Machine Learning repository layout by default. Any older repositories must be migrated before June 2026 to preserve complete functionality.	The process is automated and no steps need to be taken by Artifactory users.	No steps need to be taken. However, users are encouraged to proactively migrate older Hugging Face repositories to the new layout. For more information, see Migrate Legacy Hugging Face Repositories.
Pipelines	Pipelines	Pipelines will reach end-of-life on May 1, 2026.	For Cloud and Self-hosted customers, Pipelines will be deprecated as of May 1, 2026. Please note the following: There will be no updates beyond bug and security fixes between Nov 1, 2024, and May 1, 2026. Patches and Fixes Release Cloud: Releases automatically Self-hosted: Releases Quarterly	Users must find an alternative CI/CD solution and complete their migration before the sunset period ends.
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.
Artifactory	Use of CocoaPods Git configuration using the `cocoapods-art` plugin.	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 `/dependency` REST API for local repositories	As announced in the 7.58.1 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 v7.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: Self-hosted Artifactory version 7.47.10 includes the option to log users' authentication methods. This allows administrators to view and warn users using API Keys regarding the upcoming deprecation. See API Key User Collection for Self-Hosted Customers. Cloud Artifactory version 7.63.5 includes the option to view and download the list of users using API Keys regarding the upcoming deprecation. See API Key User Collection for Cloud Customers. From Artifactory version 7.98, you are not authorized to create new API keys through UI or API. We no longer support API keys.	Read this blog post on the API Key deprecation process. Follow the instructions in the API Key Deprecation Process to learn how to log your users' username and authentication methods. Begin changing your users' authentication to the new Identity Token format (i.e., a reference token), which can be used to replace the API Keys.
Artifactory	Legacy Federation	July 2027	An 18-month period during which customers are requested to migrate to the new Artifactory Federation Service.	We encourage all users to begin planning their transition to take advantage of RTFS's superior architecture and enhanced capabilities