Skip to content

chore(deps): upgrade to Holochain 0.7.1 - #130

Merged
Soushi888 merged 27 commits into
devfrom
chore/holochain-0.7
Nov 4, 2026
Merged

Soushi888 merged 27 commits into
devfrom
chore/holochain-0.7

Conversation

@Soushi888

@Soushi888 Soushi888 commented Aug 11, 2026 •

Copy link
Copy Markdown
Collaborator

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

Summary

This moves Nondominium from Holochain 0.6.1 to Holochain 0.7.1 (hdk 0.7.1, hdi 0.8.1, holochain 0.7.1, Holonix main-0.7 at the 0.7.1 revision, @holochain/client 0.21.1, @holochain/hc-spin 0.700.1). It also moves the hREA submodule off the 0.6 fork: vendor/hrea now points at Sensorica/hREA commit c4c44adb, which is the h-REA/hREA release happ-0.5.0-beta.1 plus one commit that changes only the hdk / hdi pins to 0.7.1 / 0.8.1. That pin bump is proposed upstream as h-REA/hREA#423, and the fork pin is retired once upstream releases it. This PR absorbs what was #169, because a Holochain 0.7 hREA DNA cannot build on the 0.6 shell alone.

What changes for people. Every DNA hash changes, so a 0.7 network is a new network and existing conductor data must be cleared. Nothing is migrated: the project has no production users, and the break costs nothing now. What the validation rules accept is meant to be unchanged, and an independent review found no port bug (verdict in the folds below). The only new behaviour is stricter validation inside hREA's own DNA, which comes with the release.

Why the fork pin. A Holochain 0.7.1 conductor cannot grant a signing capability to a DNA built on hdk 0.7.0, because 0.7.1 changed the capability grant entry that DNA's validation callback decodes. At the release as published, bun run e2e fails on its first test; with the two pins bumped it passes 23 of 23.

Changes

