Artifactory 7.71

RTDEV-45538

Related to Federated repositories:

Binary tasks for binaries that no longer exist on remote members can get stuck in the binaries_tasks table after reaching their maximum retries (10 by default). The binaries referenced by the metadata might be missing for a number of reasons; for example, they might have been deleted before the asynchronous pull task reached the remote members.

The situation described above results in many Failed to import binary with sha1 errors. The auto-healing mechanism (Artifactory 7.71.1 and above) resets the retries counter, which perpetuates the issue.

7.94.1

Workaround (before release 7.94.1): Manually delete the orphaned task.

Starting with 7.94.1, if the task reaches its maximum retries without finding the binary on any of the remote members, the task is deleted from the table.

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.71.25

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.

RTDEV-45842

Upgrading from version 7.71 directly to 7.90.x or higher fails due to a problematic artifactory revision number in 7.71 causing converters not to run.

7.90.7

Upgrade directly to 7.90.7 or above.

RTFACT-30076

Pulling Go submodules of packages when the repository is pointed to github.com will fail

7.71.3

This does not affect other remote repositories, like proxy.golang.org or others.

RTDEV-40269

When assigning repositories to a project and filtering, then clicking select all, all the repositories in the repository were selected instead of the search results that were displayed.

This might cause additional repositories to be assigned to the project not as expected, which in turn will cause repositories that were already assigned to a certain project to be removed from their original project.

7.77.13

RTDEV-36696

When enabling the setting Bypass HEAD Requests for one or more remote repositories, a connection leak might occur.

This might make resolving packages from remote resources not work as expected.

7.71.4

To avoid this issue, please verify that none of your remote repositories have the setting Bypass HEAD Requests enabled.