release: sdk 0.4.17, cli 0.4.44, creek 0.4.44 - #41
Merged
Conversation
Ships `creek logs --errors` and the drill-down hint under the error count in `creek metrics` (#40). The server side of that PR is already live; the CLI half only reaches users through npm. Three packages, and the order matters. The CLI does NOT bundle the SDK — its tsdown config externalizes every bare specifier — so the published CLI resolves `isError` from `@solcreek/sdk` at runtime. Publishing cli before sdk would ship a CLI whose `logs` command fails to load. Tag order is therefore sdk@0.4.17 → cli@0.4.44 → creek@0.4.44. creek is bumped alongside cli because it is the umbrella package tenants actually install; leaving it behind would mean `--errors` exists on npm but nobody can get it the normal way. Patch bumps across all three: the SDK change is additive (a new export and an optional filter field), and keeping creek in step with cli matches how those two have tracked each other.
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.
Version bumps only — no code changes. Ships the CLI half of #40 (
creek logs --errors+ the drill-down hint increek metrics); the server half is already live.Why three packages, in this order
The CLI does not bundle the SDK. Its
tsdown.config.tsexternalizes every bare specifier:Verified against the built output —
packages/cli/dist/commands/logs-filter.jsline 1 is stillimport { isError } from "@solcreek/sdk", andpackages/sdk/dist/index.jsis whereisErroractually lives.So publishing
clibeforesdkwould put a CLI on npm whoselogscommand fails to load:isErrordoes not exist in@solcreek/sdk@0.4.16, the currently published version.Tag order:
sdk@0.4.17→cli@0.4.44→creek@0.4.44.creekis bumped alongsideclibecause it is the umbrella package tenants actually install (the reporting tenant is oncreek@0.4.43). Leaving it behind would mean--errorsis on npm but unreachable by the normal install path.Versions
@solcreek/sdk@solcreek/clicreekPatch across all three: the SDK change is additive (one new export, one optional filter field), and
creek/clihave tracked each other.Verification
pnpm turbo build --filter=@solcreek/sdk --filter=@solcreek/clisucceeds.isErrorlinkage checked in both dist outputs (above).pnpm format:checkclean. Full suite green except the pre-existingpackages/cli/src/dev/worker-runner.test.tsfailures that reproduce on a cleanmain.After merge
Tags get pushed in the order above, verifying each package is live on npm before the next. npm versions cannot be unpublished or reused, so the sequence is not restartable — hence the checks above rather than a straight bump-and-tag.