fix(examples): link cli-empresa-inc to @figtools/cli via workspace:* - #54
Merged
Conversation
examples/cli-empresa-inc depended on @figtools/cli with a real semver range (^0.4.0), so when changesets bumped it to track the not-yet-published next version, `pnpm install --frozen-lockfile` in the Publish Packages workflow tried to resolve it against npm and failed — the version didn't exist yet because publishing it is what the same job was trying to do. Switching to workspace:* (the same pattern packages/cli already uses for @figtools/core) resolves it locally instead, so version bumps here no longer race against npm publish. Co-Authored-By: Claude Sonnet 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.
Summary
pnpm install --frozen-lockfilefailed becauseexamples/cli-empresa-inc/package.jsondepends on@figtools/cliwith a real semver range (^0.4.0), which changesets bumped when versioning@figtools/cli— but0.4.0didn't exist on npm yet, since publishing it is what that same workflow run was trying to do.workspace:*(matching the patternpackages/clialready uses for@figtools/core), so it resolves locally via a workspace link instead of racing against npm. Regeneratedpnpm-lock.yamlto match.pnpm install --frozen-lockfile --ignore-scripts) after a cleannode_moduleswipe — passes now. Also ranpnpm buildandpnpm test, both green.Test plan
pnpm install --frozen-lockfile --ignore-scripts(same command the failing job runs) — passespnpm build— passespnpm test— 128/128 passing🤖 Generated with Claude Code