![]() This section includes all the Artifactory 7.41.x releases. Please note that from version 7.41.2, the default value is still set as 'false', so take this into consideration when creating your new virtual repositories.įixed an issue whereby, running the Create Repository REST API to create a virtual repository with multiple local repositories with the same name, displayed the local repositories many times in the WebUI.įixed an issue related to NPM packages whereby, a 404 error message was generated when running NPM Install if the package.json located under the local repo contained an extra slash.įixed an issue whereby, under certain circumstances, running a Docker Pull generated an "Unknown Blob" error if the remote cache was deleted and the client had a partial cache. Please disable the flag if your intent was to prevent new artifacts from being downloaded from the virtual repository. ![]() With the new change, setting this flag to false causes helm virtual repositories not to retrieve remote artifacts from the virtual repositories, if the download request came from a Smart repository.įor existing customers, in order not to fail downloads from your Smart Helm repositories, we have changed the feature flag value to true in the existing helm virtual repositories. Resolved Issuesįixed a Cargo package-related issue, whereby a remote Cargo remote repository could not be created without providing the gitRegistryUrl which prevented Artifactory from starting.įixed a PyPI-related issue whereby, remote PyPI artifacts yanked from the registry would not be processed by Artifactory if there were no yanked details in the remote repository.įixed an issue whereby, submitting repository-related REST API requests without a repository key returned a 500 error instead of a 400 status error.įixed an issue whereby, Crowd users were unable to download artifacts via the URL-to-File requests.įixed an issue whereby, running the Get LDAP Groups Rest API returned forceAttributeSearch as false even if it was set as true in the config.xml file.įixed an issue whereby, when running NuGet-related REST APIs, the NuGet HTTP status code returned a 403 status message instead of a 409 status message for users with write and not overwrite access while trying to upload an already-existing package.Īs part of the bug fix, the flag is still set to false, however, the behavior has changed. The token restrictions will affect non-admin users and they can be set in the Access YAML Configuration. Generate a Non-expiry Admin Token without Changing the ConfigurationĪdmins can now bypass tokens restrictions and can generate a token with any expiry they wish and create refreshable tokens without changing the configuration. Modified the Project Key Name length limitation from three to two characters. Property Set /name Validation Endpoint Changed to /propertyNameĬhanged the property set endpoint from /Name to /propertyName. Cold Storage UI ImprovementsĪdded a new Skip Trash Can checkbox allowing you to skip moving items to the trash can when creating or modifying Cold Storage Archive policies in the WebUI. CRAN Local Repository ImprovementsĪligned the CRAN Local repository to follow the CRAN spec when populating the Archive folder by introducing the following enhancements:Īdded the system property that will allow the storage of the archives in the correct hierarchy.Īdded a new Move Archives CRAN REST API, which moves the existing archives to the correct location (if the system property is enabled).įor more information, see Applying the CRAN Official Spec on Local CRAN Repositories. ![]() Feature Enhancements Added a Full Broadcast Function to the Access Federation UIĪdded the option to trigger a full broadcast from a specific Access Federation source via the Access Federation UI. Artifactory 7.42.1 is available as a Cloud version.
0 Comments
Leave a Reply. |