Migration: PicPeak has moved to its own GitHub organization (June 2026)

[the-luap]

PicPeak's GitHub home and Docker image registry moved in June 2026. Read this if your docker-compose.yml stopped pulling, your CI broke, or you came here from a stale link.

What changed

	Before	After
Repo URL	github.com/the-luap/picpeak	github.com/PicPeak/picpeak
Docker images	ghcr.io/the-luap/picpeak/{backend,frontend}	ghcr.io/picpeak/picpeak/{backend,frontend}
Active dev branch	beta	main
Stable channel branch	main	stable

The single edit operators need to make

In your docker-compose.yml:

-    image: ghcr.io/the-luap/picpeak/backend:${PICPEAK_CHANNEL:-stable}
+    image: ghcr.io/picpeak/picpeak/backend:${PICPEAK_CHANNEL:-stable}
-    image: ghcr.io/the-luap/picpeak/frontend:${PICPEAK_CHANNEL:-stable}
+    image: ghcr.io/picpeak/picpeak/frontend:${PICPEAK_CHANNEL:-stable}

Then:

docker compose pull
docker compose up -d

What auto-redirects (no edit needed)

• Browser links + git clone + git fetch against github.com/the-luap/picpeak → handled by GitHub's repo-rename redirect indefinitely.
• API calls to api.github.com/repos/the-luap/picpeak → same.

What does NOT auto-redirect

• GHCR image paths. ghcr.io/the-luap/picpeak/* returns 404. You must update your compose file.

Full migration details

• Operator-facing one-pager: docs/migration-to-org.md
• Tracking issue with the full migration plan: [OPS] Repo migration to org + branch rename (beta→main, main→stable) + in-app warning + new contribution workflow #669
• Contributor branch-model docs: CONTRIBUTING.md § Branch model

For contributors

• Feature PRs and most bugfix PRs → target main
• Bugfix that needs to ship to current stable users → small surgical PR against stable (see CONTRIBUTING.md for the hard rule on PR scope)
• The "fork from beta" instruction is now "fork from main"

Got stuck?

Open a new issue with the error message and what command produced it. Tag this issue (#NNN) for context.

---

This issue is pinned as a permanent reference. It will stay open through the migration window and beyond — no action required from you on it.

[Rekoo-PS]

trying to upgrade i'm getting this error
2026-06-30T13:22:10.055526 backend Error Head "https://ghcr.io/v2/picpeak/picpeak/backend/manifests/main": unauthorized

[the-luap]

Sorry — that was a leftover from the org migration that I missed. The two GHCR packages defaulted to private when first published under the new org, and the visibility flip was on my checklist but didn't actually get clicked.

Both picpeak/backend and picpeak/frontend are public now. Anonymous pulls verified working. Please retry docker compose pull — should work immediately.

[Rekoo-PS]

Sorry — that was a leftover from the org migration that I missed. The two GHCR packages defaulted to private when first published under the new org, and the visibility flip was on my checklist but didn't actually get clicked.

Both picpeak/backend and picpeak/frontend are public now. Anonymous pulls verified working. Please retry docker compose pull — should work immediately.

Great its Working now .💯