Repository navigation
Conversation
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
Staying a draft, one blocker: the Build check cannot go green on this layer alone. The pinned hREA DNA ( |
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. |
Summary
Nondominium's
hreaDNA is built from thevendor/hreasubmodule. Until now it trackedmain-0.6on a Sensorica fork over SSH. This PR points it at the upstream release instead:https://github.com/h-REA/hREA.git, pinned to commit79c8d4fb98c4f7f9a8cf3f7dd69690d6d1334d85, the commit under the annotated taghapp-0.5.0-beta.1(the tag object is244da223bf4b6e1288828c23bc284f0df0f6ce06). 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-holochain0.700.0-rc.0) is the one the release documents for this tag.Changes
.gitmodulesuses the public https URL and drops thebranch = main-0.6line, since the pin is a tag and not a branch to follow.vendor/hreamoves fromfc3b5e78to79c8d4fb.vendor/README.md,documentation/IMPLEMENTATION_STATUS.mdanddocumentation/hREA/integration-strategy.mdname 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
79c8d4fb), and the docs name both the tag and that commit.docs/consuming-a-release.mdasks for@holochain/client ^0.21.0, a 0.7.x conductor, the adapter on the 0.700 line, theTypedAction<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 --tagsprintshapp-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.mdanddocumentation/hREA/integration-strategy.mdto name the release tag and commit.Related
Closes #154
Pre-open review
Closes #154, disclosure line first. Pass.origin/dev(7faf650); the three commits of chore(deps): vendor the hREA GraphQL adapter 0.700.0-rc.0 into the UI #155 already indevwere dropped, one conflict indocumentation/hREA/integration-strategy.mdresolved by keeping both the adapter bound paragraph and the new repository line. Pass.git ls-remoteon h-REA/hREA: tag object244da223, peeled79c8d4fb). Pass.