Trigger a skill-sync when the SDK is published

[claude]

Requested by Yarden Danan · Slack thread

Before: the base44-sdk skill in base44/skills only refreshed when the CLI released. Publishing base44/javascript-sdk triggered nothing, so the SDK skill drifted out of date. (The skills repo already has a sync-sdk-skill workflow waiting on an sdk-release dispatch — nothing was ever sending it.)

After: publishing the SDK through its manual publish workflow now also notifies base44/skills, which kicks off the sync-sdk-skill job and opens a skill-update PR — exactly what a CLI release already does.

How

Edited .github/workflows/manual-publish.yml (the release path), mirroring base44/cli's equivalent:

• Added a Notify skills repo step (last step of the publish job, after the git tag is pushed and the release is created) that sends a repository_dispatch (peter-evans/repository-dispatch@v4) to base44/skills with event-type: sdk-release and client-payload {"version": "v${{ env.NEW_VERSION }}", "release_name": "..."} — version is the only field the skills sync workflow reads (it uses it as the checkout ref), and it matches the v-prefixed git tag the job creates.
• Added owner: base44 to the existing actions/create-github-app-token@v2 step (id generate-token) so the minted token is org-scoped and allowed to dispatch to another repo (the CLI sets this; the SDK didn't).
• Added a notify_skills_repo input (default true) and gated the step on it plus non-dry-run, matching the CLI.
• Reused the existing NEW_VERSION env var (already written to $GITHUB_ENV by the version-bump steps, so ${{ env.NEW_VERSION }} resolves here) — no export needed. Omitted release_url since the release step exposes no referenceable URL output and the skills receiver doesn't read it.
• Reuses the app-token secret/var already configured in this repo (BASE44_GITHUB_ACTIONS_APP_PRIVATE_KEY / BASE44_GITHUB_ACTIONS_APP_ID) — no new secret needed.

---

Generated by Claude Code

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/sdk@0.8.39-pr.232.affea8a

Prefer not to change any import paths? Install using npm alias so your code still imports @base44/sdk:

npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.39-pr.232.affea8a"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "@base44/sdk": "npm:@base44-preview/sdk@0.8.39-pr.232.affea8a"
  }
}

• 📦 Preview Package: @base44-preview/sdk@0.8.39-pr.232.affea8a
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}

[Paveltarno]

lgtm 🔥