Skip to content

fix: build production packages from release branch instead of master#422

Closed
Kobikg78 wants to merge 1 commit into
masterfrom
fix/production-workflow-use-release-branch
Closed

fix: build production packages from release branch instead of master#422
Kobikg78 wants to merge 1 commit into
masterfrom
fix/production-workflow-use-release-branch

Conversation

@Kobikg78

Copy link
Copy Markdown
Collaborator

Summary

  • Build-Production-Packages now checks out RELEASE_BRANCH_NAME instead of master
  • Generate-Tag now tags the release branch HEAD instead of master
  • notify-team Slack step reads SDK versions from the release branch

Why

Backport releases (e.g. 6.17.900 while master is at 6.18.x) were building from master, producing a package with the wrong SDK versions. This also caused Generate-Tag to tag the wrong commit.

Test plan

  • Merge this PR
  • Trigger workflow_dispatch on release 6.17.900 — verify it checks out the release branch and builds correct SDK versions

🤖 Generated with Claude Code

Backport releases (e.g. 6.17.x while master is on 6.18.x) require the
build to use the release branch content, not master. Also tags and reads
SDK version info from the release branch for correct Slack notifications.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Kobikg78 Kobikg78 closed this Jun 15, 2026
@Kobikg78 Kobikg78 deleted the fix/production-workflow-use-release-branch branch June 15, 2026 09:35
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