Skip to content

chore: release main#63

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

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

Conversation

@github-actions
Copy link
Contributor

🤖 I have created a release beep boop

hyperstack: 0.5.7

0.5.7 (2026-03-19)

Dependencies

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

0.5.7 (2026-03-19)

Dependencies

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

0.1.4 (2026-03-19)

Bug Fixes

  • Improve Steel IDL detection for 1-byte discriminator arrays (3fcd1ee)
  • Improve Steel IDL detection for 1-byte discriminator arrays (f3a7f9c)
hyperstack-interpreter: 0.5.7

0.5.7 (2026-03-19)

Dependencies

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

0.5.7 (2026-03-19)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-idl bumped from 0.1.3 to 0.1.4
hyperstack-server: 0.5.7

0.5.7 (2026-03-19)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • hyperstack-interpreter bumped from 0.5.6 to 0.5.7

This PR was generated with Release Please. See documentation.

@vercel
Copy link

vercel bot commented Mar 19, 2026

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 10:31am

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 hyperstack-idl from 0.1.3 to 0.1.4 and propagating that change (along with a patch bump) across hyperstack, hyperstack-cli, hyperstack-interpreter, hyperstack-macros, and hyperstack-server (all 0.5.60.5.7). The root change being released is a bug fix improving Steel IDL detection for 1-byte discriminator arrays.

  • All Cargo.toml version fields and inter-workspace dependency version pins are consistent with the .release-please-manifest.json.
  • Cargo.lock correctly reflects all six version bumps.
  • rust/hyperstack-sdk is intentionally left at 0.5.6 — it has no changes in this release, which is correct per the manifest.
  • hyperstack-idl/CHANGELOG.md contains a duplicate entry for the same bug fix ("Improve Steel IDL detection for 1-byte discriminator arrays") under two different commit hashes (3fcd1ee and f3a7f9c), suggesting two commits carried identical messages for the same logical fix.

Confidence Score: 5/5

  • This PR is safe to merge — it contains only auto-generated version bumps and changelog updates with no functional code changes.
  • All version numbers are consistent across every manifest, Cargo.toml, and Cargo.lock entry. The only finding is a cosmetic duplicate changelog entry in hyperstack-idl that does not affect runtime behavior.
  • hyperstack-idl/CHANGELOG.md — contains a duplicate bug fix entry worth cleaning up before future releases.

Important Files Changed

Filename Overview
.release-please-manifest.json Version manifest correctly bumped: hyperstack, interpreter, hyperstack-macros, cli, rust/hyperstack-server to 0.5.7 and hyperstack-idl to 0.1.4; rust/hyperstack-sdk intentionally left at 0.5.6.
hyperstack-idl/CHANGELOG.md Auto-generated 0.1.4 changelog contains a duplicate entry for "Improve Steel IDL detection for 1-byte discriminator arrays" pointing to two different commits — likely from two commits with identical messages.
hyperstack/Cargo.toml Version bumped to 0.5.7; all workspace dependency versions correctly updated; hyperstack-sdk intentionally remains at 0.5.6 matching the manifest.
Cargo.lock Lock file consistently reflects all six version bumps across hyperstack, hyperstack-cli, hyperstack-idl, hyperstack-interpreter, hyperstack-macros, and hyperstack-server.
cli/Cargo.toml Version bumped to 0.5.7; hyperstack-interpreter updated to 0.5.7 and hyperstack-idl updated to 0.1.4.
interpreter/Cargo.toml Version bumped to 0.5.7; hyperstack-macros updated to 0.5.7 and hyperstack-idl updated to 0.1.4.
hyperstack-macros/Cargo.toml Version bumped to 0.5.7; hyperstack-idl dependency updated to 0.1.4.
rust/hyperstack-server/Cargo.toml Version bumped to 0.5.7; hyperstack-interpreter updated to 0.5.7.
hyperstack-idl/Cargo.toml Version correctly bumped from 0.1.3 to 0.1.4; no dependency version changes required.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    idl["hyperstack-idl\n0.1.3 → 0.1.4\n(bug fix: Steel IDL detection)"]
    macros["hyperstack-macros\n0.5.6 → 0.5.7"]
    interp["hyperstack-interpreter\n0.5.6 → 0.5.7"]
    server["hyperstack-server\n0.5.6 → 0.5.7"]
    cli["hyperstack-cli\n0.5.6 → 0.5.7"]
    main["hyperstack\n0.5.6 → 0.5.7"]
    sdk["hyperstack-sdk\n0.5.6 (unchanged)"]

    idl --> macros
    idl --> interp
    macros --> interp
    interp --> server
    interp --> cli
    idl --> cli
    server --> main
    macros --> main
    interp --> main
    sdk --> main
Loading
Prompt To Fix All With AI
This is a comment left during a code review.
Path: hyperstack-idl/CHANGELOG.md
Line: 8-9

Comment:
**Duplicate changelog entry for the same fix**

The same bug fix description — "Improve Steel IDL detection for 1-byte discriminator arrays" — appears twice in the `0.1.4` section, linked to two different commits (`3fcd1ee` and `f3a7f9c`). This is auto-generated by Release Please based on commit history, suggesting that two separate commits carried the exact same message for what appears to be the same logical fix.

While this doesn't affect runtime behavior, it creates a misleading changelog. If one commit is a fixup or amendment of the other, consider squashing them before the next release or clarifying the commit messages so Release Please can distinguish them. The second commit (`f3a7f9c`) can be verified [here](https://github.com/HyperTekOrg/hyperstack/commit/f3a7f9c628b4a66d195cc510707bb721a2908fad).

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

Last reviewed commit: "chore: release main"

Comment on lines +8 to +9
* Improve Steel IDL detection for 1-byte discriminator arrays ([3fcd1ee](https://github.com/HyperTekOrg/hyperstack/commit/3fcd1ee31bf5b01353c69c5630c122667557ddf6))
* Improve Steel IDL detection for 1-byte discriminator arrays ([f3a7f9c](https://github.com/HyperTekOrg/hyperstack/commit/f3a7f9c628b4a66d195cc510707bb721a2908fad))
Copy link

Choose a reason for hiding this comment

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

P2 Duplicate changelog entry for the same fix

The same bug fix description — "Improve Steel IDL detection for 1-byte discriminator arrays" — appears twice in the 0.1.4 section, linked to two different commits (3fcd1ee and f3a7f9c). This is auto-generated by Release Please based on commit history, suggesting that two separate commits carried the exact same message for what appears to be the same logical fix.

While this doesn't affect runtime behavior, it creates a misleading changelog. If one commit is a fixup or amendment of the other, consider squashing them before the next release or clarifying the commit messages so Release Please can distinguish them. The second commit (f3a7f9c) can be verified here.

Prompt To Fix With AI
This is a comment left during a code review.
Path: hyperstack-idl/CHANGELOG.md
Line: 8-9

Comment:
**Duplicate changelog entry for the same fix**

The same bug fix description — "Improve Steel IDL detection for 1-byte discriminator arrays" — appears twice in the `0.1.4` section, linked to two different commits (`3fcd1ee` and `f3a7f9c`). This is auto-generated by Release Please based on commit history, suggesting that two separate commits carried the exact same message for what appears to be the same logical fix.

While this doesn't affect runtime behavior, it creates a misleading changelog. If one commit is a fixup or amendment of the other, consider squashing them before the next release or clarifying the commit messages so Release Please can distinguish them. The second commit (`f3a7f9c`) can be verified [here](https://github.com/HyperTekOrg/hyperstack/commit/f3a7f9c628b4a66d195cc510707bb721a2908fad).

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

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

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant