fix: publish all public workspaces and resume partial releases - #31
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
data-slot | 3718234 | Commit Preview URL Branch Preview URL |
Sep 24 2026, 11:07 AM |
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
1 participant
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.
The v1.0.0 release skipped carousel, toast, and resizable because publishing used a manually maintained package list. The published UI package consequently references unavailable carousel and toast versions.
Discover public packages from the root workspace configuration and publish them in dependency order. Dry runs consume the same plan and no longer require npm credentials. Reject mismatched release versions, missing internal dependencies, and cycles before publishing. Skip versions already present on npm so a manual run can complete a partial release; registry errors still fail the run.
Validation: all 1,773 tests pass, all packages build, repository and release-script TypeScript checks pass, and workflow shell syntax passes. Regression coverage executes the workflow shell with a simulated registry to verify partial-release recovery and failure handling.
Recovery: the manual workflow run completed successfully and published the missing 1.0.0 versions. A fresh npm install of
@data-slot/ui@1.0.0succeeds, and standalone, UI subpath, and root carousel ESM imports plus CommonJS imports have been verified against npm.Registry caveat: resizable's version endpoint and abbreviated metadata return 1.0.0, but its full-metadata endpoint still returned 404 during verification, so a normal resizable install has not yet been verified. Carousel and toast install successfully through the UI package.