chore: release main

[github-actions]

🤖 I have created a release beep boop

hyperstack: 0.5.11

0.5.11 (2026-03-21)

Miscellaneous Chores

• hyperstack: Synchronize hyperstack versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • hyperstack-interpreter bumped from 0.5.10 to 0.5.11
    • hyperstack-macros bumped from 0.5.10 to 0.5.11
    • hyperstack-server bumped from 0.5.10 to 0.5.11
    • hyperstack-sdk bumped from 0.5.10 to 0.5.11

hyperstack-cli: 0.5.11

0.5.11 (2026-03-21)

Features

• Add AST versioning system with automatic migration support (997706b)
• Add AST versioning system with automatic migration support (b62d08d)

Bug Fixes

• Address code review feedback on error messages and examples (262be58)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • hyperstack-interpreter bumped from 0.5.10 to 0.5.11

hyperstack-interpreter: 0.5.11

0.5.11 (2026-03-21)

Features

• Add AST versioning system with automatic migration support (997706b)
• Add AST versioning system with automatic migration support (b62d08d)

Bug Fixes

• Address code review feedback on AST versioning (1791986)
• Address code review feedback on into_latest, test assertions, and parsing (da49bf9)
• Clarify UnsupportedVersion error message to mention migration support (51fde69)
• Make sync tests fail explicitly when source file not found (c824e3d)
• Remove Serialize derive from Versioned*Spec enums to prevent duplicate keys (73ad7b4)
• Use CURRENT_AST_VERSION constant instead of hardcoded version (5df9efe)
• Use CURRENT_AST_VERSION in test assertions instead of hardcoded string (6809f1a)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • hyperstack-macros bumped from 0.5.10 to 0.5.11

hyperstack-macros: 0.5.11

0.5.11 (2026-03-21)

Features

• Add AST versioning system with automatic migration support (997706b)
• Add AST versioning system with automatic migration support (b62d08d)

Bug Fixes

• Address clippy warnings in AST versioning module (1d6540f)
• Address code review feedback on AST versioning (1791986)
• Address code review feedback on into_latest, test assertions, and parsing (da49bf9)
• Clarify UnsupportedVersion error message to mention migration support (51fde69)
• Make sync tests fail explicitly when source file not found (c824e3d)
• Remove Serialize derive from Versioned*Spec enums to prevent duplicate keys (73ad7b4)
• Use CURRENT_AST_VERSION constant instead of hardcoded version (5df9efe)
• Use CURRENT_AST_VERSION in test assertions instead of hardcoded string (6809f1a)

hyperstack-sdk: 0.5.11

0.5.11 (2026-03-21)

Features

• Make snapshots optional with cursor-based filtering (HYP-148) (46be9aa)
• rust-sdk: Support optional snapshots and cursor-based resume (9c5fcc0)
• sdk: Add builder methods and React hooks for new subscription options (1f7f95b)

Bug Fixes

• add camelCase serde rename to Subscription struct (522d7ae)
• rust-sdk: Wire up new subscription fields through stream layer (8f4fba0)

hyperstack-server: 0.5.11

0.5.11 (2026-03-21)

Features

• Make snapshots optional with cursor-based filtering (HYP-148) (46be9aa)
• server: Add optional snapshot and cursor-based filtering to WebSocket protocol (da7b486)

Bug Fixes

• add camelCase serde rename to Subscription struct (fc68ea5)
• add truncate after sorting by _seq to respect snapshot_limit (0782e66)
• apply snapshot_limit after key filter in websocket subscriptions (12f8f75)
• apply snapshot_limit when no after cursor is provided (b3850e6)
• correct snapshot ordering when using cursor with limit (6f4a4d3)
• Fix _seq numeric comparison and missing borrow_and_update in cache and WebSocket handlers (7b2c06c)
• make snapshot_limit deterministic by sorting before truncation (1d62917)
• sort entities by _seq before applying snapshot_limit (6abba2a)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • hyperstack-interpreter bumped from 0.5.10 to 0.5.11

hyperstack-stacks: 0.5.11

0.5.11 (2026-03-21)

Miscellaneous Chores

• hyperstack-stacks: Synchronize hyperstack versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • hyperstack-sdk bumped from 0.5.10 to 0.5.11