Toolchain. Workspace pins hdi =0.8.1, hdk =0.7.1, holochain =0.7.1 with test_utils. flake.lock moves holonix (main-0.7) to a6cdfbd3, which locks holochain-0.7.1 and kitsune2 0.5.2. JS side: @holochain/client ^0.21.1, @holochain/hc-spin ^0.700.1; the vendored hREA adapter (@valueflows/vf-graphql-holochain 0.700.0-rc.0, from #155) depends on ^0.21.0, which 0.21.1 satisfies. bun.lock was regenerated by bun install, not edited.

0.7.1 capability grants. hdk 0.7.1 removed ZomeCallCapGrant and the CapAccess::Assigned / Transferable grant variants. The two grant sites in zome_person (grant_private_data_access, create_transferable_private_data_access) now build a CapGrant::new_zome_call_grant with GrantConstraint::Assigned / Transferable. Tag, secret, assignees and function list are the same, so what a grant allows is unchanged.

Integrity zomes, the v2 action model. 0.7 removes the per-variant action structs; an Action is an ActionHeader plus an ActionData, and flat-op variants carry a TypedAction<D>. Across zome_person, zome_resource, zome_gouvernance, zome_group_integrity and zome_lobby_integrity: StoreEntry/StoreRecord become CreateEntry/CreateRecord; RegisterCreateLink/RegisterDeleteLink fold into FlatOp::Link(OpLink::*); EntryCreationAction becomes TypedAction<EntryCreationData>; the hash fields that sat on the flat-op variant are read from the action (deletes_address, original_action_address, link_add_address); action.author becomes action.author().

Coordinator zomes. post_commit signal dispatch matches on ActionData::*.

hREA. The submodule is Sensorica/hREA c4c44adb (.gitmodules url updated, vendor/README.md says what it is). It is the upstream release happ-0.5.0-beta.1 (79c8d4fb) plus the pin bump. The release ships real validation (required fields, quantity and date rules, an action whitelist), so the earlier "every validate_* is a TODO" description no longer holds; the Sweettest and e2e runs below were made against it.

Dev launcher and tests. scripts/launch-happ.mjs passes quic (0.7 drops WebRTC). await_consistency_20_s is gone; the existing waits go through await_consistency_s(timeout, cells) with the same timings. Tryorama has no 0.7-compatible release, so the deprecated tests/ suite cannot connect and tests/DEPRECATED.md says so.

Contributor trap. The flake shellHook runs git submodule update --init vendor/hrea on every nix develop, which discards an uncommitted checkout inside the submodule. CONTRIBUTING.md documents it.

Independent review of the validation diff

Reviewed by a fresh-context reviewer given the diff and the questions, not this PR's conclusions. It read the real hdi 0.7.0 and hdi 0.8.1 sources, holochain_integrity_types 0.6.0 and 0.7.1, and holochain 0.7.1. It did not compile or run anything.

  1. FlatOp renames: equivalent. Same variant sets per op; the dropped original_*_hash fields are still reachable from action. No op type that was validated now falls into a catch-all returning Valid; catch-all arms sit at the same places before and after.
  2. The four FlatOp::Link(OpLink::*) arms: equivalent. Base, target, tag and link type come from the same underlying CreateLink, and the delete arms read them from original_action, which is built from it.
  3. prev_action: None => Valid in hREA's CreateAgent arm: a behaviour change, unreachable. In 0.6 prev_action was non-optional, so the branch only satisfies the new Option type. If it were reached it would accept a CreateAgent with no predecessor without checking the membrane proof. It cannot be reached: sys validation (check_prev_action, holochain 0.7.1 sys_validate.rs:153-172) rejects any non-genesis action with no predecessor before app validation runs. Not traced: whether sys validation always completes before the app callback for this op. Optional hardening, in hREA upstream: return Invalid on None so it fails closed.
  4. deletes_address, original_action_address, link_add_address: equivalent at every call site in both diffs. Same hash type (ActionHash) and meaning. The try_into() narrowing keeps each call site's old reaction (person, resource and hREA return Invalid; gouvernance and lobby return Valid).
  5. Other semantic changes: none from the port. hREA beta.1 is stricter than the pre-port commit (for example rea_agent.rs now requires a non-blank name and an agent_type of Person or Organization). Nondominium's hrea_bridge.rs always sends Person. Not verified by the reviewer: whether a blank name can reach the bridge, and the 18 other hREA integrity files (only skimmed). The Sweettest and e2e runs exercise the bridge and passed.

Blocking findings: none for the port.

Decisions
Option Rejected because
Hold hREA on 0.6 and ship only the Nondominium-side port The hREA DNA is a role in this hApp and runs in the same 0.7 conductor. A 0.6-built wasm will not load.
Widen the preserved 20s/10s consistency waits to the 60s default A behaviour change hidden in a dependency bump. await_consistency_s keeps the timings; retuning them is separate.
Attempt data migration via init properties The mechanism exists but its DX is incomplete and Nondominium has no production users. Every 0.7 network is a new network.
Pin the unmodified upstream tag Its DNA cannot be granted a signing capability by a 0.7.1 conductor (see Summary). Staying on Holochain 0.7.0 until upstream releases the bump was the other way out, and was not chosen.
Fork commit that changes only the two pins Chosen. The change is two lines and a regenerated lockfile, proposed upstream as h-REA/hREA#423, and the pin is retired once upstream releases it.
How to test
git submodule update --init --recursive
nix develop                      # holochain 0.7.1
bun install
(cd packages/shared-types && bun run build)   # the UI resolves its types from the gitignored dist/
bun run build:happ               # builds all zomes and hREA, packs 5 DNAs and the happ

CARGO_TARGET_DIR=target/native-tests cargo test -p nondominium_sweettest -- --test-threads 6
CARGO_TARGET_DIR=target/native-tests cargo test -p group_sweettest -- --test-threads 6
CARGO_TARGET_DIR=target/native-tests cargo test -p lobby_sweettest -- --test-threads 6

bun run --filter ui check
bun run e2e                      # needs: cd ui && bunx playwright install chromium-headless-shell chromium

Clear old conductor data first (hc sandbox clean, and remove /tmp/ndo-e2e). 0.7 cannot read 0.6 databases and the failure is a confusing startup error.

What was verified locally, inside nix develop

Check Result
bun run build:happ exit 0, 5 DNAs and workdir/nondominium.happ, hREA built from the fork pin
cargo test -p nondominium_sweettest -- --test-threads 6 44 passed, 0 failed, 2 ignored (already #[ignore] on dev)
cargo test -p group_sweettest -- --test-threads 6 24 passed, 0 failed
cargo test -p lobby_sweettest -- --test-threads 6 5 passed, 0 failed
bun run --filter ui check 0 errors, 2 warnings (LifecycleTransitionModal.svelte, state_referenced_locally)
bun run e2e (23 specs, real conductors) 23 passed in 2.8 min
hc dna hash of the rebuilt hrea.dna the same value on two separate builds (uhC0kqRm...)
Documentation
  • .rules (read as CLAUDE.md, AGENTS.md, GEMINI.md), README.md, CHANGELOG.md, documentation/IMPLEMENTATION_STATUS.md, ARCHITECTURE_COMPONENTS.md, DOCUMENTATION_INDEX.md, Testing_Infrastructure.md, specifications/ui_architecture.md: exact pins and client version.
  • documentation/zomes/architecture_overview.md, documentation/hREA/integration-strategy.md, tests/DEPRECATED.md, CONTRIBUTING.md: earlier commits of this PR (0.7 notes, submodule trap, Tryorama).

Related

Closes #134
Closes #154

Pre-open review

  • Description: Summary stands alone; folds carry detail; disclosure line first; closing keywords outside the folds. Pass.
  • Merge state: based on current dev, no conflict (git rev-list HEAD..origin/dev is 0). chore(deps): move the hREA submodule to happ-0.5.0-beta.1 #169 folded in. Pass.
  • Code findings: independent review above, no blocker for the port; the one runtime issue found since (hREA built on hdk 0.7.0 under a 0.7.1 conductor) is fixed by the pin and covered by e2e. Pass.
  • Documentation: pins, hREA source and the submodule trap updated, listed above. Pass.
  • Tests: counts above, all local runs green and CI as reported on the PR. Pass.

Pin holonix to main-0.7 and the workspace to hdk =0.7.0 / hdi =0.8.0 /
holochain =0.7.0.

The 0.7 action model replaces the per-variant action structs with
ActionHeader + ActionData, so the integrity zomes move to TypedAction:

- FlatOp variants renamed: StoreEntry -> CreateEntry, StoreRecord ->
  CreateRecord.
- EntryCreationAction is gone; narrowing a fetched Action now goes through
  TypedAction<EntryCreationData>::try_from.
- OpRecord::DeleteEntry no longer carries original_action_hash; read
  action.deletes_address. Same for UpdateEntry ->
  action.original_action_address.
- action.author is now the accessor action.author(); Create/Update
  parameter types become TypedAction<CreateData> / TypedAction<UpdateData>.
- Coordinator post_commit handlers match on action.hashed.content.data
  (ActionData) instead of the removed Action::* variants.

Validation logic is unchanged: every check reads the same value from its
new location.
- @holochain/client ^0.21.0 (root, ui, tests); @holochain/hc-spin ^0.700.0.
- scripts/launch-happ.mjs: 0.7 removed the WebRTC/tx5 transport, so
  `hc sandbox create network` now takes `quic` instead of `webrtc <signalUrl>`.
- Version references across CLAUDE.md, README.md and documentation/ updated to
  HDK 0.7 / HDI 0.8 / holochain 0.7 / client 0.21.
- Tryorama has no 0.7-compatible release; tests/DEPRECATED.md and the testing
  stack table now say the legacy suite cannot run against a 0.7 conductor.
@holochain/client 0.21 narrows AppWebsocket.client to the AppClientTransport
interface (request/on only), so the e2e harness feature-detects close()
instead of calling it on the concrete WsClient. shared-types peerDependency
moves to ^0.21.0.

svelte-check: 0 errors, 0 warnings.
- await_consistency_20_s is gone. 0.7 has await_consistency(cells) with a
  hard 60s timeout and await_consistency_s(timeout, cells) as the
  configurable form; existing 20s and 10s waits are preserved via the latter
  rather than silently widened to 60s.
- SweetConductorBatch no longer derefs mutably or exposes iter_mut, but does
  implement IndexMut, so the NDO cell setup indexes the batch directly.

All three suites (nondominium, group, lobby) compile against
holochain =0.7.0 with test_utils.
The vendored hREA DNA ships as a role in this hApp and runs in the same 0.7
conductor, so a 0.6-built wasm will not load. Upstream h-REA has no main-0.7
branch, so the Sensorica fork carries the port on chore/holochain-0.7.

Note the flake's shellHook runs `git submodule update --init vendor/hrea` on
every `nix develop`; without this pointer commit that reset the submodule back
to the 0.6 commit.
The flake shellHook runs `git submodule update --init vendor/hrea` on every
`nix develop`, which silently discards an uncommitted branch checkout inside
the submodule. Hit during the 0.7 port.
@Soushi888

Copy link
Copy Markdown
Collaborator Author

Author self-check on the highest-risk item (not an independent review)

Item 2 in "What is still missing" asks whether the replaced original_action_hash reads are
actually equivalent. I checked this myself against the hdi 0.7.1 source (the 0.6 line) versus
hdi 0.8.0. This is the author checking his own diff, so it does not discharge the need for a
second pair of eyes
— but it does mean a reviewer can start from a narrower question.

Where 0.6 populated each field, from hdi-0.7.1/src/op.rs:

0.6 flat-op field fed from this PR now reads equivalent
OpRecord::DeleteEntry.original_action_hash deletes_address.clone() (line 209) action.deletes_address yes
OpRecord::UpdateEntry.original_action_hash Update.original_action_address, renamed on destructure (lines 158/175) action.original_action_address yes
OpRecord::DeleteLink.original_action_hash link_add_address.clone() (line 94) action.link_add_address yes

Narrowing failure branches. Every site that swapped a hand-written
Action::Create(..) | Action::Update(..) match for TryInto<TypedAction<EntryCreationData>>
keeps its original verdict. try_into fails on exactly the same set the old _ arm caught
(anything that is neither Create nor Update), so the arms are semantically identical:

  • zome_resource DeleteEntry: Invalid → Invalid (same message)
  • zome_person DeleteEntry: Invalid → Invalid (same message)
  • zome_gouvernance DeleteEntry / UpdateEntry: Valid → Valid
  • zome_lobby_integrity UpdateEntry: Valid → Valid
  • hREA UpdateEntry / DeleteEntry / DeleteLink: Invalid → Invalid (same messages)

No branch flipped Invalid to Valid.

One genuinely new branch, worth a reviewer's eye. In hREA's OpActivity::CreateAgent arm,
0.6 read action.prev_action as a plain ActionHash; in 0.7 ActionHeader.prev_action is
Option<ActionHash> (None only for the genesis Dna action). I added
None => return Ok(ValidateCallbackResult::Valid). A CreateAgent op always follows an
AgentValidationPkg, so that arm should be unreachable in practice, but it is the one place in
this diff where I wrote a new decision rather than relocating an existing one.

Still unreviewed by anyone but me: the FlatOp variant renames (whether each new variant is
the same authority as the old one it replaced) and the four link-arm restructurings into
FlatOp::Link(OpLink::*), where base_address / target_address / tag are now bound from the
typed action at the top of the arm.

Soushi888 added a commit that referenced this pull request Aug 16, 2026
…can write (#138)

rsync -a preserves the read-only mode of nix store paths, so after the
first materialization .claude/ was mode 555 and the agent-skills hook
could not mkdir .claude/skills/holochain. Every nix shell entry and every
CI job logged 'rsync: mkdir failed: Permission denied (13)' three times.

Non-fatal but noisy, and a red herring when diagnosing real e2e failures:
in PR #130's failing run the error appears immediately before the launcher
timeout, though the two are unrelated.

.cursor/ already had this exact chmod; .claude/ was missing it.
Soushi888 added a commit that referenced this pull request Sep 8, 2026
The input was unpinned and the lock held ab02c4f from 2026-04-06, which
predates every tagged release of the upstream repository. Two upstream
breaking changes had to be absorbed to move it forward:

- The repository was renamed to holochain-agent-skills (plural). The input
  attribute stays singular so `nix flake update holochain-agent-skill` and
  the references in CONTRIBUTING.md and pai/README.md keep working.
- The skill moved from the repository root to skills/holochain/. Fetching
  the root used to drag book.toml, SUMMARY.md, CHANGELOG.md, docs/ and
  .github/ into the installed skill; the src now names the subpath.

v1.0.0-rc.1 targets Holochain 0.7 only, while dev is still on hdk 0.6 /
holonix main-0.6. The 0.6-compatible release is v0.2.0. Pinning the
candidate here is deliberate: it lands the skill ahead of the 0.7 upgrade
in #130 rather than after it.
@Soushi888 Soushi888 added this to the v0.1.0 peer-mesh milestone Oct 9, 2026
Commit the @valueflows/vf-graphql-holochain 0.700.0-rc.0 tarball built from h-REA/hREA tag happ-0.5.0-beta.1 (79c8d4fb) under vendor/, beside the hrea submodule, with its sha256 and a README recording source commit, rebuild steps and how to drop it once npm serves 0.700. The UI installs it through a file: dependency; bun.lock regenerated by bun install.

The adapter brings its own @holochain/client ^0.21, installed nested; the UI keeps ^0.20 until the Holochain 0.7 layer.

Closes #153
… stream

Building inside a full hREA checkout fails under npm 11 (EUNSUPPORTEDPROTOCOL on
the workspace link: dependency), so the recipe now extracts the module with git
archive. A rebuild reproduces the tar stream, not the gzip layer, so the README
records the tar stream sha256 and points at h-REA/hREA#421 for the pack script.
The integration strategy said hREA integration bypasses GraphQL entirely,
while this branch vendors the GraphQL adapter into the UI. State the bound:
the adapter serves read-only queries, and every write stays zome-level so
governance evaluation and PPR issuance cannot be skipped.
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
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
…t API

hdk 0.7.1 replaced ZomeCallCapGrant and the CapAccess grant variants with
CapGrant::new_zome_call_grant and GrantConstraint. Both grant sites keep
the same tag, secret, assignees and function list, so what a grant
allows is unchanged.
Workspace pins hdk =0.7.1, hdi =0.8.1 and holochain =0.7.1. Holonix
main-0.7 is updated to the 0.7.1 revision, and the JS side moves to
@holochain/client ^0.21.1 and @holochain/hc-spin ^0.700.1. Docs that
named the exact pins follow.

Refs #130
@Soushi888
Soushi888 changed the base branch from dev to chore/154-hrea-beta1 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 added this pull request to stack #176 November 3, 2026 23:34
@Soushi888 Soushi888 added dual-dna Dual-DNA architecture - cross-DNA bridge calls and bundling frontend Frontend development - UI, SvelteKit, Effect-TS hrea hREA integration - Holochain Resource-Event-Agent ValueFlows backend testing Test infrastructure, scenarios, integration tests labels Nov 3, 2026
@Soushi888 Soushi888 changed the title chore(deps): upgrade to Holochain 0.7 chore(deps): upgrade to Holochain 0.7.1 Nov 3, 2026
@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 (full text in the body, section "Waiting on Soushi").

Blocker. The hREA DNA at the happ-0.5.0-beta.1 tag is built with hdk 0.7.0 / hdi 0.8.0. A Holochain 0.7.1 conductor cannot grant it a signing capability: authorizeSigningCredentials fails with The callback has invalid parameters, because 0.7.1 changed the capability grant entry (CapGrant { tag, constraint, capability }) that the hREA validation callback decodes. Evidence: bun run e2e at the tag as pinned fails on the first test (1 failed, 1 failed in the multi-agent spec, 21 did not run); with vendor/hrea/Cargo.toml locally changed to hdi =0.8.1 / hdk =0.7.1 (not committed), the same suite passes 23/23 in 2.4 min. Choices, all Soushi's: a fork commit on the tag that changes only those two pins; a 0.7.1 release from h-REA and, meanwhile, staying on 0.7.0; or a build step that rewrites the pins.

Independent review of the validation diff, verdict: no blocker for the port. Reviewer was a fresh-context agent given the diff and five questions. It read hdi 0.7.0 and 0.8.1, holochain_integrity_types 0.6.0 and 0.7.1 and holochain 0.7.1 sources, and ran nothing.

  • FlatOp renames and the four OpLink arms: equivalent.
  • deletes_address, original_action_address, link_add_address: equivalent at every call site.
  • prev_action: None => Valid in hREA's CreateAgent arm: a behaviour change but unreachable, since sys validation rejects a non-genesis action without a predecessor first (sys_validate.rs:153-172). Optional hardening upstream: return Invalid.
  • Not verified by the reviewer: that sys validation always completes before the app callback for this op, whether a blank Person name can reach hREA's new rea_agent rule (the bridge always sends Person; Sweettest and e2e exercise it), and 18 other hREA integrity files.

Also found on the way. hdk 0.7.1 is not a drop-in patch bump: ZomeCallCapGrant and CapAccess::Assigned / Transferable are gone. The two grant sites in zome_person moved to CapGrant::new_zome_call_grant with the same tag, secret, assignees and functions (commit 5534309).

Local results, inside nix develop: build:happ passes; Sweettest 44 + 24 + 5 = 73 passed, 0 failed, 2 ignored (already ignored on dev); ui check 0 errors, 2 warnings.

vendor/hrea now points at Sensorica/hREA c4c44adb: the release commit
79c8d4fb with only the hdk =0.7.1 / hdi =0.8.1 pins and the lockfile
changed. A DNA built on hdk 0.7.0 cannot be granted a signing capability
by a Holochain 0.7.1 conductor. Retired once upstream releases the bump.

Refs #130
@Soushi888

Copy link
Copy Markdown
Collaborator Author

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

Review APPROVE at head 15ad9a5, merging under Soushi's explicit -mwr authorisation (2026-11-03 21:42). Bottom of native stack #179.

  • Scope matches the body: toolchain pins to Holochain 0.7.1, the v2 action model port across the five integrity zomes, the capability grant sites in zome_person, hREA submodule on the Sensorica/hREA fork pin, launcher and test updates, and the docs the body lists. The body's independent validation review found no port bug; the one runtime issue found afterwards (hREA built on hdk 0.7.0 under a 0.7.1 conductor) is fixed by the fork pin and covered by e2e.
  • CI at this head: build, rustfmt, all six Sweettest shards and e2e are SUCCESS. Branch is mergeable and clean against dev after ci(tests): run the group and lobby Sweettest suites #170 landed; this PR does not touch build.yml, so there was no conflict to resolve.
  • Not covered by this head's CI: the group and lobby Sweettest shards added by ci(tests): run the group and lobby Sweettest suites #170 (this head predates them). The body reports them green locally on 0.7.1 (24 and 5 passed). They run on dev from the next push.
  • Follow-up: .gitmodules now points vendor/hrea at the fork until chore(deps): bump hdk 0.7.1 / hdi 0.8.1 for Holochain 0.7.1 h-REA/hREA#423 is released, as the body states. docs: publish the Holochain 0.7.1 DNA hashes #178 retargets to dev next.

@Soushi888
Soushi888 merged commit 4d0e830 into dev Nov 4, 2026
9 checks passed
@Soushi888
Soushi888 deleted the chore/holochain-0.7 branch November 4, 2026 02:45
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 frontend Frontend development - UI, SvelteKit, Effect-TS hrea hREA integration - Holochain Resource-Event-Agent ValueFlows backend testing Test infrastructure, scenarios, integration tests

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 chore(deps): upgrade Nondominium to Holochain 0.7.1 and hREA happ-0.5.0-beta.1

1 participant