fix: UI extension release deploy#58
Merged
wcole1-godaddy merged 3 commits intoJun 12, 2026
Merged
Conversation
…essages Add esbuild to external dependencies in build config and enhance error logging in bundler with detailed output file information. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Include UI extensions from config when creating releases. Validates that extensions have at most one target (API limitation) and includes extension data in the release mutation. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
llessa-godaddy
changed the title
- Add integration test for creating releases with UI extensions - Update test fixture to support uiExtensions in release response - Verify extensions are properly included in release data Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
llessa-godaddy
commented
Jun 12, 2026
| extension: pkg.name, | ||
| entryPath, | ||
| config, | ||
| error: errorMessage, |
Contributor
Author
There was a problem hiding this comment.
let me know if error logging is showing info that shouldn't be user-facing. We couldn't debug the esbuild issue until this logged a full error message from esbuild
wcole1-godaddy
approved these changes
Jun 12, 2026
llessa-godaddy
added a commit
to llessa-godaddy/cli
that referenced
this pull request
Jun 12, 2026
Merged
wcole1-godaddy
pushed a commit
that referenced
this pull request
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
include uiExtensions in input to app registry create release call
for verification, include it in mutation output, too.
This pull request introduces support for UI extensions in the release process, adds validation to ensure only one target per UI extension, and improves error logging in the extension bundler. The changes also update the GraphQL schema and input validation to accommodate the new UI extension format. Additionally, a minor build configuration update ensures
esbuildis handled as an external dependency.UI Extension Support and Validation:
ReleaseUiExtensioninterface and updated the release flow to extract, validate (only one target per extension), and map UI extensions from the config, making them available in release data. [1] [2] [3] [4]uiExtensionsfield, ensuring that releases can include UI extension metadata. [1] [2]Error Handling and Logging Improvements:
bundleExtensionEffectto capture detailed information when esbuild fails or when expected output files are missing, aiding debugging and transparency. [1] [2]Build Configuration:
esbuildas an external dependency in the build script to ensure its binary can be accessed correctly.