Skip to content

chore: bump @openhop/server @openhop/web openhop to 0.2.0#138

Merged
naorsabag merged 2 commits into
masterfrom
chore/bump-0.2.0
May 11, 2026
Merged

chore: bump @openhop/server @openhop/web openhop to 0.2.0#138
naorsabag merged 2 commits into
masterfrom
chore/bump-0.2.0

Conversation

@naorsabag
Copy link
Copy Markdown
Owner

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 running npx openhop .... This bump fixes that.

The publish workflow (.github/workflows/publish.yml) auto-detects package.json version drift against the npm registry on push-to-master, publishes each package whose version changed in dependency order (server → web → cli), and then tags v0.2.0 + creates the matching GitHub Release. Merging this PR triggers the release. No manual npm publish needed.

Versions

Package Old New
@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 @openhop/server and @openhop/web also bumped to 0.2.0. package-lock.json regenerated.

CHANGELOG

[Unreleased] block promoted to [0.2.0]. Added entries grouped Added / Changed / Fixed / Notes for the work since v0.1.0:

  • CLI: machine-first contract, validate, get, init, JSON output discipline (already in the prior unreleased block — preserved).
  • Skill: explicit create/destroy semantics, new Voice section, prompt → YAML table additions.
  • New examples bundled into the CLI tarball: create-destroy.yaml, sub-flows.yaml, parallel.yaml.
  • Web: sidebar resize + tooltips + single-slash root, INSPECT dock-aware toggle, edit modal z-index above carrots, carrot dwell tuned (gap 700 → 1100 ms, auto-zoom 1.0 default).
  • Web: __setMaxZoom(n) debug-only browser-console hook (still in; will be stripped in a later release once the default lands cleanly).
  • Existing example YAMLs migrated to verbose plain-English voice.

What the workflow does after merge

  1. Detects packages/{server,web,cli}/package.json version drift.
  2. Publishes @openhop/server@0.2.0@openhop/web@0.2.0openhop@0.2.0 (in that order; CLI pins both).
  3. Skips any package whose target version already exists on the registry (none in this case).
  4. Tags v0.2.0 against this commit and creates the GitHub Release with auto-generated notes plus the CHANGELOG-style "Published to npm" header.

Test plan

  • CI green on this PR (build, test, audit, gitleaks, codeql).
  • After merge: `gh run watch ` — server/web/cli all publish successfully.
  • After publish: `npm view openhop version` → `0.2.0`.
  • After publish: `npx openhop@latest demo` in a fresh shell on a clean machine works end-to-end.
  • GitHub Release `v0.2.0` appears with the CHANGELOG body.

🤖 Generated with Claude Code

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>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 11, 2026

Warning

Rate limit exceeded

@naorsabag has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 10 minutes and 49 seconds before requesting another review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e783a245-1bf6-4214-b12f-39a664245c41

📥 Commits

Reviewing files that changed from the base of the PR and between 2fc2148 and c429ce0.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json, !package-lock.json
📒 Files selected for processing (5)
  • CHANGELOG.md
  • packages/cli/package.json
  • packages/cli/src/index.ts
  • packages/server/package.json
  • packages/web/package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-0.2.0

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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>
@naorsabag naorsabag merged commit c006a94 into master May 11, 2026
8 checks passed
@naorsabag naorsabag deleted the chore/bump-0.2.0 branch May 15, 2026 16:00
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.

1 participant