hyperstack-npm: 0.5.11

0.5.11 (2026-03-21)

Miscellaneous Chores

• hyperstack-npm: Synchronize hyperstack versions

hyperstack-react: 0.5.11

0.5.11 (2026-03-21)

Features

• Make snapshots optional with cursor-based filtering (HYP-148) (46be9aa)
• sdk: Add builder methods and React hooks for new subscription options (1f7f95b)
• typescript-sdk: Support optional snapshots and cursor-based resume (3f239e9)

Bug Fixes

• guard refresh() isLoading behind withSnapshot check (18ec45d)
• guard setIsLoading(true) when withSnapshot is false (3808e59)
• prevent isLoading stuck when withSnapshot is false in view hooks (b8a3692)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • hyperstack-typescript bumped from ^0.5.10 to ^0.5.11

hyperstack-stacks: 0.5.11

0.5.11 (2026-03-21)

Miscellaneous Chores

• hyperstack-stacks: Synchronize hyperstack versions

Dependencies

• The following workspace dependencies were updated
  • devDependencies
    • hyperstack-typescript bumped from file:../../../typescript/core to 0.5.11
  • peerDependencies
    • hyperstack-react bumped from >=0.5.10 to >=0.5.11
    • hyperstack-typescript bumped from >=0.5.10 to >=0.5.11

hyperstack-typescript: 0.5.11

0.5.11 (2026-03-21)

Features

• Make snapshots optional with cursor-based filtering (HYP-148) (46be9aa)
• typescript-sdk: Support optional snapshots and cursor-based resume (3f239e9)

---

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)
hyperstack-docs	Ready	Preview, Comment	Mar 21, 2026 5:58pm

[greptile-apps]

Greptile Summary

This is an automated release PR generated by Release Please, bumping all workspace packages from 0.5.10 to 0.5.11. The underlying feature work includes an AST versioning system with automatic migration support, optional snapshot/cursor-based filtering for WebSocket subscriptions, and several related bug fixes across the Rust and TypeScript SDKs.

• All Rust crate versions (hyperstack, hyperstack-interpreter, hyperstack-macros, hyperstack-cli, hyperstack-sdk, hyperstack-server, hyperstack-stacks) correctly bumped to 0.5.11 with consistent intra-workspace dependency version pins
• All TypeScript package versions (hyperstack-typescript, hyperstack-react, hyperstack-stacks, packages/hyperstack) correctly bumped to 0.5.11
• Cargo.lock is consistent with the updated Cargo.toml files
• typescript/react/package-lock.json is out of sync: packages[""].dependencies.hyperstack-typescript still shows "^0.5.9" while package.json now specifies "^0.5.11" — this will cause npm ci to fail
• stacks/sdk/typescript/package-lock.json is out of sync: packages[""].peerDependencies for hyperstack-react and hyperstack-typescript still show ">=0.5.9" while package.json was updated to ">=0.5.11"

Confidence Score: 3/5

• PR is mostly safe but two npm lockfiles are out of sync with their package.json, which will cause npm ci failures in CI/CD for the TypeScript packages.
• The Rust side of the release is fully consistent and safe. The TypeScript package.json files are correct. However, two package-lock.json files were not regenerated after version bumps — the root packages[""] entries still reference old version ranges that don't match the updated package.json. This will cause npm ci to fail for hyperstack-react and hyperstack-stacks (TypeScript) until the lockfiles are regenerated with npm install.
• typescript/react/package-lock.json and stacks/sdk/typescript/package-lock.json require attention due to stale version ranges in the lockfile root package entries.

Important Files Changed

