Skip to content

chore: release main#67

Merged
adiman9 merged 1 commit intomainfrom
release-please--branches--main
Mar 19, 2026
Merged

chore: release main#67
adiman9 merged 1 commit intomainfrom
release-please--branches--main

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Mar 19, 2026

🤖 I have created a release beep boop

hyperstack: 0.5.9

0.5.9 (2026-03-19)

Miscellaneous Chores

  • hyperstack: Synchronize hyperstack versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-interpreter bumped from 0.5.8 to 0.5.9
      • hyperstack-macros bumped from 0.5.8 to 0.5.9
      • hyperstack-server bumped from 0.5.8 to 0.5.9
      • hyperstack-sdk bumped from 0.5.6 to 0.5.9
hyperstack-cli: 0.5.9

0.5.9 (2026-03-19)

Miscellaneous Chores

  • hyperstack-cli: Synchronize hyperstack versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-interpreter bumped from 0.5.8 to 0.5.9
hyperstack-interpreter: 0.5.9

0.5.9 (2026-03-19)

Bug Fixes

  • generate correct deserializers for i32/u32 fields (86438e2)
  • handle u64 integer precision loss across Rust-JS boundary (e96e7fa)
  • handle u64 integer precision loss across Rust-JS boundary (c3a3c69)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-macros bumped from 0.5.8 to 0.5.9
hyperstack-macros: 0.5.9

0.5.9 (2026-03-19)

Bug Fixes

  • handle u64 integer precision loss across Rust-JS boundary (e96e7fa)
hyperstack-sdk: 0.5.9

0.5.9 (2026-03-19)

Bug Fixes

  • generate correct deserializers for i32/u32 fields (86438e2)
  • handle u64 integer precision loss across Rust-JS boundary (e96e7fa)
  • handle u64 integer precision loss across Rust-JS boundary (c3a3c69)
  • harden serde_utils integer deserialization and add missing i64 vec deserializers (4afc52e)
hyperstack-server: 0.5.9

0.5.9 (2026-03-19)

Bug Fixes

  • apply u64 string transform to live bus updates in projector (c179f06)
  • convert negative i64 values outside MIN_SAFE_INTEGER to strings in WebSocket frames (de89478)
  • handle u64 integer precision loss across Rust-JS boundary (e96e7fa)
  • handle u64 integer precision loss across Rust-JS boundary (c3a3c69)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-interpreter bumped from 0.5.8 to 0.5.9
hyperstack-stacks: 0.5.9

0.5.9 (2026-03-19)

Bug Fixes

  • handle u64 integer precision loss across Rust-JS boundary (e96e7fa)
  • handle u64 integer precision loss across Rust-JS boundary (c3a3c69)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-sdk bumped from 0.5.6 to 0.5.9
hyperstack-npm: 0.5.9

0.5.9 (2026-03-19)

Miscellaneous Chores

  • hyperstack-npm: Synchronize hyperstack versions
hyperstack-react: 0.5.9

0.5.9 (2026-03-19)

Miscellaneous Chores

  • hyperstack-react: Synchronize hyperstack versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-typescript bumped from ^0.5.6 to ^0.5.9
hyperstack-stacks: 0.5.9

0.5.9 (2026-03-19)

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.9
    • peerDependencies
      • hyperstack-react bumped from >=0.5.6 to >=0.5.9
      • hyperstack-typescript bumped from >=0.5.6 to >=0.5.9
hyperstack-typescript: 0.5.9

0.5.9 (2026-03-19)

Miscellaneous Chores

  • hyperstack-typescript: Synchronize hyperstack versions

This PR was generated with Release Please. See documentation.

@vercel
Copy link

vercel bot commented Mar 19, 2026 •
edited
Loading

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

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

Request Review

@greptile-apps
Copy link

greptile-apps bot commented Mar 19, 2026

Greptile Summary

