<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=595277) </details> <!--IssueSummary end--> ## Overview We have recently migrated the backend infrastructure behind `packages.gitlab.com` to improve the reliability and performance of our Linux package distribution. As part of this migration, there are some changes that may affect how you interact with our package repositories. For full details on what changed and what actions you may need to take, please refer to our blog post: **TODO: Add link to blog post once published** ## Summary of changes - **URL format changes**: Some repository URL formats are changing. Old URLs will continue to work via redirects for the next 6 months, but customers should update their configurations to the new formats. - **Firewall / network allowlist**: Package downloads now redirect to Google Cloud Storage (`storage.googleapis.com`). Customers with strict firewall rules may need to update their allowlists. - **Repository mirroring**: Customers mirroring GitLab package repositories must update to the new URL format for correct behavior. - **UI changes**: The package browsing interface at `packages.gitlab.com` is being updated with a new UI. - **GitLab Runner `noarch` packages**: Changes to how Runner `noarch` packages are distributed for RPM-based distributions. ## Purpose of this issue This issue is a central place for customers to **report problems and provide feedback** related to these changes. If you encounter any issues, please comment below with: 1. The exact URL you are trying to access 2. The error message or unexpected behavior you are seeing 3. Your operating system and package manager version 4. Whether you are using repository mirroring or direct package access 5. Any firewall or proxy configuration that may be relevant