Repository navigation
Qualify Node 24 agent packages and preserve legacy state - #24
Merged
spenceralbrecht merged 18 commits intoOct 27, 2026
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
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.
Modern Node 24 agent bundles need native package ownership that preserves an existing installation's configuration and service state. This adds deterministic Debian and Chocolatey package assembly, guarded package hooks, and transactional migration/cleanup for the two retained legacy package families. Unknown Windows shims stay unowned and preserved.
Qualification uses isolated Linux systemd/BPF controls and Windows native package-manager tests to exercise upgrade, crash compensation, reporting, uninstall and cleanup. Run identifiers, versions and Windows cleanup commands use bounded, fixed protocols; the Windows helper model no longer rereads its own source file.
Validation at
47c5d8a7359b13472de3cf49e559870fe065303a: both push and PR source/native matrices pass on Linux and Windows. CodeQL and all three language analyses pass. Five operator-selected CLI path findings were individually reviewed and recorded as false positives with reopening conditions; scanning remains enabled. The inconsistent historical Linux upgrade byte-size field is excluded from qualification.This merges package preparation and qualification only. No binary is published, no legacy
v*release tag is created, and no customer agent is upgraded. Final retained release bytes, fresh-enrollment compatibility, post-success Windows recovery, supported customer OS and actual fleet adoption remain separate acceptance work.