Deprecations in Process

JFrog Release Information

Content Type
Release Notes
ft:sourceType
Paligo

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

Use of CocoaPods Git configuration using the cocoapods-art plugin.

This feature will reach end-of-life at the end of Q1, 2025.

Enable CocoaPods CDN for your CocoaPods repositories. For more information, see Use CocoaPods CDN.Use CocoaPods CDN

Platform

Classic UI Navigation

For Cloud customers, the classic UI navigation will be deprecated as part of a gradual rollout starting 11 July 2024.

For Self-Hosted customers, the classic UI navigation will be deprecated in the next Self-Hosted release of October, 2024.

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.0Relative URL Support for Helm Repositories

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 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 is slated to be removed in a future release. To ease customer migration to reference tokens, which replaces API key, we are disabling the ability to create new API keys at the end of Q3 2024. The ability to use API keys will be removed at the end of Q4 2024. For more information, see JFrog API Key Deprecation Process.User ProfileJFrog API Key Deprecation Process

The deprecation process of the API Keys will be as 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.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.API Key User Collection for Cloud Customers

  1. From Artifactory version 7.98, you will not be able to create new API keys through UI or API.

  2. By the end of Q4 2024, we will no longer support API keys.

  1. Read this blog post on the API Key deprecation process.

  2. Follow the instructions in the API Key Deprecation Process to learn how to log your users' username and authentication methods.API Key

  3. 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.User Profile

Artifactory

Unexpired password for a single-user endpoint

In an upcoming release of Artifactory, JFrog will expire the "Unexpire Password for a Single User" endpoint from RT REST APIs and the UI that goes with it (once API v1 is fully deprecated). This means this API will not be available in Artifactory REST API V2.