Conversation
…gistry, but that version doesn't exist
|
|
Claude finished @punkbit's task in 44s —— View job Review
✅ Looks good! Clean, targeted hotfix — nice work! The change is a single line in - run: npm install --global vercel@latest
+ run: npm install --global vercel@41.7.3This correctly pins the Vercel CLI to the last known-good version before 💡 Suggestion (non-blocking)
No concerns with the fix itself — this is the right short-term approach to unblock CI. |
|
Claude finished @punkbit's task in 43s —— View job Review
✅ Looks great! This PR is in good shape. The latest push ( Current state of - name: Install Vercel CLI
# NOTE: Pinned to avoid broken @vercel/hono@0.2.67 dep in newer versions can revisit when Vercel publishes a fix
run: npm install --global vercel@41.7.3Regarding @EvandroLG's comment — the intent is to be on an older version (that's the whole fix), so No blocking issues. Ready to merge. 🙌 |
📚 Storybook Preview Deployed✅ Preview URL: https://click-7et5bu2a1-clickhouse.vercel.app Built from commit: |
Why?
NPM is trying to fetch @vercel/hono@0.2.67.tgz from the npm registry, but that version doesn't exist. The latest published version of @vercel/hono on npm is 0.2.64, published about 16 hours ago. npm Version 0.2.67 was never actually published to the registry, but the latest vercel CLI package declared it as a dependency.
How?
Tickets?
N/A
Contribution checklist?
buildcommand runs locallySecurity checklist?
dangerouslySetInnerHTMLPreview?