Skip to content

ci: GHCR+Hub Docker, auto FnOS, cascade desktop after release - #459

Merged
jubaoliang merged 4 commits into
developfrom
ci/docker-publish-ghcr
Aug 27, 2026
Merged

ci: GHCR+Hub Docker, auto FnOS, cascade desktop after release#459
jubaoliang merged 4 commits into
developfrom
ci/docker-publish-ghcr

Conversation

@jubaoliang

@jubaoliang jubaoliang commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Dual-publish Docker to GHCR (ghcr.io/tencentcloud/octop) + Docker Hub; docs/FnOS use GHCR only (no vanilla tags).
  • After tag: Release ∥ Docker ∥ Desktop; FnOS FPK cascades from Release (reuse wheel + wait for GHCR).
  • Desktop: restrict octop-desktop.yml to v* + workflow_dispatch; Auto Tag dispatches it with attach_release=true.
  • Merged latest develop (includes schema v10 fix fix(db): duplicate v10 migration skipped thread projection tables #461).

Companion on main (Auto Tag runs from main): #463

Test plan

  • CI green on this PR (Linux + Windows)
  • Next release: Auto Tag dispatches release.yml, docker-publish.yml, octop-desktop.yml
  • FnOS starts after GitHub Release; Desktop assets appear on the same v* release
  • Ordinary branch pushes do not start Desktop Package

jubaoliang-tencent and others added 4 commits August 27, 2026 07:35
Cascade FnOS FPK from Release (reuse GHCR image and release wheel), keep
Docker Hub sync, and fix workflow_dispatch version tags for Auto Tag.

Co-authored-by: Cursor <cursoragent@cursor.com>
Pick up schema v10 fix (#461) so CI matches develop.

Co-authored-by: Cursor <cursoragent@cursor.com>
Stop running the six-platform desktop matrix on every branch push.
Auto Tag dispatches Octop Desktop alongside Release and Docker so
artifacts attach to the same v* GitHub Release.

Co-authored-by: Cursor <cursoragent@cursor.com>
@jubaoliang jubaoliang changed the title ci: GHCR+Hub Docker publish and auto FnOS after Release ci: GHCR+Hub Docker, auto FnOS, cascade desktop after release Aug 27, 2026
@jubaoliang
jubaoliang merged commit 803c859 into develop Aug 27, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants