The initial RakuOS migration to GitLab is now complete.
RakuOS development, image publishing, and core project infrastructure are now centered around GitLab. This move gives the project a stronger long-term home for CI/CD, container image distribution, branch-based workflows, and future release operations.
What This Means
GitLab is now the primary platform for RakuOS going forward.
For the time being, the GitHub repositories and GHCR image path will remain available in a frozen state. They are being kept online temporarily so existing users can receive the final migration update that moves systems from GHCR-based image delivery over to the GitLab container registry.
Important Notes For Current Users
If you are already running RakuOS from an older GitHub / GHCR-based image source:
- GitHub is not the long-term update source anymore
- a final migration update is being left in place to move existing installs to GitLab
- after that transition, GitLab will be the primary source for ongoing image updates
Why GitHub Is Staying Up For Now
We are intentionally keeping the old GitHub-side infrastructure around for a short period so current systems are not stranded during the registry transition.
This means:
- existing users still have a path to migrate cleanly
- the update transition can happen through the normal system update flow
- we can move users over without requiring everyone to reinstall immediately
Going Forward
From this point on:
- GitLab is the primary home of RakuOS
- GitHub should be considered legacy / frozen for transition purposes
- future development and infrastructure work will increasingly happen on GitLab
Thank you to everyone who has tested, downloaded, and supported RakuOS through this migration. This is a major infrastructure step for the project, and it helps set the stage for the next phase of development.