chore(release): v2026.5.6.7 — installer pnpm activation + dashboard @noble fix#433
Open
webdevtodayjason wants to merge 1 commit into
Open
chore(release): v2026.5.6.7 — installer pnpm activation + dashboard @noble fix#433webdevtodayjason wants to merge 1 commit into
webdevtodayjason wants to merge 1 commit into
Conversation
…dashboard @noble build Two fixes for the public `curl | bash` install, both surfaced on a clean Mac that has no compatible system Node (so the installer provisions its private Node runtime): - activate_pinned_pnpm invoked corepack/npm (`#!/usr/bin/env node` scripts) without that Node on PATH, so they died with "env: node: No such file or directory"; the pinned pnpm@10.23.0 was never cached and the install fell back to a mismatched global pnpm and aborted. Put node on PATH, set COREPACK_ENABLE_DOWNLOAD_PROMPT=0 (no TTY under curl|bash), and surface the corepack error instead of swallowing it. - dashboard `vite build` imports shared ui/ source that needs @noble/ed25519, which the installer's --ignore-workspace install never provided. Declare it at the repo root so it resolves for the dashboard bundle. (lockfile fast-path falls back to a non-frozen install until a clean workspace regen lands.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
📝 WalkthroughWalkthroughThis is a fantastic patch release. Version 2026.5.6.7 fixes two critical installer problems: ensuring the private Node runtime is on PATH so corepack and npm work correctly with pinned pnpm, and declaring the ChangesInstaller and Dashboard Bug Fixes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 172: package.json was updated to add the new dependency specifier
"`@noble/ed25519`": "3.0.0" but pnpm-lock.yaml was not regenerated, causing CI
failures; run pnpm install --lockfile-only to update pnpm-lock.yaml (so the
lockfile matches package.json), stage the updated pnpm-lock.yaml, and commit the
change so CI with --frozen-lockfile will succeed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: deffc6b2-b1b4-4e1d-92d4-6ca7be4772f2
📒 Files selected for processing (3)
CHANGELOG.mdpackage.jsonscripts/install-hosted.sh
| "@lydell/node-pty": "1.2.0-beta.3", | ||
| "@modelcontextprotocol/sdk": "^1.25.2", | ||
| "@mozilla/readability": "^0.6.0", | ||
| "@noble/ed25519": "3.0.0", |
There was a problem hiding this comment.
Lockfile mismatch is a hard blocker — CI is red, very red.
Line 172 adds a new specifier, but pnpm-lock.yaml was not updated, so all pnpm install --frozen-lockfile jobs fail.
Suggested fix
pnpm install --lockfile-only
git add pnpm-lock.yaml🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 172, package.json was updated to add the new dependency
specifier "`@noble/ed25519`": "3.0.0" but pnpm-lock.yaml was not regenerated,
causing CI failures; run pnpm install --lockfile-only to update pnpm-lock.yaml
(so the lockfile matches package.json), stage the updated pnpm-lock.yaml, and
commit the change so CI with --frozen-lockfile will succeed.
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.
Cherry-pick of the v2026.5.6.7 hotfix (commit b5c8291, tagged + released) onto main.
Already live: tag v2026.5.6.7, GitHub release (Latest), and argentos.ai/install.sh. This brings main in line.
🤖 Generated with Claude Code
Summary by CodeRabbit
Bug Fixes
Chores