Skip to content

Version Packages - #887

Open
viam-ci-org-reader[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

Version Packages#887
viam-ci-org-reader[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@viam-ci-org-reader

@viam-ci-org-reader viam-ci-org-reader Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@viamrobotics/motion-tools@1.39.1

Patch Changes

  • 1c61c5c: Add tests for the new Pose class
  • d2c58fe: Use Three.js-like api for pose math

@claude

claude Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Docs check: no guide updates needed. The only changelog entry (d2c58fe / #884, "Use Three.js-like api for pose math") is an internal refactor — it gathers the loose pose utility functions into a Pose class under src/lib/math/ and rewrites internal callers (transform.ts, ECS traits, hooks, plugins). Nothing exported from src/lib/index.ts changed, so no documented prop, hook, or component behavior moved. The pose references in the guides and in the v1→v2 migration page are all Go-side spatialmath.Pose, which this PR does not touch. Verdict: (D) no change.

@viam-ci-org-reader
viam-ci-org-reader Bot force-pushed the changeset-release/main branch from 7d37bc3 to 978a44a Compare July 28, 2026 20:28
@claude

claude Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

No guide changes needed: both entries in this release are internal-only. #884 ("Use Three.js-like api for pose math") consolidates loose pose helpers from $lib/transform into a Pose class in $lib/math — that module is not re-exported from the ., /lib, or /plugins package entrypoints and is not referenced in any use-case guide, and #888 only adds unit tests for it. No documented prop, import path, or behavior in guides/embedding.mdx, guides/local-usage.mdx, guides/worldstatestore.mdx, or migration/v1-to-v2.mdx is affected.

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.

0 participants