Artifactory 7.98

RTDEV-55585

When Debian packages are uploaded directly to the root directory:

Cloud: 7.109.3

Self-hosted: 7.104.21

Suggested workaround:

To avoid unintended cleanup/archive, always upload Debian packages to a subdirectory rather than the root.

RTFACT-31038

An unannounced change was introduced by Conda Forge upstream which impacts Artifactory's ability to resolve package metadata and dependencies with virtual Conda repositories. For more information see this article.

7.98.15

Suggested workaround:

Use the Conda Remote Repository Directly: Instead of relying on the Virtual Conda repository, users can directly use the Conda remote repository (repo.anaconda.com/conda-forge) to download packages.

JFCON-776

When applying a new Artifactory license key to replace an old one that is about to expire, the expiration date for the new license may not change in the Artifactory UI.

This is because Artifactory relies on the JPD Entitlements to define the expiration date. In cases where Artifactory cannot fetch new Entitlements from the JFrog Entitlements server, it will continue to use the Entitlements stored in your JPD, along with the expiration date of the old license.

This is a known issue since Artifactory version 7.98. However, this issue also impacts Artifactory versions prior to the Artifactory 7.98 release.

N/A

Suggested next actions:

For more information, see JFConnect Microservice.

RTDEV-46375

The remote repository setting to Block Mismatching Mime Types can be overridden by the settings of the upstream server. For example, if the upstream server allows all MIME types (Accept: */*), this will override the Artifactory setting to block certain MIME types as defined in system properties.Other Advanced Settings for Remote Repositories

N/A

RTDEV-51106

When performing pull replication, properties generated locally by Artifactory are deleted from the target when the properties are unchanged from the previous replication execution.Pull Replication

This behavior occurs only when you have selected the options to synchronize artifact properties and synchronize artifact deletions. See Configure Pull Replication.Configure Pull Replication

TBD

Suggested workaround:

Add a custom property to the package. This will prevent the locally-generated properties from being deleted during pull replication.

INST-9289

After upgrading to Apache Tomcat 10.1.x, the system property org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH was replaced with the Connector attribute encodedSolidusHandling.

Note that the Connector attribute encodedSolidusHandling is added by default to the Artifactory server.xml template. However, it disappears when Mission Control is enabled in your Artifactory instance.

As a result, incoming requests to Artifactory could fail with 400 Status Codes, particularly for NPM Scope packages or when trying to download Support Bundle from Artifactory UI.npm Scope Packages

7.98.9

Suggested workaround:

If Mission Control is enabled or if you have manually added the system property org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH in the past, configure the following settings in the system.yaml file under $JFrog_HOME/var/etc/system.yaml and restart Artifactory:

artifactory:
    tomcat:
        connector:
            extraConfig: "encodedSolidusHandling='DECODE'"
access:
    tomcat:
        connector:
            extraConfig: "encodedSolidusHandling='DECODE'"

INST-8592

Initially, Xms and Xmx were the standard parameters used by Java to set the JVM memory. Later, two new settings called InitialRAMPercentage and MaxRAMPercentage were introduced. These new settings have now become the recommended way to set memory for the Java Virtual Machine (JVM), replacing Xms and Xmx.

In the Artifactory JVM, the -Xms and -Xmx values are set by default in the artifactory.default file, which overrides the InitialRAMPercentage and MaxRAMPercentage values.

This means that only the -Xms and -Xmx values can be tuned for the Artifactory JVM.

7.104.5

This is a known issue since Artifactory version 7.98. However, this issue also impacts Artifactory versions prior to the Artifactory 7.98 release.