Skip to content

chore: bump version to 0.0.67 - #211

Merged
CarmenDou merged 1 commit into
mainfrom
chore/bump-0.0.67
Sep 11, 2026
Merged

chore: bump version to 0.0.67#211
CarmenDou merged 1 commit into
mainfrom
chore/bump-0.0.67

Conversation

@CarmenDou

@CarmenDou CarmenDou commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

What

Bump insta to 0.0.67 so the next tag ships #206 (insta domain) and #210 (MCP token registration failures are reported and exit non-zero).

How

npm version 0.0.67 --no-git-tag-version, which touches only the version fields in package.json and package-lock.json.

Verify

  • Diff is the two version fields and nothing else.
  • After merge: tag v0.0.67 on main. The release workflow publishes the five binaries and the npm package. Check with npm view insta version.

🤖 Generated with Claude Code


Summary by cubic

Bumps insta from 0.0.66 to 0.0.67 so the next release ships the insta domain and MCP token registration failure reporting changes. Only the version fields in package.json and package-lock.json change; no other files are touched.

Written for commit 07381cd. Summary will update on new commits.

Review in cubic

@jwfing jwfing left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - approved.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Re-trigger cubic

@CarmenDou
CarmenDou merged commit 3b1e652 into main Sep 11, 2026
3 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