Skip to content

Release 0.1.6 - #52

Closed
jamesyong-42 wants to merge 1 commit into
mainfrom
release/0.1.6
Closed

jamesyong-42 wants to merge 1 commit into
mainfrom
release/0.1.6

Conversation

@jamesyong-42

@jamesyong-42 jamesyong-42 commented Nov 12, 2026 •

Copy link
Copy Markdown
Member

The problem and the resulting behavior

Version 0.1.6 on every plane: the workspace version in Cargo.toml, @vibefield/rosetta-protocol and
@vibefield/rosetta-room, and the app's two dependency ranges, with the lock entries that record them (the 22
workspace crates in Cargo.lock, five lines of package-lock.json). Six files, the same six and the same line
counts as the 0.1.5 release.

0.1.6 carries the Swift client's stored-member reads (#50) and the MIT license (#51). The wire protocol version is
unchanged.

Validation

  • The lock files were edited as text, not regenerated by cargo or npm. Only version strings of this
    repository's own packages moved. CI is the proof: the Rust jobs build with --locked, and the npm job runs
    npm ci and packs both tarballs.
  • After the merge, tag the merged commit v0.1.6 and npm-v0.1.6.

🤖 Generated with Claude Code


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

The workspace version, the two npm packages and the app's two dependency
ranges move from 0.1.5 to 0.1.6, with the lock entries that record them:
the 22 workspace crates in Cargo.lock and five lines of package-lock.json.

0.1.6 carries the Swift client's stored-member reads and the MIT license.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@jamesyong-42 jamesyong-42 mentioned this pull request Nov 12, 2026
@jamesyong-42

Copy link
Copy Markdown
Member Author

Superseded by the re-cut after #48.

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