Skip to content

build(deps): bump @neuralegion/os-service to ^2.0.7 (@xmldom/xmldom 0.9.x) - #789

Merged
aborovsky merged 4 commits into
nextfrom
chore/sec-bump-os-service
Oct 7, 2026
Merged

aborovsky merged 4 commits into
nextfrom
chore/sec-bump-os-service

Conversation

@aborovsky

@aborovsky aborovsky commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

No description provided.

@aborovsky aborovsky self-assigned this Oct 5, 2026
@aborovsky

aborovsky commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor Author

Bumps @neuralegion/os-service ^2.0.6 → ^2.0.7.

The new @neuralegion/os-service@2.0.7 bumps its own plist dependency to
^3.1.1, which moves @xmldom/xmldom from the vulnerable 0.8.x line to the
0.9.x line. The bright-cli tree now resolves a single @xmldom/xmldom@0.9.12
(was 0.8.13), outside every flagged advisory range.

Upstream fix: BrightSec/node-os-service#83 (released as @neuralegion/os-service@2.0.7).

Verification

  • Single @xmldom/xmldom@0.9.12 copy in the tree; no vulnerable copy remains.
  • npm run build (webpack, production) succeeds.
  • npm run test:unit → 222 passed. (The one native-addon resolution error
    seen locally is from installing with --ignore-scripts, i.e. no prebuilt
    @brightsec/node-libcurl binary — not a regression; CI installs it normally.)
  • To be gated on the e2e.yml workflow for this branch before marking ready.

@aborovsky aborovsky added the dependencies Pull requests that update a dependency file label Oct 6, 2026
@neuralegion/os-service 2.0.7 bumps its plist dependency to ^3.1.1, which
moves @xmldom/xmldom off the vulnerable 0.8.x line to 0.9.12. Bumping it
here replaces the single @xmldom/xmldom copy in the tree with 0.9.12 and
clears all 10 @xmldom/xmldom alerts.

Production webpack build and all 222 unit tests pass.
…Packages

The lockfile recorded @neuralegion/os-service@2.0.7 with a GitHub Packages
resolved URL (npm.pkg.github.com), because it was regenerated in an
environment whose .npmrc maps the @NeuraLegion scope to GHP. In CI, npm ci
fetches that exact URL and 401s (no GHP token on the e2e runners), unlike
every other dependency which resolves from registry.npmjs.org.

os-service@2.0.7 is published to public npm too (same integrity), so point
the resolved URL there to match @neuralegion/raw-socket and the rest of the
tree. Verified: npm ci now succeeds with a token-less public-npm config.
@aborovsky
aborovsky force-pushed the chore/sec-bump-os-service branch from 1f5b091 to d81e2da Compare October 6, 2026 10:37
@derevnjuk

Copy link
Copy Markdown
Member

build not fix #793 (comment)

@aborovsky aborovsky changed the title fix(deps): bump @neuralegion/os-service to ^2.0.7 (@xmldom/xmldom 0.9.x) build(deps): bump @neuralegion/os-service to ^2.0.7 (@xmldom/xmldom 0.9.x) Oct 7, 2026
@aborovsky
aborovsky requested a review from YarikMamykin October 7, 2026 13:56
@aborovsky
aborovsky marked this pull request as ready for review October 7, 2026 13:56
@aborovsky
aborovsky enabled auto-merge (squash) October 7, 2026 13:57
@aborovsky
aborovsky merged commit 6a14a9f into next Oct 7, 2026
30 checks passed
@aborovsky
aborovsky deleted the chore/sec-bump-os-service branch October 7, 2026 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants