Skip to content

chore: release main#61

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

chore: release main#61
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-idl: 0.1.3

0.1.3 (2026-03-19)

Bug Fixes

  • align Steel discriminant size with get_discriminator return value (4d283f2)
  • change any() to all() for Steel-style IDL detection (77d2566)
  • Core interpreter and server improvements (b05ae9b)
  • implement discriminant size inference and fix test failures (c8b26d5)
  • prevent empty instruction arrays from being misclassified as Steel-style (abad594)
  • replace panicking expect with graceful fallback in get_discriminator (fa09ef9)
  • replace silent u8 truncation of Steel discriminant with try_from (f4de6ef)
  • replace unnecessary unwrap with if let pattern (b3e6dac)
  • tests: replace diagnostic println with assertion for discriminant_size (f391581)
hyperstack: 0.5.6

0.5.6 (2026-03-19)

Features

  • add Keccak256 hashing and slot hash caching (768c407)

Dependencies

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

0.5.6 (2026-03-19)

Miscellaneous Chores

  • hyperstack-cli: Synchronize hyperstack versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-interpreter bumped from 0.5.5 to 0.5.6
      • hyperstack-idl bumped from 0.1.2 to 0.1.3
hyperstack-interpreter: 0.5.6

0.5.6 (2026-03-19)

Features

  • add Keccak256 hashing and slot hash caching (768c407)
  • Add rt-multi-thread (a426edb)
  • add skip_resolvers mechanism for stale data reprocessing (a11c669)

Bug Fixes

  • add missing return to AbortIfNullKey opcode (8d98359)
  • align Steel discriminant size with get_discriminator return value (4d283f2)
  • Core interpreter and server improvements (b05ae9b)
  • correct resolver output types and schema generation in TypeScript emitter (b37ef43)
  • correct SlotHashResolver TypeScript types to match actual return values (358d9bd)
  • derive state_id from bytecode routing for PDA cache (927b364)
  • prevent panic in SlotHash resolver when using current_thread runtime (3525397)
  • prevent silent byte truncation in json_array_to_bytes (10ff8aa)
  • reduce MAX_CACHE_SIZE from 50k to 1k (462230f)
  • resolve clippy warnings across workspace (c19d1ec)
  • restore cross-account lookup resolution at round boundaries (0af0835)
  • serialize pre_reveal_rng as string to avoid JS precision loss (9f07692)
  • serialize u64-from-bytes computed fields as strings to avoid JS precision loss (1f67a7a)
  • TypeScript generator now correctly types computed fields using resolver output types (5d28937)
  • use BTreeMap for slot hash cache to ensure oldest entries are evicted (94249ba)
  • use BTreeMap in ResolverRegistry to ensure deterministic SDK output (0129f75)
  • wrap slot hash bytes in object to match SlotHashBytes schema (247ffa3)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-macros bumped from 0.5.5 to 0.5.6
      • hyperstack-idl bumped from 0.1.2 to 0.1.3
hyperstack-macros: 0.5.6

0.5.6 (2026-03-19)

Features

  • add Keccak256 hashing and slot hash caching (768c407)
  • improve slot scheduler with notification-based waiting and enhanced logging (0b8681e)

Bug Fixes

  • cache account data for all entity states that route an event type (1b59633)
  • conditionally enable TLS only for https/grpcs endpoints in slot subscription (8c8875b)
  • Core interpreter and server improvements (b05ae9b)
  • correct resolver output types and schema generation in TypeScript emitter (b37ef43)
  • derive state_id from bytecode routing for PDA cache (927b364)
  • keep gRPC subscription sender alive to prevent stream termination (42460d2)
  • prevent integer overflow in SlotHashes sysvar parsing (99427f6)
  • prevent panic in SlotHash resolver when using current_thread runtime (3525397)
  • remove unnecessary async from parse_and_cache_slot_hashes (03e00aa)
  • resolve clippy warnings across workspace (c19d1ec)
  • restore cross-account lookup resolution at round boundaries (0af0835)
  • serialize u64-from-bytes computed fields as strings to avoid JS precision loss (1f67a7a)
  • use dynamic-length discriminator slice in generated code (d67b727)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-idl bumped from 0.1.2 to 0.1.3
hyperstack-sdk: 0.5.6

0.5.6 (2026-03-19)

Miscellaneous Chores

  • hyperstack-sdk: Synchronize hyperstack versions
hyperstack-server: 0.5.6

0.5.6 (2026-03-19)

Features

  • add Yellowstone gRPC dependencies and update Ore examples (2f23205)

Bug Fixes

  • Core interpreter and server improvements (b05ae9b)
  • resolve clippy warnings across workspace (c19d1ec)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-interpreter bumped from 0.5.5 to 0.5.6
