Skip to content

chore: bump pi-sidecar to v4.1.2 - #1177

Open
myakove wants to merge 1 commit into
mainfrom
fix/issue-1174-bump-pi-sidecar
Open

chore: bump pi-sidecar to v4.1.2#1177
myakove wants to merge 1 commit into
mainfrom
fix/issue-1174-bump-pi-sidecar

Conversation

@myakove

@myakove myakove commented Jul 29, 2026

Copy link
Copy Markdown
Collaborator

Closes #1174

Changes

  • Bump @myk-org/pi-sidecar ^1.3.1^4.1.2 in sidecar-helper/package.json
  • Bump pi-sidecar-client >=1.1.0>=4.1.2 in pyproject.toml
  • Sync sidecar-helper/package-lock.json and uv.lock
  • Restore libc selectors dropped by npm install

Made with Cursor

Bump @myk-org/pi-sidecar ^1.3.1 → ^4.1.2 (npm) and
pi-sidecar-client >=1.1.0 → >=4.1.2 (PyPI).
Restore libc selectors dropped by npm install.

Co-authored-by: Cursor <cursoragent@cursor.com>
@myakove-bot1

Copy link
Copy Markdown

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

🔄 Automatic Actions

  • Reviewer Assignment: Reviewers are automatically assigned based on the OWNERS file in the repository root
  • Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are automatically applied based on changes
  • Issue Creation: Disabled for this repository
  • Pre-commit Checks: pre-commit runs automatically if .pre-commit-config.yaml exists
  • Branch Labeling: Branch-specific labels are applied to track the target branch
  • Auto-verification: Auto-verified users have their PRs automatically marked as verified
  • Labels: All label categories are enabled (default configuration)

📋 Available Commands

PR Status Management

  • /wip - Mark PR as work in progress (adds WIP: prefix to title)
  • /wip cancel - Remove work in progress status
  • /hold - Block PR merging (PR author or approvers)
  • /hold cancel - Unblock PR merging (PR author or approvers)
  • /verified - Mark PR as verified
  • /verified cancel - Remove verification status
  • /reprocess - Trigger complete PR workflow reprocessing (useful if webhook failed or configuration changed)
  • /regenerate-welcome - Regenerate this welcome message
  • /security-override - Set security check runs to pass (maintainers only)
  • /security-override cancel - Re-run security checks

Review & Approval

  • /lgtm - Approve changes (looks good to me)
  • /approve - Approve PR (approvers only)
  • /automerge - Enable automatic merging when all requirements are met (maintainers and approvers only)
  • /assign-reviewers - Assign reviewers based on OWNERS file
  • /assign-reviewer @username - Assign specific reviewer
  • /check-can-merge - Check if PR meets merge requirements

Testing & Validation

  • /retest tox - Run Python test suite with tox
  • /retest build-container - Rebuild and test container image
  • /retest python-module-install - Test Python package installation
  • /retest pre-commit - Run pre-commit hooks and checks
  • /retest conventional-title - Validate commit message format
  • /retest all - Run all available tests

Container Operations

  • /build-and-push-container - Build and push container image (tagged with PR number)
    • Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

  • /cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
    • Multiple branches: /cherry-pick branch1 branch2 branch3
  • /cherry-pick-retry <branch> - Retry a failed cherry-pick (merged PRs only)

Branch Management

  • /rebase - Rebase this PR branch onto its base branch

Label Management

  • /<label-name> - Add a label to the PR
  • /<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

  1. Approval: /approve from at least one approver
  2. LGTM Count: Minimum 1 /lgtm from reviewers
  3. Status Checks: All required status checks must pass
  4. No Blockers: No wip, hold, has-conflicts labels and PR must be mergeable (no conflicts)
  5. Verified: PR must be marked as verified

📊 Review Process

Approvers and Reviewers

Approvers:

  • myakove
  • rnetser

Reviewers:

  • myakove
  • rnetser
Available Labels
  • hold
  • verified
  • wip
  • lgtm
  • approve
  • automerge
AI Features
  • Conventional Title: Mode: fix (claude/claude-opus-4-6-1m)
  • Cherry-Pick Conflict Resolution: Enabled (claude/claude-opus-4-6-1m)
  • Test Oracle: Triggers: approved (claude/claude-opus-4-6[1m]); /test-oracle can be used anytime
Security Checks
  • Suspicious Path Detection: Monitors paths: .claude/, .vscode/, .cursor/, .devcontainer/, .pi/, .github/workflows/, .github/actions/
  • Committer Identity Check: Verifies last committer matches PR author
  • Mandatory: Security checks block merge (use /security-override to bypass — maintainers only)

