What to prepare
- An owner account with a linked GitHub identity and repository push access.
- Node.js 22 or later and the integrity-locked official CLI with an isolated owner home.
- An independently verified import or publication result.
Use the publishing tool, not an issue
LobeHub maintainers direct listing and refresh requests to their official CLI. Browser login and GitHub connection are owner actions. An issue in the application repository is not a substitute for marketplace publication; unsupported authentication is a visible blocker.
Submission workflow
- Read the official publishing instructions.
- Sign in and connect the source-owner GitHub identity.
- Review the generated declaration and authorize its exact source revision and release metadata.
- Follow the asynchronous import and verify the matching public record.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- Missing owner authentication or repository access.
- An asynchronous import treated as a verified public listing.
Primary sources
Checked 2026-10-30. Follow the destination’s current instructions if its requirements change.