fix: republish @tooee/diff with its compiled output - #9
Merged
Conversation
`@tooee/diff@0.7.0` reached npm without its `dist` directory, so the package entry point `./dist/index.js` was missing and any import of `@tooee/diff` — including the diff subview reached through `@tooee/view` — failed to resolve. The source is unchanged; the artifact was published from a tree that had not been built. Adds a patch release note for the shared Tooee group so the workflow can republish the whole public set at `0.7.1` through npm trusted publishing, and clears the completed `0.7.0` publish lock. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Problem
@tooee/diff@0.7.0is on npm without itsdistdirectory. The tarball holds onlypackage.json,README.mdandsrc, so the export condition./dist/index.jspoints at a file that does not exist.@tooee/view@0.7.0depends on@tooee/diff@0.7.0, so diff rendering fails for anyone who installs the 0.7.0 set.The package was created by a manual publish from a tree that had not been built. The trusted-publishing path could not create the package on its first publish, so the release workflow failed with
E404. Trusted publishing for@tooee/diffis configured now.Change
group:tooeeset, so every public package moves to0.7.1together and@tooee/view@0.7.1depends on a working@tooee/diff@0.7.1..tegami/publish-lock.yamlthroughbun run tegami cleanup. Tegami confirmed all 19 packages in the lock reached npm at0.7.0.No source changes. The published artifact was the defect.
Verification
npm pack --dry-runandbun pm pack --dry-runinpackages/diffboth includedistfrom a built tree.bun run tegami check-publishreports nothing left to publish at0.7.0.bun run lint:checkandbunx tsc -b && bunx tsc -p examples.@tooee/diff@0.7.0will be deprecated on npm once0.7.1is out.