💡 Tips

  • WIP Status: Use /wip when your PR is not ready for review
  • Verification: The verified label is removed on new commits unless the push is detected as a clean rebase
  • Cherry-picking: Cherry-pick labels are processed when the PR is merged
  • Container Builds: Container images are automatically tagged with the PR number
  • Permission Levels: Some commands require approver permissions
  • Auto-verified Users: Certain users have automatic verification and merge privileges

For more information, please refer to the project documentation or contact the maintainers.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Bump pi-sidecar to v4.1.2 (npm + PyPI)

⚙️ Configuration changes 🕐 20-40 Minutes

Grey Divider

AI Description

• Upgrade pi-sidecar dependencies to v4.1.2 across Node and Python consumers.
• Regenerate npm/uv lockfiles to reflect the new dependency graph.
• Re-add libc selectors in package-lock to preserve platform-specific installs.
Diagram

graph TD
  R["Repo"] --> PY["Python service"] --> PYP["pi-sidecar-client >=4.1.2"] --> PYPI{{"PyPI"}}
  R --> NH["sidecar-helper (Node)"] --> NPMD["@myk-org/pi-sidecar ^4.1.2"] --> NPM{{"npm registry"}}
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Pin exact versions for this major bump
  • ➕ Avoids unintentionally pulling newer 4.x releases with breaking behavior changes
  • ➕ Makes incidents easier to bisect to a known sidecar version
  • ➖ Requires manual bumps for patch/minor releases
  • ➖ May conflict with existing dependency policy that prefers ranges
2. Add explicit runtime/CI guardrails for Node engine/platform constraints
  • ➕ Catches Node version mismatches early if pi-sidecar now requires a newer Node engine
  • ➕ Prevents regressions on alpine/musl vs glibc images where libc selectors matter
  • ➖ Requires CI/config changes outside the scope of a simple bump
  • ➖ May need coordinated updates across build/deploy pipelines

Recommendation: Proceed with the bump as proposed, but verify the repo’s Node runtime meets the new pi-sidecar engine requirement and run a minimal smoke test in both glibc and musl environments (the PR explicitly restores libc selectors, so platform behavior is part of the risk surface). If stability is a priority, consider temporarily pinning to 4.1.2 for the first rollout.

Files changed (4) +172 / -1622

Other (4) +172 / -1622
pyproject.tomlBump Python pi-sidecar-client requirement to >=4.1.2 +1/-1

Bump Python pi-sidecar-client requirement to >=4.1.2

• Updates the Python dependency constraint for pi-sidecar-client from >=1.1.0 to >=4.1.2 to align with the sidecar v4 series.

pyproject.toml

package.jsonBump @myk-org/pi-sidecar to ^4.1.2 +1/-1

Bump @myk-org/pi-sidecar to ^4.1.2

• Updates the Node sidecar-helper’s direct dependency on @myk-org/pi-sidecar from ^1.3.1 to ^4.1.2.

sidecar-helper/package.json

package-lock.jsonRegenerate npm lockfile for pi-sidecar v4.1.2 and platform metadata +164/-1617

Regenerate npm lockfile for pi-sidecar v4.1.2 and platform metadata

• Synchronizes package-lock.json to reflect @myk-org/pi-sidecar v4.1.2 and resulting transitive dependency changes. Restores libc selectors (glibc/musl) for platform-specific optional packages that were dropped during install churn.

sidecar-helper/package-lock.json

uv.lockUpdate uv lockfile to pi-sidecar-client 4.1.2 +6/-3

Update uv lockfile to pi-sidecar-client 4.1.2

• Updates uv.lock to lock pi-sidecar-client at 4.1.2 and adjusts the locked source artifacts (sdist/wheel URLs and hashes) accordingly.

uv.lock

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used
✅ Compliance rules (platform): 13 rules

Grey Divider


Remediation recommended

1. Docs mismatch sidecar deps 🐞 Bug ☼ Reliability
Description
The updated lockfile installs @myk-org/pi-sidecar@4.1.2 without any pi-vertex-claude-named
dependency in its declared dependency list, while the repo docs still state VERTEX_CLAUDE_1M is
“Read by Pi SDK sidecar” for Vertex Claude support. Users following the docs may enable Vertex
Claude configuration even though the shipped sidecar dependency set no longer obviously includes a
Vertex-Claude provider module.
Code

sidecar-helper/package-lock.json[R2840-2846]

+      "dependencies": {
+        "@earendil-works/pi-ai": "^0.81.1",
+        "@earendil-works/pi-coding-agent": "^0.81.1",
+        "acpx": "^0.8.0",
+        "jiti": "^2.7.0",
+        "protobufjs": "7.6.5"
+      },
Relevance

●●● Strong

Team previously accepted updating docs to match config/behavior (Renovate docs PR#1140; prompt/tool
alignment PR#1127).

PR-#1140
PR-#1127

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The pi-sidecar 4.1.2 entry in the current lockfile lists its dependencies and does not include any
pi-vertex-claude-named package, while repo documentation explicitly instructs users to set
VERTEX_CLAUDE_1M=true and states it is read by the sidecar for Vertex Claude support.

sidecar-helper/package-lock.json[2834-2853]
docs/environment-variables.md[203-220]
docs/enabling-ai-features.md[37-43]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
After upgrading `@myk-org/pi-sidecar` to `4.1.2`, the lockfile’s declared dependency set for the sidecar no longer clearly includes a Vertex Claude provider module (previously implied by a `pi-vertex-claude` dependency name), but documentation still advertises `VERTEX_CLAUDE_1M` as a supported sidecar feature.

### Issue Context
This is a major-version upgrade of the sidecar; the container’s shipped Node dependency tree is the product surface for AI-provider support. Documentation and examples should match what is actually included in `sidecar-helper`’s dependency graph.

### Fix Focus Areas
- sidecar-helper/package-lock.json[2834-2853]
- sidecar-helper/package.json[9-20]
- docs/environment-variables.md[203-220]
- docs/enabling-ai-features.md[37-43]

### What to change
Choose one of the following and make it explicit:
1. **If Vertex Claude is still supported in pi-sidecar v4**: update docs to reference the new mechanism/package name used by v4 (and remove any outdated implication that `VERTEX_CLAUDE_1M` is supported if it isn’t).
2. **If Vertex Claude is not supported anymore by default**: update docs/examples to remove `VERTEX_CLAUDE_1M` guidance (or mark it as unsupported/deprecated).
3. **If Vertex Claude support requires an additional package now**: add the required dependency explicitly in `sidecar-helper/package.json` and regenerate `package-lock.json` so the provider module is present in the shipped image.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

To customize comments, go to the Qodo configuration screen, or learn more in the docs.

Qodo Logo

Comment on lines +2840 to +2846
"dependencies": {
"@earendil-works/pi-ai": "^0.81.1",
"@earendil-works/pi-coding-agent": "^0.81.1",
"acpx": "^0.8.0",
"jiti": "^2.7.0",
"protobufjs": "7.6.5"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

1. Docs mismatch sidecar deps 🐞 Bug ☼ Reliability

The updated lockfile installs @myk-org/pi-sidecar@4.1.2 without any pi-vertex-claude-named
dependency in its declared dependency list, while the repo docs still state VERTEX_CLAUDE_1M is
“Read by Pi SDK sidecar” for Vertex Claude support. Users following the docs may enable Vertex
Claude configuration even though the shipped sidecar dependency set no longer obviously includes a
Vertex-Claude provider module.
Agent Prompt
### Issue description
After upgrading `@myk-org/pi-sidecar` to `4.1.2`, the lockfile’s declared dependency set for the sidecar no longer clearly includes a Vertex Claude provider module (previously implied by a `pi-vertex-claude` dependency name), but documentation still advertises `VERTEX_CLAUDE_1M` as a supported sidecar feature.

### Issue Context
This is a major-version upgrade of the sidecar; the container’s shipped Node dependency tree is the product surface for AI-provider support. Documentation and examples should match what is actually included in `sidecar-helper`’s dependency graph.

### Fix Focus Areas
- sidecar-helper/package-lock.json[2834-2853]
- sidecar-helper/package.json[9-20]
- docs/environment-variables.md[203-220]
- docs/enabling-ai-features.md[37-43]

### What to change
Choose one of the following and make it explicit:
1. **If Vertex Claude is still supported in pi-sidecar v4**: update docs to reference the new mechanism/package name used by v4 (and remove any outdated implication that `VERTEX_CLAUDE_1M` is supported if it isn’t).
2. **If Vertex Claude is not supported anymore by default**: update docs/examples to remove `VERTEX_CLAUDE_1M` guidance (or mark it as unsupported/deprecated).
3. **If Vertex Claude support requires an additional package now**: add the required dependency explicitly in `sidecar-helper/package.json` and regenerate `package-lock.json` so the provider module is present in the shipped image.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore: update @myk-org/pi-sidecar to v4.1.2 (from pi-config monorepo)

2 participants