Repository navigation
Conversation
…ored tarball @valueflows/vf-graphql-holochain 0.700.0-rc.0 is on npm (h-REA/hREA#412), published by hREA's CI with provenance. The UI now depends on ^0.700.0-rc.0 from the registry, and bun.lock (regenerated with the flake's bun) pins its npm integrity. The published package is the vendored tarball's code, file for file; only its package.json gains repository, homepage and bugs. The tarball, its .sha256 and the vendor README that described it go. vendor/hrea, the submodule the hApp builds its hrea DNA from, stays.
Soushi888
marked this pull request as ready for review
November 4, 2026 00:37
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The hREA GraphQL adapter is on npm:
@valueflows/[email protected], published 2026-11-03 by hREA's CI through npm trusted publishing, with SLSA provenance (h-REA/hREA#412). The UI now installs it from the registry, and the tarball #155 vendored for #153 goes.vendor/hrea, the submodule the hApp builds itshreaDNA from, is untouched.Changes
ui/package.json:file:../vendor/…tgzbecomes^0.700.0-rc.0.bun.lockregenerated with the flake's bun (1.2.13, the one CI uses); its only change is that entry, now pinned to the npm integritysha512-HdnnB44Q…MSnGw==, the valuenpm view … dist.integrityreturns.vendor/valueflows-vf-graphql-holochain-0.700.0-rc.0.tgz, its.sha256, andvendor/README.md, which described only that tarball.ui/README.md,documentation/hREA/integration-strategy.md(the read-only bound on the adapter is unchanged, only where it comes from),documentation/specifications/ui_architecture.md.Same code as the vendored copy
The published tarball and the vendored one were unpacked side by side:
diff -rdiffers inpackage.jsononly, which gainsrepository,homepageandbugs(hREA #418 added them so npm could attest provenance). Every JavaScript and type file is identical.Verification
Run in
nix developon this branch, and on a cleanorigin/devworktree for comparison:bun installsvelte-check.svelte-kitsync (1 on a cold first run, both sides)vitest(chromium)prettier --check .inui/vite build --mode productionThe one failing spec,
src/routes/page.svelte.spec.ts, cannot resolvevirtual:uno.cssfrom+layout.svelte. It fails identically ondevand has nothing to do with the adapter. The files this branch touches pass Prettier.Schema smoke:
createHolochainSchemafrom the installed npm package, with a dummy cell, builds and exposes the Proposal, Agreement, Commitment and EconomicEvent surface,fulfillsandclauseOfincluded. The adapter is not wired to any screen yet, so this is the check that the real module loads.In CI on
4fbc22c:build,rustfmt, all seven Sweettest legs (governance, misc, nondominium a and b, person, resource) and the Playwrighte2ejob passes 23/23 in 2.6 minutes.