Harden Host-Tools for the 2.6 release - #17
Conversation
Prevent stale release metadata and partial overwrites from reaching artifacts. Tighten host command handling and driver lifecycle behavior, with regression coverage and release documentation.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1d51c8fc2a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
What
Why
The published v2.5 archive carried 2.4 version strings because the tag changed only the archive filename. A clean test run also exposed an ARM64 native-compiler selection problem and a recursive MHI package-directory collision. The runtime review found additional data-integrity, timeout, and driver-lifecycle edge cases worth resolving before the next release.
Root cause
Release metadata was duplicated and never checked against staged artifacts. Native-test selection assumed x86-64, recursive make inherited a generic package variable, and several host bridges treated asynchronous operations as if they completed synchronously.
Impact
This is release hardening with two intentional input changes: host-download accepts HTTP, HTTPS, FTP, and FTPS only, and host-env values must be single-line. Existing download destinations remain untouched until a successful replacement is ready. No installer destinations or component choices change.
Checks