Skip to content

fix: require SDK release PR approval#1084

Merged
dhruva-vapi merged 1 commit into
mainfrom
dhruva/prism-1030-sdk-release-pr-approval
Jun 25, 2026
Merged

fix: require SDK release PR approval#1084
dhruva-vapi merged 1 commit into
mainfrom
dhruva/prism-1030-sdk-release-pr-approval

Conversation

@dhruva-vapi

@dhruva-vapi dhruva-vapi commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Summary

  • require Fern-managed server SDK generation to use pull-request mode by default
  • remove manual workflow-dispatch toggles that allowed accidental direct SDK release generation
  • add callable PHP and Swift SDK release workflows so they match the other server SDK release jobs

Why

Branch protection should make SDK release changes reviewable before they land. The current docs/Fern release path could still generate SDK commits/releases directly, which left package registries out of sync and gave Vapi no human approval point.

Test Plan

  • ruby -e 'require "yaml"; ARGV.each { |f| YAML.load_file(f); puts "parsed #{f}" }' fern/apis/api/generators.yml .github/workflows/release-{ts,python,go,ruby,csharp,java,php,swift}-sdk.yml
  • fern check

Linear: PRISM-1030

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@github-actions

Copy link
Copy Markdown
Contributor

@dhruva-vapi dhruva-vapi force-pushed the dhruva/prism-1030-sdk-release-pr-approval branch from c99d6ee to dc33ab1 Compare June 25, 2026 21:05
@dhruva-vapi dhruva-vapi merged commit 71c3e0f into main Jun 25, 2026
8 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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.

2 participants