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

Project	Deployment	Actions	Updated (UTC)
hyperstack-docs	Ready	Preview, Comment	Mar 19, 2026 5:41pm

Greptile Summary

This is an automated release PR generated by Release Please, bumping all workspace packages from 0.5.9 to 0.5.10. The substantive changes driving this release are a bug fix in hyperstack-server (reducing cache size for slot hashes) and a stale lockfile fix in hyperstack-react. All Rust Cargo.toml manifests, the Cargo.lock, TypeScript package.json files, and changelogs have been updated consistently.

Key observations:

• All Rust crate versions and inter-workspace dependency pins are consistently updated to 0.5.10 across Cargo.toml files and Cargo.lock.
• stacks/sdk/typescript/package-lock.json root packages[""] entry has stale peerDependencies ranges (>=0.5.9) that do not reflect the updated package.json values (>=0.5.10). This lockfile was not regenerated after the bump and may cause npm ci --frozen-lockfile to fail.
• typescript/react/package-lock.json similarly has a stale dependency range in the root entry (previously flagged).
• rust/hyperstack-server/CHANGELOG.md contains a duplicate bug fix entry (previously flagged).
• The stacks/sdk/typescript CHANGELOG describes hyperstack-typescript devDependency as having been "bumped from file:../../../typescript/core to 0.5.10", but the package.json still correctly retains the local file: reference for development — the changelog entry is misleading but the actual code is fine.

Confidence Score: 3/5

• Safe to merge for the Rust packages; the stale lockfile peerDependency ranges in stacks/sdk/typescript should be regenerated before publishing that package.
• The version bumps are mechanical and consistent across the Rust ecosystem. The main concern is two npm lockfiles whose root entries are out of sync with their respective package.json files — one was already flagged in a prior review cycle and one is new (stacks/sdk/typescript/package-lock.json). These stale ranges can cause npm ci failures in CI pipelines and potentially resolve the wrong package versions after publish. The duplicate changelog entry in hyperstack-server is cosmetic but warrants investigation into the commit history.
• stacks/sdk/typescript/package-lock.json and typescript/react/package-lock.json need lockfile regeneration to match their updated package.json dependency ranges.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[release-please triggers] --> B[Bump all versions 0.5.9 → 0.5.10]

    B --> C[Rust Workspace]
    B --> D[TypeScript Packages]

    C --> C1[hyperstack-macros Cargo.toml ✅]
    C --> C2[hyperstack-interpreter Cargo.toml ✅]
    C --> C3[hyperstack-server Cargo.toml ✅]
    C --> C4[hyperstack-sdk Cargo.toml ✅]
    C --> C5[hyperstack-stacks Cargo.toml ✅]
    C --> C6[hyperstack + hyperstack-cli Cargo.toml ✅]
    C --> C7[Cargo.lock ✅]

    D --> D1[typescript/core package.json ✅]
    D --> D2[typescript/core package-lock.json ✅]
    D --> D3[typescript/react package.json ✅]
    D --> D4[typescript/react package-lock.json ⚠️ stale dep range]
    D --> D5[stacks/sdk/typescript package.json ✅]
    D --> D6[stacks/sdk/typescript package-lock.json ⚠️ stale peerDep ranges]
    D --> D7[packages/hyperstack package.json ✅]

This is a comment left during a code review.
Path: stacks/sdk/typescript/package-lock.json
Line: 20-21

Comment:
**Stale peerDependencies ranges in lockfile root entry**

The root `packages[""]` entry in `package-lock.json` still records `peerDependencies` as `">=0.5.9"` for both `hyperstack-react` and `hyperstack-typescript`, but `package.json` was updated to `">=0.5.10"` in this same PR. The lockfile root entry is supposed to mirror `package.json` exactly, so they are now out of sync.

This is the same class of problem as the stale lockfile in `typescript/react/package-lock.json` — the lockfile was not regenerated (`npm install`) after bumping the ranges in `package.json`, which means `npm ci --frozen-lockfile` may fail or produce an integrity warning for this package.

```suggestion
      "peerDependencies": {
        "hyperstack-react": ">=0.5.10",
        "hyperstack-typescript": ">=0.5.10"
```

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

_{Last reviewed commit: "chore: release main"}

🤖 Created releases:

• hyperstack-v0.5.10
• hyperstack-interpreter-v0.5.10
• hyperstack-macros-v0.5.10
• hyperstack-cli-v0.5.10
• hyperstack-sdk-v0.5.10
• hyperstack-server-v0.5.10
• hyperstack-react-v0.5.10
• hyperstack-typescript-v0.5.10
• hyperstack-stacks-v0.5.10
• hyperstack-npm-v0.5.10

🌻