fix(example): compile the release consumer from the registry - #25
Merged
Conversation
The release guide requires verifying every release with a clean consumer that installs exact versions from the registry and compiles. The example currently fails that check: - package-tour.ts imports @codesoul-co/hypha-serving-cache and @codesoul-co/hypha-testing, but the manifest only declares domain and kernel; - three map callbacks rely on implicit any under the strict tsconfig. Declare the full 15-package release line and annotate the callbacks.
erwinmsmith
added a commit
to erwinmsmith/THETA-Agent
that referenced
this pull request
Aug 14, 2026
Hypha is no longer a local third_party checkout. THETA-Agent now depends on the published @codesoul-co/hypha-* npm release line (1.0.1) exactly as Hypha's official release guidance prescribes; THETA remains the single third_party upstream checkout. - manifests: replace all file:third_party/Hypha dependencies with @codesoul-co/hypha-*@1.0.1 and drop the hypha:install/hypha:build steps - imports: rename every @hypha/* import across agent, tools, domain to the published package names - skills: load Hypha built-in skills from the shipped resolveBuiltinSkillsDirectory() data of @codesoul-co/hypha-skills instead of a source checkout - doctor: replace hypha.lock/hypha.build checks with hypha.packages, which verifies the installed release line, package entries, and shipped built-ins - upstreams: config/upstreams.lock.json now pins only THETA - tooling: allow better-sqlite3 postinstall for pnpm; update repository validation, README, architecture and CLI docs accordingly Hypha-side fixes released upstream and consumed here: - CodeSoul-co/Hypha#22 ships built-in skills in the hypha-skills tarball - CodeSoul-co/Hypha#23 resolves the npm audit failures - CodeSoul-co/Hypha#24 prepares and publishes @codesoul-co/hypha-* 1.0.1 - CodeSoul-co/Hypha#25 makes the official consumer example compile from the registry Verified: build, test:registries, test:providers, test:docs, test:python, validate, doctor, governed demo, REPL, and the HTTP API all pass without a Hypha checkout.
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
1 participant
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.
Problem
docs/guides/releases.mdrequires verifying each release with a clean temporary consumer that installs exact versions from the registry, compiles, and runs tests. Doing that withexamples/release-agentfails today:package-tour.tsimports@codesoul-co/hypha-serving-cacheand@codesoul-co/hypha-testing, but the example manifest only declareshypha-domainandhypha-kernel;mapcallbacks rely on implicitanyunder the example's strict tsconfig.Change
@codesoul-co/hypha-*1.0.1 release line in the example manifest.package-tour.ts.Verification (clean consumer from the registry)