Skip to content

chore(deps): move the hREA submodule to happ-0.5.0-beta.1 - #169

Closed
Soushi888 wants to merge 2 commits into
devfrom
chore/154-hrea-beta1
Closed

Soushi888 wants to merge 2 commits into
devfrom
chore/154-hrea-beta1

Conversation

@Soushi888

Copy link
Copy Markdown
Collaborator

SoushAI analysis. Drafted by Soushi's AI assistant, reviewed and posted by @Soushi888.

Summary

Nondominium's hrea DNA is built from the vendor/hrea submodule. Until now it tracked main-0.6 on a Sensorica fork over SSH. This PR points it at the upstream release instead: https://github.com/h-REA/hREA.git, pinned to commit 79c8d4fb98c4f7f9a8cf3f7dd69690d6d1334d85, the commit under the annotated tag happ-0.5.0-beta.1 (the tag object is 244da223bf4b6e1288828c23bc284f0df0f6ce06). That release is the Holochain 0.7, ValueFlows 1.0 line. The README, vendor README, implementation status and hREA integration strategy now name the tag instead of the fork.

This layer changes no code. The pinned DNA needs a Holochain 0.7 toolchain, so on its own it does not build under the current Holonix 0.6 shell. It is the bottom of a stack and lands together with the Holochain 0.7 port above it (#130). The adapter vendored in #155 (@valueflows/vf-graphql-holochain 0.700.0-rc.0) is the one the release documents for this tag.

Changes
  • Submodule source: .gitmodules uses the public https URL and drops the branch = main-0.6 line, since the pin is a tag and not a branch to follow. vendor/hrea moves from fc3b5e78 to 79c8d4fb.
  • Docs: README, vendor/README.md, documentation/IMPLEMENTATION_STATUS.md and documentation/hREA/integration-strategy.md name the tag and commit. The integration strategy's risk table records that the HDK version mismatch it rated "Low" is now real: the tag uses hdk 0.7.0 and hdi 0.8.0.
Decisions
  • Pin the commit, record the tag: the tag is annotated, so the gitlink holds the commit it points at (79c8d4fb), and the docs name both the tag and that commit.
  • The release's consumer notes: hREA's docs/consuming-a-release.md asks for @holochain/client ^0.21.0, a 0.7.x conductor, the adapter on the 0.700 line, the TypedAction<T> validation signatures, the { header, data } action shape and a getrandom backend flag for wasm builds. The adapter is already in place (chore(deps): vendor the hREA GraphQL adapter 0.700.0-rc.0 into the UI #155). The client and the Rust side belong to the Holochain 0.7 port, so they are applied in chore(deps): upgrade to Holochain 0.7.1 #130 and not here.
How to test

git submodule update --init vendor/hrea && git -C vendor/hrea describe --tags prints happ-0.5.0-beta.1. Building the hApp needs the Holochain 0.7 layer from #130, so the build and test matrix runs there.

Documentation

Updated README.md, vendor/README.md, documentation/IMPLEMENTATION_STATUS.md and documentation/hREA/integration-strategy.md to name the release tag and commit.

Related

Closes #154

Pre-open review

  • Description: Summary stands alone, Closes #154, disclosure line first. Pass.
  • Merge state: rebased onto origin/dev (7faf650); the three commits of chore(deps): vendor the hREA GraphQL adapter 0.700.0-rc.0 into the UI #155 already in dev were dropped, one conflict in documentation/hREA/integration-strategy.md resolved by keeping both the adapter bound paragraph and the new repository line. Pass.
  • Code findings: none, no code changed; the gitlink resolves to the commit the tag points at (git ls-remote on h-REA/hREA: tag object 244da223, peeled 79c8d4fb). Pass.
  • Documentation: four docs updated, listed above. Pass.
  • Tests: none apply to this layer. Open item: the Build check cannot go green here, since a Holochain 0.7 DNA does not compile on the Holonix 0.6 shell. The matrix runs on chore(deps): upgrade to Holochain 0.7.1 #130.

Point vendor/hrea at the upstream repository over https and pin it to
79c8d4fb, the commit tagged happ-0.5.0-beta.1. The branch line is
dropped: the pin is a release tag, not a branch to follow.

Refs #154
The README, the vendor README, the implementation status and the
integration strategy still named the Sensorica fork on main-0.6. They
now name the upstream release tag and its commit, and the integration
strategy records that the pin needs the Holochain 0.7 toolchain.

Refs #154
@Soushi888 Soushi888 added dual-dna Dual-DNA architecture - cross-DNA bridge calls and bundling hrea hREA integration - Holochain Resource-Event-Agent ValueFlows backend labels Nov 3, 2026
@Soushi888
Soushi888 changed the base branch from dev to main November 3, 2026 23:34
@Soushi888
Soushi888 added this pull request to stack #175 November 3, 2026 23:34
@Soushi888
Soushi888 removed this pull request from stack #175 November 3, 2026 23:34
@Soushi888
Soushi888 changed the base branch from main to dev November 3, 2026 23:34
@Soushi888
Soushi888 added this pull request to stack #176 November 3, 2026 23:34
@Soushi888

Copy link
Copy Markdown
Collaborator Author

SoushAI analysis. Drafted by Soushi's AI assistant, reviewed and posted by @Soushi888.

Staying a draft, one blocker: the Build check cannot go green on this layer alone. The pinned hREA DNA (happ-0.5.0-beta.1) needs a Holochain 0.7 toolchain, and dev still builds on Holonix 0.6. The failing step is build:zomes:hrea, error[E0658]: use of unstable library feature round_char_boundary while compiling holochain_zome_types. This is not a pre-existing failure on dev; it comes from this change by design, and it is fixed by #130 on top (Build passes there). The stack is meant to land as one atomic merge (gh stack merge), so the red check on this layer is expected. Whether to merge it that way, or to fold #130's toolchain into this layer, is Soushi's call.

@Soushi888
Soushi888 removed this pull request from stack #176 November 3, 2026 23:54
@Soushi888

Copy link
Copy Markdown
Collaborator Author

SoushAI analysis. Drafted by Soushi's AI assistant, reviewed and posted by @Soushi888.

Folded into #130, which already contains this PR's commits (the hREA submodule move and its docs). A Holochain 0.7 hREA DNA cannot build on the 0.6 shell alone, so this layer could never pass its Build check by itself; #130 carries the toolchain and now also the pin to the hREA fork commit with the hdk 0.7.1 bump. #154 is closed by #130.

@Soushi888 Soushi888 closed this Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dual-dna Dual-DNA architecture - cross-DNA bridge calls and bundling hrea hREA integration - Holochain Resource-Event-Agent ValueFlows backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore(deps): move the hREA submodule to happ-0.5.0-beta.1

1 participant