hyperstack-stacks: 0.5.6

0.5.6 (2026-03-19)

Miscellaneous Chores

  • hyperstack-stacks: Synchronize hyperstack versions

Dependencies

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

0.5.6 (2026-03-19)

Miscellaneous Chores

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

0.5.6 (2026-03-19)

Miscellaneous Chores

  • hyperstack-react: Synchronize hyperstack versions

Dependencies

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

0.5.6 (2026-03-19)

Features

  • add Yellowstone gRPC dependencies and update Ore examples (2f23205)

Bug Fixes

  • correct resolver output types and schema generation in TypeScript emitter (b37ef43)
  • Keccak types (7af4cf3)
  • Ore sdk (5f423da)
  • serialize pre_reveal_rng as string to avoid JS precision loss (9f07692)
  • TypeScript generator now correctly types computed fields using resolver output types (5d28937)

Dependencies

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

0.5.6 (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 9:21am

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 the full workspace to 0.5.6 (Rust crates and npm packages) and hyperstack-idl to 0.1.3. The changes consist entirely of version bumps across Cargo.toml files, package.json files, Cargo.lock, package-lock.json files, and generated CHANGELOG.md entries capturing the accumulated fixes and features merged since 0.5.5.

Key issues found:

  • The typescript/react/package-lock.json root packages."" entry still records "hyperstack-typescript": "^0.5.4" while package.json was updated to ^0.5.6. This stale specifier means the lock file was not properly regenerated and may cause npm ci to fail.
  • The stacks/sdk/typescript/CHANGELOG.md claims the hyperstack-typescript devDependency was bumped from file:../../../typescript/core to 0.5.6, but stacks/sdk/typescript/package.json still references the unchanged file:../../../typescript/core path. This CHANGELOG entry is inaccurate and was likely generated incorrectly by the Release Please automation.

Confidence Score: 3/5

  • Mostly safe to merge, but the stale package-lock.json entry may break CI pipelines that use npm ci for the hyperstack-react package.
  • The bulk of the changes are straightforward, consistent version bumps across Rust and TypeScript packages. However, the typescript/react/package-lock.json root entry retains a stale ^0.5.4 specifier for hyperstack-typescript instead of reflecting the ^0.5.6 in package.json, which can cause npm ci to fail. Additionally, the stacks/sdk/typescript/CHANGELOG.md contains a factually incorrect dependency change entry.
  • typescript/react/package-lock.json needs regeneration to sync with package.json; stacks/sdk/typescript/CHANGELOG.md contains an inaccurate devDependency bump entry.

Important Files Changed

Filename Overview
.release-please-manifest.json Version manifest correctly updated from 0.5.5→0.5.6 for all crates/packages and 0.1.2→0.1.3 for hyperstack-idl.
Cargo.lock Lock file updated consistently with all Rust package version bumps.
typescript/react/package-lock.json Root package entry retains stale "hyperstack-typescript": "^0.5.4" specifier while package.json was bumped to ^0.5.6; lock file is out of sync.
stacks/sdk/typescript/CHANGELOG.md CHANGELOG claims devDependency hyperstack-typescript was bumped from file:../../../typescript/core to 0.5.6, but the actual package.json still references the local file path unchanged.
stacks/sdk/typescript/package.json Peer dependency range bumped to >=0.5.6; devDependency hyperstack-typescript still uses local file: path (unchanged), contradicting the CHANGELOG.
interpreter/Cargo.toml Version bumped to 0.5.6 with consistent dependency version updates for hyperstack-macros and hyperstack-idl.
hyperstack-idl/Cargo.toml Version correctly bumped from 0.1.2 to 0.1.3.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    RP[Release Please Bot] --> Manifest[.release-please-manifest.json\n0.5.5 → 0.5.6 / idl 0.1.2 → 0.1.3]

    Manifest --> RustCrates
    Manifest --> NpmPackages

    subgraph RustCrates[Rust Crates bumped to 0.5.6]
        IDL[hyperstack-idl\n0.1.2 → 0.1.3]
        Macros[hyperstack-macros\n0.5.5 → 0.5.6]
        Interp[hyperstack-interpreter\n0.5.5 → 0.5.6]
        Server[hyperstack-server\n0.5.5 → 0.5.6]
        SDK[hyperstack-sdk\n0.5.5 → 0.5.6]
        Stacks[hyperstack-stacks rust\n0.5.5 → 0.5.6]
        Core[hyperstack\n0.5.5 → 0.5.6]
        CLI[hyperstack-cli\n0.5.5 → 0.5.6]
        IDL --> Macros & Interp & CLI
        Macros --> Interp
        Interp --> Server & Core & CLI
        SDK --> Core & Stacks
    end

    subgraph NpmPackages[npm Packages bumped to 0.5.6]
        TSCore[hyperstack-typescript\n0.5.5 → 0.5.6]
        TSReact[hyperstack-react\n0.5.5 → 0.5.6]
        TSStacks[hyperstack-stacks ts\n0.5.5 → 0.5.6]
        HsCLI[hyperstack-cli npm\n0.5.5 → 0.5.6]
        TSCore --> TSReact
        TSReact --> TSStacks
    end

    LockIssue["⚠️ typescript/react/package-lock.json\nstill has ^0.5.4 for hyperstack-typescript\n(should be ^0.5.6)"]
    TSCore -.->|stale lock entry| LockIssue
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 lock file entry for `hyperstack-typescript`**

The root `packages.""` entry in `package-lock.json` still records `"hyperstack-typescript": "^0.5.4"`, but `typescript/react/package.json` was updated in this PR to `"hyperstack-typescript": "^0.5.6"`. In npm lockfile v3 format the `packages.""` section is expected to mirror `package.json` exactly. This mismatch means the lock file was not regenerated after the dependency bump and can cause `npm ci` to fail with a consistency check error.

The lock file should be regenerated (`npm install`) to align with the updated `package.json`.

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

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/CHANGELOG.md
Line: 23-24

Comment:
**CHANGELOG entry does not reflect actual `package.json` change**

The changelog states that `hyperstack-typescript` devDependency was bumped from `file:../../../typescript/core` to `0.5.6`, but `stacks/sdk/typescript/package.json` still contains the unchanged local file path reference:

```json
"devDependencies": {
  "hyperstack-typescript": "file:../../../typescript/core",
  ...
}
```

The `devDependency` was never actually changed in this PR, so this changelog entry is inaccurate. This was likely generated incorrectly by Release Please. The entry should be removed or corrected to avoid confusion about what the `0.5.6` release actually changed.

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.6",
"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.

P1 Stale lock file entry for hyperstack-typescript

The root packages."" entry in package-lock.json still records "hyperstack-typescript": "^0.5.4", but typescript/react/package.json was updated in this PR to "hyperstack-typescript": "^0.5.6". In npm lockfile v3 format the packages."" section is expected to mirror package.json exactly. This mismatch means the lock file was not regenerated after the dependency bump and can cause npm ci to fail with a consistency check error.

The lock file should be regenerated (npm install) to align with the updated package.json.

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

Comment:
**Stale lock file entry for `hyperstack-typescript`**

The root `packages.""` entry in `package-lock.json` still records `"hyperstack-typescript": "^0.5.4"`, but `typescript/react/package.json` was updated in this PR to `"hyperstack-typescript": "^0.5.6"`. In npm lockfile v3 format the `packages.""` section is expected to mirror `package.json` exactly. This mismatch means the lock file was not regenerated after the dependency bump and can cause `npm ci` to fail with a consistency check error.

The lock file should be regenerated (`npm install`) to align with the updated `package.json`.

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

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

stacks/sdk/typescript/CHANGELOG.md
Comment on lines +23 to +24
* devDependencies
* hyperstack-typescript bumped from file:../../../typescript/core to 0.5.6
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 CHANGELOG entry does not reflect actual package.json change

The changelog states that hyperstack-typescript devDependency was bumped from file:../../../typescript/core to 0.5.6, but stacks/sdk/typescript/package.json still contains the unchanged local file path reference:

"devDependencies": {
  "hyperstack-typescript": "file:../../../typescript/core",
  ...
}

The devDependency was never actually changed in this PR, so this changelog entry is inaccurate. This was likely generated incorrectly by Release Please. The entry should be removed or corrected to avoid confusion about what the 0.5.6 release actually changed.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: stacks/sdk/typescript/CHANGELOG.md
Line: 23-24

Comment:
**CHANGELOG entry does not reflect actual `package.json` change**

The changelog states that `hyperstack-typescript` devDependency was bumped from `file:../../../typescript/core` to `0.5.6`, but `stacks/sdk/typescript/package.json` still contains the unchanged local file path reference:

```json
"devDependencies": {
  "hyperstack-typescript": "file:../../../typescript/core",
  ...
}
```

The `devDependency` was never actually changed in this PR, so this changelog entry is inaccurate. This was likely generated incorrectly by Release Please. The entry should be removed or corrected to avoid confusion about what the `0.5.6` release actually changed.

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

@adiman9 adiman9 merged commit 4f9f7f4 into main Mar 19, 2026
3 checks passed
@adiman9 adiman9 deleted the release-please--branches--main branch March 19, 2026 09:25
@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