Skip to content

fix: publish SDK after Release Please release#214

Merged
dodeja merged 2 commits into
mainfrom
fix/sdk-release-publish-automation
May 7, 2026
Merged

fix: publish SDK after Release Please release#214
dodeja merged 2 commits into
mainfrom
fix/sdk-release-publish-automation

Conversation

@dodeja
Copy link
Copy Markdown
Contributor

@dodeja dodeja commented May 7, 2026

Summary

  • dispatch the SDK publish workflow from the Release Please workflow when an SDK release is created
  • keep npm publishing in the existing trusted-publishing workflow file
  • add a manual workflow_dispatch tag input so missed releases can be published by tag

Verification

  • ruby YAML parse for both workflow files
  • git diff --check

@vercel
Copy link
Copy Markdown

vercel Bot commented May 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
api Ready Ready Preview, Comment May 7, 2026 6:37pm

Request Review

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 7, 2026

Target branch is in the excluded branches list.

@dodeja dodeja merged commit 123bec3 into main May 7, 2026
8 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.

1 participant