This is an automated release PR generated by Release Please, bumping all packages in the monorepo to version 0.5.9. The release includes several bug fixes related to u64/i64 integer precision loss across the Rust-JS boundary, correct deserialization for i32/u32 fields, and hardened serde_utils integer deserialization. Packages that were previously behind at 0.5.6 (hyperstack-sdk, hyperstack-stacks, TypeScript packages) are aligned to 0.5.9 alongside those at 0.5.8.

  • All Rust crates (hyperstack, hyperstack-cli, hyperstack-interpreter, hyperstack-macros, hyperstack-sdk, hyperstack-server, hyperstack-stacks) bumped to 0.5.9 with intra-workspace dependency versions updated consistently.
  • All TypeScript/npm packages (hyperstack-typescript, hyperstack-react, hyperstack-stacks, packages/hyperstack) bumped to 0.5.9; peer dependency lower bounds in stacks/sdk/typescript tightened to >=0.5.9.
  • Cargo.lock and package-lock.json files updated to reflect new versions.
  • One minor discrepancy: typescript/react/package-lock.json retains the stale range ^0.5.4 for hyperstack-typescript in the root packages[""] block, while package.json correctly declares ^0.5.9. The resolved locked version is 0.5.9 so it poses no practical risk, but the lockfile should be regenerated to keep the two files fully in sync.

Confidence Score: 5/5

  • This PR is safe to merge — it is a straightforward automated release bump with no logic changes.
  • All changes are mechanical version bumps and changelog entries generated by Release Please. The Cargo.lock and package-lock.json files are consistent with the updated manifests. The only minor issue is a stale dependency range in typescript/react/package-lock.json (^0.5.4 vs ^0.5.9), which does not affect resolution since 0.5.9 satisfies ^0.5.4. No functional code was modified in this PR.
  • No files require special attention; typescript/react/package-lock.json has a trivial stale range that can optionally be cleaned up.

Important Files Changed

Filename Overview
.release-please-manifest.json All package versions bumped to 0.5.9 (or kept at 0.1.5 for hyperstack-idl); straightforward manifest update.
Cargo.lock All Rust crates bumped to 0.5.9; lockfile is consistent with updated Cargo.toml versions.
typescript/react/package-lock.json Package version updated to 0.5.9, but the root packages[""].dependencies entry for hyperstack-typescript still shows the old stale range ^0.5.4 instead of matching the package.json range ^0.5.9.
typescript/react/package.json Version bumped to 0.5.9 and hyperstack-typescript dependency correctly updated to ^0.5.9.
stacks/sdk/typescript/package.json Version bumped to 0.5.9; peerDependency ranges tightened to >=0.5.9 as expected for aligned release.
stacks/sdk/typescript/package-lock.json Version and resolved hyperstack-typescript version both updated to 0.5.9; consistent with package.json.
rust/hyperstack-server/Cargo.toml Version bumped to 0.5.9 and hyperstack-interpreter dependency updated to 0.5.9; consistent.
rust/hyperstack-sdk/Cargo.toml Version bumped from 0.5.6 to 0.5.9; no other changes needed (no workspace dependencies).
hyperstack/Cargo.toml Version bumped to 0.5.9; all four optional dependency versions updated consistently.
stacks/sdk/rust/Cargo.toml Version bumped from 0.5.6 to 0.5.9; hyperstack-sdk dependency also updated to 0.5.9.
interpreter/Cargo.toml Version bumped to 0.5.9; hyperstack-macros dependency updated consistently.
hyperstack-macros/Cargo.toml Version bumped to 0.5.9 with no dependency changes; straightforward bump.
cli/Cargo.toml Version bumped to 0.5.9; hyperstack-interpreter dependency updated consistently.
typescript/core/package.json Version bumped from 0.5.6 to 0.5.9; no dependency changes needed.
packages/hyperstack/package.json npm CLI wrapper version bumped from 0.5.6 to 0.5.9; no other changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    subgraph Rust ["Rust Packages → 0.5.9"]
        macros["hyperstack-macros\n0.5.8 → 0.5.9"]
        interp["hyperstack-interpreter\n0.5.8 → 0.5.9"]
        sdk_rust["hyperstack-sdk\n0.5.6 → 0.5.9"]
        server["hyperstack-server\n0.5.8 → 0.5.9"]
        stacks_rust["hyperstack-stacks (rust)\n0.5.6 → 0.5.9"]
        hs["hyperstack\n0.5.8 → 0.5.9"]
        cli["hyperstack-cli\n0.5.8 → 0.5.9"]
    end

    subgraph TS ["TypeScript / npm Packages → 0.5.9"]
        core["hyperstack-typescript\n0.5.6 → 0.5.9"]
        react["hyperstack-react\n0.5.6 → 0.5.9"]
        stacks_ts["hyperstack-stacks (ts)\n0.5.6 → 0.5.9"]
        npm["hyperstack-cli (npm)\n0.5.6 → 0.5.9"]
    end

    macros --> interp
    macros --> hs
    interp --> server
    interp --> hs
    interp --> cli
    sdk_rust --> stacks_rust
    sdk_rust --> hs
    server --> hs
    core --> react
    core --> stacks_ts
