Repository navigation
chore(release): prepare dhttp v0.7.0 - #33
Merged
Merged
Conversation
This was referenced Oct 12, 2026
metah3m
force-pushed
the
feat/release-dhttp-0.7.0
branch
from
October 12, 2026 06:20
ac2b54b to
e6237dc
Compare
Restore high-level clients and handler servers through N-API and PyO3 using shared bounded streams, trusted identity metadata and cancellation ownership. Add explicit profile loading/reload and preserve core error categories across Body and I/O boundaries. Validated Rust workspace and real QUIC tests, installed npm/wheel tests with independent language servers, TypeScript declarations and binding Clippy checks. Default H3 DNS/mDNS, name publication and multi-platform releases remain follow-up work.
Prepare dhttp 0.7.0, supporting crates and Node/Python SDK versions. Replace Git pins with compatible registry dependencies and update publication order. Refresh registry lockfiles after upstream releases.
Keep seven internal design and API drafts local and ignored. Update README and SDK links. Checked file preservation, ignore rules, documentation links and whitespace.
Require release tags to match the package version before publication. Keep the existing dependency-ordered release flow. Workflow syntax and matching/mismatched tag checks passed.
metah3m
force-pushed
the
feat/release-dhttp-0.7.0
branch
from
October 12, 2026 07:28
67cc5ec to
3306c28
Compare
metah3m
marked this pull request as ready for review
October 12, 2026 08:54
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
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.
Summary
This release exposes the network, identity and request APIs needed for applications such as gmutils to use DHTTP directly.
Endpointand anonymous requests separate, with standard HTTP bodies, native HTTP/3 streaming uploads and trailers.DhttpNetwork::active_bindings(); DHTTP owns interface watching and live transport bindings, while discovery libraries consume snapshots.expand_uri_with_baseimplementation for early validation/display and public trust helpers for certificate verification.managefeature for default identity settings, candidate discovery and recoverable certificate/key installation on the existing home/profile model.ocspfeature for bounded refresh, validation and caching. DHTTP'sonline-identityfeature provides explicitEndpoint::load_from_with_ocsp();load_from()remains local-only.These APIs support gmutils' removal of its intermediary networking crate and dyns' snapshot-driven discovery maintenance.
Release
Planned tag:
v0.7.0. Compatible 0.x requirements and publication steps are documented inRELEASING.md.dhttpdhttp-homedhttp-accessdhttp-log@genmeta/dhttp / dhttpyPrerequisites: dquic v0.8.0 and h3x v0.7.0. Publish dhttp-home, dhttp-access and dhttp-log before dhttp. The SDK bridge remains
publish = false.Verification
Validated against temporary local prerequisite overrides:
online-identity,log: 64 passed.-D warnings: passed.Normal registry CI, the complete release matrix and publish dry run still require upstream publication and registry lockfile regeneration outside ancestor overrides. Local integration lockfiles were not committed; merge/tag only after the normal locked checks pass.