fix(k8s): float the k8s-client optional-dep range — publish failures stop degrading installs - #1196
Merged
Merged
Conversation
…ersion can't break installs The exact lockstep pin (^0.33.0) meant a failed client publish made npm resolve the optional dep to NOTHING silently: fresh installs lost all live-cluster capability with exit 0 (the 0.33.0 skew). The dynamic-import seam never needed exact coupling — float to >=0.31.0 <1.0.0 and drop the range from the release recipe's lockstep bump, so whatever version is published resolves and a stranded publish is cosmetic.
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.
Root-cause hardening independent of the npm trusted-publisher saga: lexicon-k8s pinned the client at the exact lockstep version, so a stranded client publish (three releases running) silently resolves the optional dep to nothing — fresh installs lose live observation with exit 0. Floats the range to >=0.31.0 <1.0.0 and removes the lockstep bump from the release recipe. The #1188 range-resolution smoke keeps guarding the resolved outcome.
🤖 Generated with Claude Code