---
updatedAt: 2026-08-10T02:58:35.000Z
agentTools:
  siteIndex: https://docs.jfrog.com/llms.txt
  projectIndex: https://docs.jfrog.com/releases/llms.txt
---

# 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).

<Table align={["left","left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Product
      </th>

      <th>
        What is being deprecated?
      </th>

      <th>
        Timeframe
      </th>

      <th>
        Deprecation process and next steps
      </th>

      <th>
        What has to be done?
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Artifactory
      </td>

      <td>
        Release Lifecycle Management (RLM)
      </td>

      <td>
        RLM will reach end-of-life on January 31, 2028.
      </td>

      <td>
        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](/docs/release-lifecycle-management-deprecation-end-of-life).
      </td>

      <td>
        Users are encouraged to migrate to <Anchor target="_blank" href="/governance/docs/jfrog-apptrust">JFrog AppTrust</Anchor> for lifecycle management.
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        Artifactory Access REST APIs
      </td>

      <td>
        These APIs will be removed in the future based on analysis of usage.
      </td>

      <td>
        These APIs will be disabled by default in an upcoming Artifactory version and removed in a subsequent version.
      </td>

      <td>
        Check whether you are using any of the deprecated REST APIs and take the migration steps to switch to the new endpoints. For more information, see <Anchor target="_blank" href="/integrations/docs/deprecated-jfrog-apis">Deprecated JFrog APIs</Anchor>.
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        Composer 1.x
      </td>

      <td>
        December 2026
      </td>

      <td>
        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 <Anchor target="_blank" href="https://blog.packagist.com/packagist-org-shutdown-of-composer-1-x-support-postponed-to-september-1st-2025/">deprecation notice</Anchor> from Packagist.
      </td>

      <td>
        Upgrade to Composer 2.0
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        Artifactory Microsoft SQL Server 2016 / 2017 Support
      </td>

      <td>
        End of Q3-2025
      </td>

      <td>
        Artifactory Self-Hosted versions released after September 2025 will no longer include support for MSSQL 2016 and MSSQL 2017.
      </td>

      <td>
        Upgrade to a newer database version.
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        Hugging Face Repositories Legacy Layout
      </td>

      <td>
        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​​](/artifactory/docs/machine-learning-repositories#machine-learning-repository-structure) by default. Any older repositories must be migrated before June 2026 to preserve complete functionality.
      </td>

      <td>
        The process is automated and no steps need to be taken by Artifactory users.
      </td>

      <td>
        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​​](/artifactory/docs/hugging-face-repositories#migrate-legacy-hugging-face-repositories).
      </td>
    </tr>

    <tr>
      <td>
        Pipelines
      </td>

      <td>
        Pipelines
      </td>

      <td>
        Pipelines will reach end-of-life on May 1, 2026.
      </td>

      <td>
        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
      </td>

      <td>
        Users must find an alternative CI/CD solution and complete their migration before the sunset period ends.
      </td>
    </tr>

    <tr>
      <td>
        Insight
      </td>

      <td>
        Insight
      </td>

      <td>
        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.
      </td>

      <td>

      </td>

      <td>
        JFrog will provide alternatives using APIs.
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        Use of CocoaPods Git configuration using the `cocoapods-art` plugin.
      </td>

      <td>
        This feature will reach end-of-life in July 2025.
      </td>

      <td>

      </td>

      <td>
        Enable CocoaPods CDN for your CocoaPods repositories. For more information, see [Use CocoaPods CDN](/artifactory/docs/cocoapods-repositories#connect-cocoapods-cdn-to-artifactory).
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        Cargo Git Indexing
      </td>

      <td>
        This feature will reach end-of-life at the end of Q2, 2024.
      </td>

      <td>
        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.
      </td>

      <td>
        Enable Sparse indexing for your Cargo client: for more information, see <Anchor target="_blank" href="https://jfrog.com/help/r/artifactory-transitioning-from-cargo-git-to-sparse-index-protocol/artifactory-transitioning-from-cargo-git-to-sparse-index-protocol">Transitioning from Cargo Git to Sparse Index Protocol</Anchor>
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        Support for Helm client versions under 3.0.0
      </td>

      <td>
        This feature will reach end-of-life on January 1st, 2024.
      </td>

      <td>
        Starting November 1st, 2024, all upcoming JFrog Artifactory versions will use [Helm Relative URL for indexing Helm charts](/artifactory/docs/kubernetes-helm-chart-repositories), and remove the support for all Helm client versions under 3.0.0
      </td>

      <td>
        For more information about migrating Helm v2 to v3 see: <Anchor target="_blank" href="https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/">How to migrate from Helm v2 to Helm v3</Anchor>
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        RubyGems `/dependency` REST API for local repositories
      </td>

      <td>
        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: <Anchor target="_blank" href="https://blog.rubygems.org/2023/02/22/dependency-api-deprecation.html">RubyGems.org Dependency API Deprecation</Anchor>

        This feature will reach end-of-life at the end of Q1, 2024.
      </td>

      <td>
        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.
      </td>

      <td>
        Use the RubyGems Compact Index REST API instead of the deprecated REST API.

        For more information about local repositories, see: <Anchor target="_blank" href="https://jfrog.com/help/r/artifactory-rubygems-org-local-repositories-dependency-api-deprecation/artifactory-rubygems.org-local-repositories-dependency-api-deprecation">ARTIFACTORY: RubyGems.org Local Repositories Dependency API Deprecation</Anchor>

        For more information about remote repositories, see: <Anchor target="_blank" href="https://jfrog.com/help/r/artifactory-rubygems-org-dependency-api-deprecation">ARTIFACTORY: RubyGems.org Dependency API Deprecation</Anchor>
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        API Key
      </td>

      <td>
        As notified in v7.47.10 support for API Key was removed in a future release. To ease customer migration to <Anchor target="_blank" href="/administration/docs/access-tokens#create-an-admin-scoped-reference-token">reference tokens</Anchor>, 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](/user-management/docs/api-key#jfrog-api-key-deprecation-process).
      </td>

      <td>
        The deprecation process of the API Keys is follows:

        1. - 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 <Anchor target="_blank" href="/user-management/docs/api-key#api-key-user-collection-for-self-hosted-customers">API Key User Collection for Self-Hosted Customers</Anchor>.
           - 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 <Anchor target="_blank" href="/user-management/docs/api-key#api-key-user-collection-for-cloud-customers">API Key User Collection for Cloud Customers</Anchor>.
        2. From Artifactory version 7.98, you are not authorized to create new API keys through UI or API.
        3. We no longer support API keys.
      </td>

      <td>
        1. Read <Anchor target="_blank" href="https://jfrog.com/knowledge-base/platform-api-key-deprecation-and-the-new-reference-tokens/">this</Anchor> blog post on the API Key deprecation process.
        2. Follow the instructions in the [API Key Deprecation Process](/user-management/docs/api-key#jfrog-api-key-deprecation-process) to learn how to log your users' username and authentication methods.
        3. Begin changing your users' authentication to the

           new <Anchor target="_blank" href="/user-management/docs/identity-tokens#understanding-identity-tokens">Identity Token</Anchor> format (i.e., a reference token), which can be used to replace the API Keys.
      </td>
    </tr>

    <tr>
      <td>
        Artifactory
      </td>

      <td>
        Legacy Federation
      </td>

      <td>
        July 2027
      </td>

      <td>
        An 18-month period during which customers are requested to migrate to the new Artifactory Federation Service.
      </td>

      <td>
        We encourage all users to begin planning their transition to take advantage of RTFS's superior architecture and enhanced capabilities
      </td>
    </tr>
  </tbody>
</Table>