Skip to content

release: bump OctoBus to v0.7.0 - #541

Merged
eetoc merged 1 commit into
mainfrom
release/v0.7.0
Sep 28, 2026
Merged

eetoc merged 1 commit into
mainfrom
release/v0.7.0

Conversation

@eetoc

@eetoc eetoc commented Sep 28, 2026

Copy link
Copy Markdown
Collaborator

Summary

Release metadata for v0.7.0. Bumps @chaitin-ai/octobus and all six platform binary packages from 0.6.0 to 0.7.0, and points the main package's optionalDependencies at the same version.

The publish-octobus job in .github/workflows/ci.yml is triggered by a v<semver> tag push and refuses to publish when the tag version differs from npm/octobus/package.json.version, so the version bump has to land on main before the tag is created.

Follows the same shape as aa76846 ("release: bump OctoBus to v0.6.0"): 7 files, 13 insertions, 13 deletions, version strings only.

Tests run

  • task lint passes: the gofmt check over tracked Go files and go vet ./... are both clean.
  • bash ./scripts/build-octobus-npm-packages.sh --dry-run passes with exit 0. It cross-builds all six platform binaries, checks that the main package version, every platform package version and all six optionalDependencies agree, then runs npm pack --dry-run for each package. All seven packages pack as 0.7.0.

No Go code is touched in this PR, so tests/e2e was not re-run here.

Release notes / impact

  • This PR itself changes version metadata only.
  • v0.7.0 includes Add dry-run mode to service import #539 (dry-run mode for service import: preview the service record and Methods without importing, plus existing_service for replacement-baseline checks) and Serialize imports, recover interrupted commits, and report dry-run restart impact #540 (import robustness: imports sharing a data dir serialize, interrupted commits are recovered on daemon startup, dry runs report the restart blast radius via would_restart_instances, --dry-run --reinstall warns, and the daemon takes the port before its destructive startup steps and releases it when a later step fails).
  • After merge, the release itself is: create an annotated v0.7.0 tag on the merge commit on main and push it. CI then publishes the six platform packages followed by the main package to npm with the latest dist-tag, and the docker workflow pushes docker.io/chaitin/octobus:v0.7.0 plus :latest for linux/amd64 and linux/arm64.

🤖 Generated with Claude Code

Bump the main npm package and all six platform binary packages to
0.7.0, and point the optionalDependencies range at the same version,
so the v0.7.0 tag satisfies the publish job's tag/package version
check.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@monkeyscan

monkeyscan Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

PR Title: release: bump OctoBus to v0.7.0

Commit: bf32306

整体评估

本次改动是一次常规的 npm 包版本发布升级,将主包与六个平台子包的版本号从 0.6.0 统一提升到 0.7.0,并同步更新主包 optionalDependencies 中的依赖版本。改动方向一致、范围清晰,未发现风险。

总结

主包 @chaitin-ai/octobus 的 version、optionalDependencies 中六个平台子包的版本约束,以及各子包自身的 version 三者完全一致,均更新为 0.7.0,没有版本错配或遗漏。本次改动无必须修复的问题,可以合并。

@eetoc
eetoc merged commit 954eb2f into main Sep 28, 2026
2 checks passed
@eetoc
eetoc deleted the release/v0.7.0 branch September 28, 2026 12:40
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