Skip to content

Fix release request startup and retry native SDK builds - #3

Merged
JBailes merged 1 commit into
mainfrom
fix/release-request-entrypoint
Nov 15, 2026
Merged

JBailes merged 1 commit into
mainfrom
fix/release-request-entrypoint

Conversation

@JBailes

@JBailes JBailes commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

The first merged release run stopped in revision resolution with ModuleNotFoundError: release: GitHub executes shell:python blocks from a temporary script directory, so they do not import modules from the checkout as python -c did locally. No private source checkout, compilation or artifact upload ran.

Resolve requests through the existing release.py command entry point invoked from bash, emitting only the exact commit=SHA GitHub output record. Add a subprocess regression covering the real command from a separate directory, manual overrides, generic failures and invalid requests. Add an optional positive attempt field so a reviewed PR can retry the same unpublished revision without moving its source tag; request attempt 2 for the existing engine revision.

Validation: nine publication-boundary tests pass; actionlint, staged-content and complete-public-history audits pass. PR CI has no source credential. Merging this PR automatically retries the three native SDK builds with the existing source secret. SDK images are built only by CI.

@JBailes JBailes changed the title Resolve SDK requests through the release command entry point Fix release request startup and retry native SDK builds Nov 15, 2026
@JBailes
JBailes merged commit 6bba3fa into main Nov 15, 2026
1 check 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