chore: bump @openhop/server @openhop/web openhop to 0.2.0#138
Conversation
Cuts the first release since v0.1.0 on 2026-05-11. The publish workflow auto-publishes each package whose package.json version differs from the registry, then tags `v0.2.0` and creates the GitHub release. Versions: - @openhop/server 0.1.0 -> 0.2.0 - @openhop/web 0.1.0 -> 0.2.0 - openhop (CLI) 0.1.0 -> 0.2.0 - CLI's pinned deps on server + web also bumped to 0.2.0. CHANGELOG: promotes the existing [Unreleased] block to [0.2.0] and adds entries for the merged work since v0.1.0 - CLI contract (already noted), skill voice + new examples, sidebar resize, INSPECT dock-aware toggle, edit modal z-index, carrot pacing defaults, and the debug __setMaxZoom hook. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ 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 (5)
✨ 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 |
The CLI's `--version` is rendered from a literal string in src/index.ts (Commander's .version()), not from package.json. Bumping package.json alone leaves the bundled dist out of sync, which the contract test catches: "expected '0.1.0' to be '0.2.0'". Bringing the literal in line with package.json restores CI green. (Reading from package.json at runtime is a separate refactor.) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Summary
Cuts the first npm release since
v0.1.0(2026-05-11 05:35 UTC). 17 commits of merged work have been sitting on master invisible to anyone runningnpx openhop .... This bump fixes that.The publish workflow (
.github/workflows/publish.yml) auto-detectspackage.jsonversion drift against the npm registry on push-to-master, publishes each package whose version changed in dependency order (server → web → cli), and then tagsv0.2.0+ creates the matching GitHub Release. Merging this PR triggers the release. No manualnpm publishneeded.Versions
@openhop/server@openhop/webopenhop(CLI)CLI's pinned deps on
@openhop/serverand@openhop/webalso bumped to0.2.0.package-lock.jsonregenerated.CHANGELOG
[Unreleased]block promoted to[0.2.0]. Added entries grouped Added / Changed / Fixed / Notes for the work since v0.1.0:validate,get,init, JSON output discipline (already in the prior unreleased block — preserved).create-destroy.yaml,sub-flows.yaml,parallel.yaml.__setMaxZoom(n)debug-only browser-console hook (still in; will be stripped in a later release once the default lands cleanly).What the workflow does after merge
packages/{server,web,cli}/package.jsonversion drift.@openhop/server@0.2.0→@openhop/web@0.2.0→openhop@0.2.0(in that order; CLI pins both).v0.2.0against this commit and creates the GitHub Release with auto-generated notes plus the CHANGELOG-style "Published to npm" header.Test plan
🤖 Generated with Claude Code