Make the publish dry run walk the real path - #54
Merged
Merged
Conversation
The first dry run proved the build and the pack and nothing about the version, which is the part most likely to be wrong. It invoked `bun pm pack` directly and so skipped `publish.ts` entirely -- where the version injection lives -- and packed the committed `0.0.0`. The tarball said `redrob-code-sdk-0.0.0.tgz` and the run was green. A rehearsal that bypasses the code it is rehearsing is not one. Both modes now run the same script, which stops only at the registry call. Verified locally: `REDROB_VERSION=0.4.1` with the dry-run flag packs `redrob-code-sdk-0.4.1.tgz`, restores `package.json` to `0.0.0` afterwards, and the tarball's `dist/v2/gen/types.gen.d.ts` carries the `blocked` session status -- which is the variant the desktop app currently has to declare structurally because no published package contains it.
This was referenced Sep 22, 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
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.
Caught by reading the first dry run's output instead of its green checkmark.
It proved the build and the pack and nothing about the version — the part most likely to be wrong. The workflow invoked
bun pm packdirectly, skippingpublish.tswhere the version injection lives, so it packed the committed0.0.0:A rehearsal that bypasses the code it is rehearsing is not one. Both modes now run the same script, stopping only at the registry call.
Verified locally
That last line is the point of the exercise:
blockedis the session status the desktop app currently has to declare structurally, because no published package contains it.