FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

No new Container Images on registry.gitlab.com/python-gitlab/python-gitlab since v5.6.0 · Issue #3395 · python-gitlab/python-gitlab · GitHub

Repository navigation

No new Container Images on registry.gitlab.com/python-gitlab/python-gitlab since v5.6.0 #3395

Description

Description of the problem, including code/CLI snippet

As per the documentation docker images are pushed to the GitLab container registry. However, the gitlab container registry of this project's latest container image for registry.gitlab.com/python-gitlab/python-gitlab is version v5.6.0 while the py package's current version is v8.3.0.

Expected Behavior

All releases produce a container image that is pushed to https://gitlab.com/python-gitlab/python-gitlab/container_registry/592152

Actual Behavior

Since version v5.6.0 no further release was pushed as a container image to https://gitlab.com/python-gitlab/python-gitlab/container_registry/592152

Activity

  1. TimKnight01 commented on May 14, 2026

    Looks like the mirror to https://gitlab.com/python-gitlab/python-gitlab has been disabled, meaning that no new tags after 5.6.0 are in GitLab.

    The .gitlab-ci.yml file hasn't changed, so as soon as the tags get mirrored to Gitlab then the images should get build

  2. uluzox commented on Jul 14, 2026

    Author

    Can the team elaborate on why the mirror to gitlab was disabled?

  3. TimKnight01 commented on Jul 14, 2026

    @uluzox I cannot, I'm not a maintainer, all I can say from investigating is that is what has happened

  4. JohnVillalovos commented on Jul 14, 2026

    Member

    One issue is that on GitLab we no longer have the Premium level. I believe that level has to be re-applied for each year for open source projects.

    The Premium level is where "Pull" mirroring is available. That is how the sync between them is currently being done.

  5. TimKnight01 commented on Jul 14, 2026

    @JohnVillalovos yes I believe it does have to be re-applied for each year for OSS frustratingly

  6. JohnVillalovos commented on Jul 14, 2026

    Member

    One issue is: https://gitlab.com/gitlab-org/gitlab/-/work_items/543742 as at the moment the LGPL v3 license is being detected as "Other" and thus not allowing to apply as an open-source project 😢 Can see that here: https://gitlab.com/python-gitlab/python-gitlab/-/blob/main/COPYING

  7. JohnVillalovos commented on Jul 14, 2026

    Member

    I have proposed a PR to make our LGPGL v3 license be recognized by GitLab: #3420

  8. JohnVillalovos commented on Jul 29, 2026

    Member

    The LGPL license has been updated. Git Lab repository synced with current GitHub repository. Git Lab Open Source program application approved. Mirroring has started back up again. And docker images have been built for x86_64 and ARM64.

    Container registry: https://gitlab.com/python-gitlab/python-gitlab/container_registry/

    @nejch FYI about the above

  9. uluzox commented on Jul 30, 2026

    Author

    Many Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL