chore(piece): pin @thinkfleet/agentmark to ^0.11.0 for publishing - #10
Merged
Conversation
The monorepo-dev `file:../..` link was correct during PR review (kept the piece pinned to the in-tree version), but npm won't accept a file: dep on publish — it requires a real version range pointing at the registry. Now that `@thinkfleet/agentmark@0.11.0` is on its way to npm, the piece can ship pointing at the published version. Co-Authored-By: Claude Opus 4.7 (1M context) <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
2 participants
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.
Tiny prep PR. The piece's `package.json` referenced `@thinkfleet/agentmark` as `file:../..` for monorepo development — npm rejects `file:` deps on publish. Swap to `^0.11.0` so we can publish `@thinkfleet/piece-agentmark@0.1.0`.
Order of operations:
Both packages will be live on npm.
🤖 Generated with Claude Code