DAPPS bundle → v0.34.0: manifest fetched from the release, zero-config enable - #382
Merged
Conversation
…ease The interim packaging/dapps/pdn-app.yaml is deleted: v0.34.0 is the first dapps release shipping its own manifest as an asset, so build-deb now fetches manifest + binary from the same release (four sha256 pins, version-keyed cache, all-or-nothing staging, same hard-fail/skip semantics — all four paths proven). ShippedManifestsTests read the cached release manifest via SkippableFacts whose path derives from the script's own pin (no drift possible); the catalog test splits so wall/lobby coverage survives cache-less environments. The release carries DAPPS_ENV_MANAGED + the node-derived callsign with SSID probe-walk — enabling dapps on a pdn node is now zero-config. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
m0lte/dapps v0.34.0 is the first release to ship
pdn-app.yamlas a release asset (packet-net/dapps#149), so this completes the 5b design: the interim manifest copy inpackaging/dapps/is deleted, andbuild-deb.shfetches manifest + binary from the same release — four sha256 pins (three RID binaries + the RID-independent manifest), a version-keyed cache, and all-or-nothing staging (never a binary without its manifest). Failure semantics unchanged and re-proven: fresh-download pin mismatch hard-fails; unreachable release with no cache warns and skips the whole package.ShippedManifestsTestsnow read the cached release manifest viaSkippableFacts whose cache path is derived from the script's own version pin — the tests cannot drift from the script. New assertion: the manifest setsDAPPS_ENV_MANAGED: "true"(the opt-in deployment-managed config mode). The catalog-layout test splits so wall/lobby coverage runs unconditionally in cache-less environments.What v0.34.0 brings to the bundle: enabling DAPPS on a pdn node is now zero-config — it derives
<nodecall>-7from the supervisor-injectedPDN_NODE_CALLSIGN(PR #381), probe-walking to a free SSID via the node's deterministic duplicate-refusal (deviation D5) if 7 is taken.729/729 Node tests; deb 73.3 MB with
/usr/share/packetnet/apps/dapps/{dapps,pdn-app.yaml}verified staged at v0.34.0. plan.md §17 updated.🤖 Generated with Claude Code