Loading
Prompt To Fix All With AI 
This is a comment left during a code review.
Path: typescript/react/package-lock.json
Line: 12

Comment:
**Stale lockfile dependency range**

`package.json` was updated to `"hyperstack-typescript": "^0.5.9"`, but the `package-lock.json` still declares `"^0.5.4"` in the root package's `packages[""].dependencies` block. In `lockfileVersion: 3`, this section is expected to mirror `package.json` exactly.

While `^0.5.4` does satisfy `0.5.9` (so `npm ci` will still resolve the correct locked version), the two files are out of sync. Running `npm install` after a fresh checkout would update this line to `^0.5.9`, producing an unintended diff. It's worth regenerating the lock file with `npm install` so it accurately reflects the declared range.

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

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

Last reviewed commit: "chore: release main"

greptile-apps[bot]
greptile-apps bot reviewed Mar 19, 2026
View reviewed changes
typescript/react/package-lock.json
"version": "0.5.9",
"license": "MIT",
"dependencies": {
"hyperstack-typescript": "^0.5.4",
Copy link

@greptile-apps greptile-apps bot Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Stale lockfile dependency range

package.json was updated to "hyperstack-typescript": "^0.5.9", but the package-lock.json still declares "^0.5.4" in the root package's packages[""].dependencies block. In lockfileVersion: 3, this section is expected to mirror package.json exactly.

While ^0.5.4 does satisfy 0.5.9 (so npm ci will still resolve the correct locked version), the two files are out of sync. Running npm install after a fresh checkout would update this line to ^0.5.9, producing an unintended diff. It's worth regenerating the lock file with npm install so it accurately reflects the declared range.

Suggested change
"hyperstack-typescript": "^0.5.4",
"hyperstack-typescript": "^0.5.9",
Prompt To Fix With AI 
This is a comment left during a code review.
Path: typescript/react/package-lock.json
Line: 12

Comment:
**Stale lockfile dependency range**

`package.json` was updated to `"hyperstack-typescript": "^0.5.9"`, but the `package-lock.json` still declares `"^0.5.4"` in the root package's `packages[""].dependencies` block. In `lockfileVersion: 3`, this section is expected to mirror `package.json` exactly.

While `^0.5.4` does satisfy `0.5.9` (so `npm ci` will still resolve the correct locked version), the two files are out of sync. Running `npm install` after a fresh checkout would update this line to `^0.5.9`, producing an unintended diff. It's worth regenerating the lock file with `npm install` so it accurately reflects the declared range.

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

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

@adiman9 adiman9 merged commit 8e0cca3 into main Mar 19, 2026
3 checks passed
@adiman9 adiman9 deleted the release-please--branches--main branch March 19, 2026 14:54
@github-actions
Copy link
Contributor Author

github-actions bot commented Mar 19, 2026

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@greptile-apps greptile-apps[bot] greptile-apps[bot] left review comments

Assignees

No one assigned

Labels

autorelease: tagged

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@adiman9