![]() If your workflow depends on the current bugged behavior, this fix will introduce a breaking change. User permissions will be checked after the most recent package is found.Īfter the change, download requests for users without correct permissions will be rejected. In GitLab 17.0, the package finder logic will be fixed so that the “most recent” package is the last updated name and version of a package in a group. It is possible for a user with different permissions in different projects to download the wrong Maven package. The Maven package finder always returns the most recent package, but the “most recent” filter depends on user permissions. However, there is a limitation that affects duplicate package names hosted in different projects. The package finder first locates the package within the group, and then finds the file within the package. The Maven repository exposes an API endpoint at the group level that allows Maven clients to download files from a specific package. ![]() To discuss this change or learn more, see the deprecation issue.Removal in GitLab 17.0 ( breaking change). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |