Skip to content

Fix OpenClaw ByteRover plugin version for v3#759

Merged
bao-byterover merged 1 commit into
mainfrom
fix/openclaw-byterover-plugin-1-1-8
Jun 25, 2026
Merged

Fix OpenClaw ByteRover plugin version for v3#759
bao-byterover merged 1 commit into
mainfrom
fix/openclaw-byterover-plugin-1-1-8

Conversation

@cuongdo-byterover

Copy link
Copy Markdown
Collaborator

Summary

  • Pin the OpenClaw ByteRover plugin install to @byterover/byterover@1.1.8 for v3 users.
  • Surface the pinned version in installer logs and failure messages.

Tests

  • bash -n scripts/openclaw-setup.sh
  • Push hook: npm run typecheck

@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Claude finished @cuongdo-byterover's task in 1m 2s —— View job


PR Review: Fix OpenClaw ByteRover plugin version for v3

  • Read the diff and surrounding script context
  • Check for other references to the plugin version
  • Assess correctness, security, and code quality
  • Post review with inline comments and score

Score: 5 / 5 — small, correct, and a genuine improvement.

Summary

This pins the OpenClaw ByteRover plugin install from @byterover/byterover@latest to a fixed 1.1.8 and threads the version through the install command, the progress log, and the failure message. The change is well-scoped and does exactly what the description claims.

What's good

  • praise: Replacing @latest with a pinned version makes installs reproducible and protects v3 users from a future plugin release silently breaking the setup flow.
  • praise: The version is defined once as a constant (BYTEROVER_OPENCLAW_PLUGIN_VERSION) in the dedicated Constants section and reused everywhere — no duplication, single source of truth.
  • The install argument is correctly quoted ("@byterover/byterover@${...}"), so it's safe under set -eu.
  • Surfacing the version in both the info log and the error message improves debuggability when an install fails.

Notes

  • nitpick (non-blocking): The pinned version is now a manual bump point. A one-line comment explaining why it's pinned (v3 compatibility) would help a future maintainer know when it's safe to advance. See the inline suggestion.
  • No security concerns — no new untrusted input, no shell-injection surface, the value is a hardcoded literal.
  • bash -n syntax check could not be run in this environment (command approval), but the diff is a simple constant assignment plus literal-for-literal substitution, and the author confirmed bash -n scripts/openclaw-setup.sh passes.

Nice, clean fix. 👍
fix/openclaw-byterover-plugin-1-1-8

Comment thread scripts/openclaw-setup.sh
@bao-byterover bao-byterover merged commit 1052ac1 into main Jun 25, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants