Registered next-docker's Release and Served launcher workflows

[acburdine]

GitHub dispatches a workflow only when its file is on the default branch. release.yml and launcher.yml exist only on next-docker, where releases are cut, so neither can be run (gh workflow run release.yml --ref next-docker returns 404).

These two files are dispatch-only stand-ins on main that register the workflows. Dispatched with --ref next-docker, GitHub runs next-docker's own files. Run on main, they fail with a message saying where to run them.

• Existing installations never run workflows, so nothing they use changes.
• next-docker's real files replace these when it merges into main (S6b).

Once merged:

gh workflow run release.yml --repo TryGhost/ghost-docker --ref next-docker

🤖 Generated with Claude Code

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: a0c901a8-9694-4ec1-9277-961b3b6d5519

📥 Commits

Reviewing files that changed from the base of the PR and between fce74d5 and 35b8643.

📒 Files selected for processing (2)

• .github/workflows/launcher.yml
• .github/workflows/release.yml

 _____________________________________________________________________________________________________________________
< Use a project glossary. Create and maintain a single source of all the specific terms and vocabulary for a project. >
 ---------------------------------------------------------------------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}