Repository navigation
feat: publish derives the sdkVersion floor from the built bundle - #55
Merged
Merged
Conversation
…ly, never hangs without a terminal
… never outwaits the hook
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
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.
bun widget publishderivessdkVersionfrom the built bundle (oldest SDK exporting every imported name), prints which Dash versions the widget reaches, refuses names no released SDK has, and asks before publishing a widget no stable Dash runs (--allow-prerelease-dashfor non-interactive runs). A failed publish leaves the manifest untouched; the hub release table fetch fails closed with a timeout.bun widget upgradeno longer rewritessdkVersion.Depends on a widget-contract release with
./sdk-floorand./dash-releases, and on the hub serving/api/widgets/dash-releasesbefore this ships.Need help on this PR? Tag
@codesmith-botwith what you need.