chore(main): release brepjs 18.69.0

[brepjs]

🤖 I have created a release beep boop

18.69.0 (2026-06-09)

Features

• implicit: graded + conformal lattices (TPMS + strut) and chamber v1 (Phase 2c) (#1266) (666bfb6)
• implicit: profile-along-spine sweep operator with RMF frames (Phase 2a) (#1260) (10422ff)
• implicit: scalar-field modulation + position-varying operators (Phase 2b) (#1264) (9b59880)

---

This PR was generated with Release Please. See documentation.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
brepjs	Ready	Preview, Comment	Jun 9, 2026 3:03pm

[greptile-apps]

Greptile Summary

Release Please PR bumping the root package from 18.68.0 → 18.69.0 and brepjs-verify from 0.5.0 → 0.5.1, capturing three implicit-geometry features (graded/conformal lattices, profile-along-spine sweep, and scalar-field modulation).

• packages/brepjs-verify/package.json was not updated to 0.5.1 — the manifest and lockfile reflect the bump but the workspace's own package.json still reads 0.5.0, so an npm publish of that package would publish as 0.5.0.
• The package-lock.json entries for brepjs-verify also record "brepjs": "^18.69.0" as a dependency, which disagrees with the "^18.0.0" range declared in the workspace package.json, indicating the lockfile was regenerated against a different tree state.

Confidence Score: 4/5

Merging is risky until packages/brepjs-verify/package.json is updated to 0.5.1 — as-is, publishing the package would emit the wrong version to the registry.

The lockfile and release manifest both record brepjs-verify at 0.5.1, but the workspace package.json for that package was not updated and still reads 0.5.0. Any publish step will use the workspace file as the authoritative version, resulting in either a collision with an existing 0.5.0 tag or a release that does not match the manifest.

packages/brepjs-verify/package.json needs its version field updated to 0.5.1 to match the manifest and lockfile.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Bumps root from 18.68.0 → 18.69.0 and brepjs-verify from 0.5.0 → 0.5.1; brepjs-voxel-wasm left at 0.6.0 in the manifest.
CHANGELOG.md	Standard Release Please changelog entry for 18.69.0 listing three implicit-geometry features.
package.json	Root package version bumped from 18.68.0 → 18.69.0; no other changes.
package-lock.json	Version bumps for root and brepjs-verify look correct, but brepjs-voxel-wasm jumps from 0.3.0 → 0.7.0 while the manifest and workspace package.json agree on 0.6.0; additionally brepjs-verify's workspace package.json was never updated from 0.5.0 to 0.5.1, and its brepjs dependency range in the lockfile (^18.69.0) disagrees with the declared ^18.0.0.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
package-lock.json:12567-12581
**`brepjs-verify` workspace `package.json` not bumped to match manifest and lockfile**

The manifest was updated to `0.5.1` and the lockfile reflects `0.5.1`, but `packages/brepjs-verify/package.json` was never changed from `0.5.0`. When the package is published, npm reads the workspace `package.json` as the authoritative version — it will publish as `0.5.0`, colliding with (or silently shadowing) whatever is already on the registry at that tag and mismatching the release manifest. The lockfile also records `"brepjs": "^18.69.0"` for this workspace entry, which diverges from the `"^18.0.0"` range declared in its own `package.json`, further indicating the lockfile was regenerated against a different state of the tree.

_{Reviews (3): Last reviewed commit: "chore(main): release brepjs 18.69.0" | Re-trigger Greptile}

[greptile-apps]

brepjs-voxel-wasm lockfile version doesn't match any authoritative source

The lockfile changes packages/brepjs-voxel-wasm from 0.3.0 to 0.5.0, but both the .release-please-manifest.json (unchanged at 0.4.0) and packages/brepjs-voxel-wasm/package.json ("version": "0.4.0") agree the package is at 0.4.0. Neither the before (0.3.0) nor the after (0.5.0) entry matches the real workspace version. This suggests the lockfile was regenerated from a different state of the tree. Running npm install after merging will likely produce a different lockfile again, and any tooling that reads the lockfile to resolve the workspace version will see a phantom 0.5.0.

Prompt To Fix With AI

This is a comment left during a code review.
Path: package-lock.json
Line: 12682-12685

Comment:
**brepjs-voxel-wasm lockfile version doesn't match any authoritative source**

The lockfile changes `packages/brepjs-voxel-wasm` from `0.3.0` to `0.5.0`, but both the `.release-please-manifest.json` (unchanged at `0.4.0`) and `packages/brepjs-voxel-wasm/package.json` (`"version": "0.4.0"`) agree the package is at `0.4.0`. Neither the before (`0.3.0`) nor the after (`0.5.0`) entry matches the real workspace version. This suggests the lockfile was regenerated from a different state of the tree. Running `npm install` after merging will likely produce a different lockfile again, and any tooling that reads the lockfile to resolve the workspace version will see a phantom `0.5.0`.

How can I resolve this? If you propose a fix, please make it concise.

[brepjs]

🤖 Created releases:

• brepjs-v18.69.0

🌻