Skip to content

chore: release vRealTime 0.2.1 - #76

Merged
austinchennn merged 1 commit into
mainfrom
codex/release-0.2.1
Oct 23, 2026
Merged

austinchennn merged 1 commit into
mainfrom
codex/release-0.2.1

Conversation

@austinchennn

Copy link
Copy Markdown
Collaborator

Description:

Release the current main implementation, including #75 stop-reason continuations, as @vrealtime/*@0.2.1 so downstream applications can install registry packages instead of vendored tarballs.

Fixes:

No linked issue. Requested release for vdoc-server consumption.

Behaviours Completed:

  • Bump all public workspace packages together to 0.2.1.
  • Pin internal and example dependencies to the same release; refresh the lockfile.

Files Changed:

  • Public package and example manifests, and the root lockfile: release version alignment.

Brief Explanation:

Runtime source is the current main containing #75. After merge, the v0.2.1 tag invokes the existing checked npm release workflow.

Testing:

  • Typecheck and all 591 tests across 34 files passed.
  • npm run pack passed for all release packages.
  • git diff --check passed.

Unsure About:

  • Publishing depends on the configured npm release credential and environment; registry availability will be verified after the release workflow.

@austinchennn
austinchennn merged commit 34e1080 into main Oct 23, 2026
6 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.

1 participant