feat: marketplace publish path (manifest + script + staging/prod workflows)#369
Merged
Conversation
…flows) HotCRM had no way to reach the marketplace — only a GitHub-Release workflow. Adds the full publish path so it can be listed alongside the templates: - objectstack.manifest.json — marketplace metadata (manifestId app.objectstack.hotcrm, category crm, MIT, icon, readme). - scripts/publish-marketplace.mjs — single-package publisher: reads package.json + manifest + dist/objectstack.json, upserts sys_package then creates the version (auto_approve, 409 = no-op). Hardened with per-request timeout + retry (the control plane is a cold singleton) — mirrors the templates repo's publisher. - pnpm publish:marketplace (+ :dry-run). - .github/workflows/publish-staging.yml → https://cloud.objectos.app (OS_CLOUD_API_KEY_STAGING; dispatch + release) .github/workflows/publish-production.yml → https://cloud.objectos.ai (OS_CLOUD_API_KEY_PRODUCTION; manual dispatch only) Same explicit-target / org-level-secret model as the templates repo. Setup: org-level secrets OS_CLOUD_API_KEY_STAGING / _PRODUCTION (already set). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| 'Content-Type': 'application/json', | ||
| Authorization: `Bearer ${OS_CLOUD_API_KEY}`, | ||
| }, | ||
| body: JSON.stringify(body), |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HotCRM had no way to reach the marketplace — only a GitHub-Release workflow. This adds the full publish path so it can be listed alongside the templates.
manifestId: app.objectstack.hotcrm, categorycrm, MIT, icon, README).dist/objectstack.json, upsertssys_packagethen creates the version (auto_approve, 409 = no-op). Hardened with per-request timeout + retry (the control plane is a cold singleton) — mirrors the templates repo's publisher.pnpm publish:marketplace(+:dry-run).https://cloud.objectos.app(OS_CLOUD_API_KEY_STAGING; dispatch + release)https://cloud.objectos.ai(OS_CLOUD_API_KEY_PRODUCTION; manual dispatch only)Same explicit-target / org-level-secret model as the templates repo — no per-repo Environment setup; the org secrets are already configured.
After merge: dispatch
publish-staging(or withdry_run) to list HotCRM on the staging marketplace.🤖 Generated with Claude Code