chore: bump @openhop/server @openhop/web openhop to 0.3.0#145
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
✅ Files skipped from review due to trivial changes (4)
WalkthroughUpdates release metadata: bumps packages/cli, packages/server, and packages/web from 0.2.0 to 0.3.0 and adds 0.3.0 release notes to CHANGELOG.md (skill trigger routing/gating and INSPECT panel dock defaults), plus changelog link updates. Changes0.3.0 Release Coordination
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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 `@CHANGELOG.md`:
- Around line 10-16: Update the changelog footer link references to include the
new release tag and point Unreleased at v0.3.0; specifically, add a new
reference label `[0.3.0]` that compares the previous tag (e.g.
`v0.2.0...v0.3.0`) and change the `[Unreleased]` comparison target to
`v0.3.0...HEAD` (or the repo’s canonical compare URL format used elsewhere).
Locate and edit the existing reference lines at the bottom of CHANGELOG.md (the
`[Unreleased]` and link refs) so navigation is consistent with the new `##
[0.3.0] - 2026-05-12` section.
🪄 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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 769ddf20-efbc-4bb7-94c0-8a8b4c6f9bdb
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json,!package-lock.json
📒 Files selected for processing (4)
CHANGELOG.mdpackages/cli/package.jsonpackages/server/package.jsonpackages/web/package.json
|
Addressed in -[Unreleased]: https://github.com/naorsabag/OpenHop/compare/v0.2.0...HEAD
+[Unreleased]: https://github.com/naorsabag/OpenHop/compare/v0.3.0...HEAD
+[0.3.0]: https://github.com/naorsabag/OpenHop/releases/tag/v0.3.0
[0.2.0]: https://github.com/naorsabag/OpenHop/releases/tag/v0.2.0
[0.1.0]: https://github.com/naorsabag/OpenHop/releases/tag/v0.1.0 |
Cuts the first release since v0.2.0 on 2026-05-11. The publish workflow auto-publishes each package whose package.json version differs from the registry, then tags v0.3.0 and creates the GitHub release. Versions: - @openhop/server 0.2.0 -> 0.3.0 - @openhop/web 0.2.0 -> 0.3.0 - openhop (CLI) 0.2.0 -> 0.3.0 - CLI's pinned deps on server + web also bumped to 0.3.0. CHANGELOG: promotes the existing [Unreleased] block to [0.3.0] with the two user-visible shipping changes since v0.2.0: - Skill triggers broadened (#143) — diagram / visualization / walkthrough prompts about products, features, workflows, user journeys, etc. now route to OpenHop, not just code walkthroughs. Adds an explicit negative gate to keep generic explainer prompts ("how does TCP work?") from over-activating the skill. - INSPECT panel defaults to bottom-dock on mobile (#142) — narrow viewports keep the canvas full-width when the user opens the inspector. plumbing and not changelogged. #140 / #141 only touched the README and do not ship in any tarball.
7733c09 to
f7c9988
Compare
Summary
Cuts the first release since v0.2.0 (2026-05-11). The publish workflow auto-publishes each package whose
package.jsonversion differs from the registry, then tagsv0.3.0and creates the GitHub release.@openhop/server@openhop/webopenhop(CLI)CLI's pinned deps on
@openhop/server/@openhop/webalso bumped.Why republish
Verified by extracting the current
openhop@0.2.0tarball from npm: it still ships the old narrow skill description ("walk the user through their code..."). The broadened description from #143 is on master but not reachingnpx openhop initusers until we cut a release.What's in this release (user-visible)
Not changelogged
--versionnow reads frompackage.jsonvia prebuild generator. No user-facing behavior.filesfield inpackages/cli/package.jsonis["dist", "skills"]).Test plan
npm run typecheck --workspaces --if-present— all 3 workspaces passnpm run test:cli-contract -w openhop— 37/37 pass against freshly-builtdist/index.js(catches--versiondrift)packages/cli/src/version.tsregenerates to0.3.0via prebuildsync:versionv0.3.0npx openhop initon a fresh machine installs the broadened skill description🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Bug Fixes
Documentation
Chores