Repository navigation
fix(agent-init): use the project's package manager and pin the version - #180
Merged
Merged
Conversation
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
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.
Two reports from people who tried rc.8:
devEnginesset to pnpm makes npm refusenpx hono, but the block told agents to runnpx honoandnpx skills add. Now the block uses the package manager of the lockfile:pnpm exec honoandpnpm dlx skills addin a pnpm project,npxwith npm,yarn/yarn dlx,bunx.pnpm add -D @hono/cli@nextsilently stays on an older version, because pnpm 11 skips a release younger thanminimumReleaseAge. agent-init now adds the exact version, and pnpm adds an exclude for it.The author should do the following, if applicable
pnpm run check:fixto format and lint the code