Filename	Overview
.release-please-manifest.json	All tracked packages bumped from 0.5.10 to 0.5.11; hyperstack-idl remains at 0.1.5 as expected.
Cargo.lock	All Rust workspace crates updated from 0.5.10 to 0.5.11 in the lockfile; consistent with Cargo.toml changes.
typescript/react/package-lock.json	Lockfile packages[""].dependencies.hyperstack-typescript still shows "^0.5.9" while package.json specifies "^0.5.11" — lockfile was not regenerated after the version bump, which will cause npm ci failures.
stacks/sdk/typescript/package-lock.json	Lockfile packages[""].peerDependencies still shows ">=0.5.9" for hyperstack-react and hyperstack-typescript while package.json was updated to ">=0.5.11" — lockfile not regenerated.
typescript/react/package.json	Version bumped to 0.5.11 and hyperstack-typescript dependency correctly updated to ^0.5.11.
stacks/sdk/typescript/package.json	Version bumped to 0.5.11 and peerDependencies for hyperstack-react and hyperstack-typescript correctly updated to >=0.5.11.
typescript/core/package.json	Version bumped to 0.5.11; no dependency changes needed for this leaf package.
rust/hyperstack-server/Cargo.toml	Version bumped to 0.5.11 and hyperstack-interpreter dependency updated to 0.5.11.
interpreter/Cargo.toml	Version bumped to 0.5.11 and hyperstack-macros dependency updated to 0.5.11.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] --> B[Bump all packages 0.5.10 → 0.5.11]

    B --> C[Rust Crates]
    B --> D[TypeScript Packages]
    B --> E[Manifest & Lockfiles]

    C --> C1[hyperstack-macros]
    C --> C2[hyperstack-interpreter\ndeps: macros ^0.5.11]
    C --> C3[hyperstack-sdk]
    C --> C4[hyperstack-server\ndeps: interpreter ^0.5.11]
    C --> C5[hyperstack-cli\ndeps: interpreter ^0.5.11]
    C --> C6[hyperstack\ndeps: all ^0.5.11]
    C --> C7[hyperstack-stacks\ndeps: sdk ^0.5.11]

    D --> D1[hyperstack-typescript\ncore]
    D --> D2[hyperstack-react\ndeps: typescript ^0.5.11]
    D --> D3[hyperstack-stacks TS\npeerDeps: >=0.5.11]
    D --> D4[packages/hyperstack\nnpm CLI wrapper]

    E --> E1[.release-please-manifest.json ✅]
    E --> E2[Cargo.lock ✅]
    E --> E3[typescript/react/package-lock.json\n⚠️ deps still show ^0.5.9]
    E --> E4[stacks/sdk/typescript/package-lock.json\n⚠️ peerDeps still show >=0.5.9]

Loading

Comments Outside Diff (2)

1. typescript/react/package-lock.json, line 12 (link)

   Lockfile out of sync with package.json

   The packages[""].dependencies.hyperstack-typescript field in the lockfile is "^0.5.9", but package.json was updated to "^0.5.11". When npm ci is run (e.g. in CI/CD), it validates that the packages[""] section in the lockfile exactly matches package.json, and this mismatch will cause the command to fail with a sync error.

   The lockfile should have been regenerated with npm install after bumping the version in package.json. The packages[""].dependencies entry needs to be updated to match:

2. stacks/sdk/typescript/package-lock.json, line 20-22 (link)

   Lockfile peerDependencies out of sync with package.json

   The packages[""].peerDependencies in the lockfile still shows ">=0.5.9" for both hyperstack-react and hyperstack-typescript, but package.json was updated to ">=0.5.11". This means the lockfile was not regenerated after the version bump. Running npm ci in environments that validate lockfile consistency may fail.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: typescript/react/package-lock.json
Line: 12

Comment:
**Lockfile out of sync with package.json**

The `packages[""].dependencies.hyperstack-typescript` field in the lockfile is `"^0.5.9"`, but `package.json` was updated to `"^0.5.11"`. When `npm ci` is run (e.g. in CI/CD), it validates that the `packages[""]` section in the lockfile exactly matches `package.json`, and this mismatch will cause the command to fail with a sync error.

The lockfile should have been regenerated with `npm install` after bumping the version in `package.json`. The `packages[""].dependencies` entry needs to be updated to match:

```suggestion
        "hyperstack-typescript": "^0.5.11",
```

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

---

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

Comment:
**Lockfile peerDependencies out of sync with package.json**

The `packages[""].peerDependencies` in the lockfile still shows `">=0.5.9"` for both `hyperstack-react` and `hyperstack-typescript`, but `package.json` was updated to `">=0.5.11"`. This means the lockfile was not regenerated after the version bump. Running `npm ci` in environments that validate lockfile consistency may fail.

```suggestion
        "hyperstack-react": ">=0.5.11",
        "hyperstack-typescript": ">=0.5.11"
```

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

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