Skip to content

ARSN-659: Fix remaining CVEs in tests/workflows and release 8.6.0 - #2731

Merged
bert-e merged 5 commits into
development/8.6from
improvement/ARSN-659
Oct 14, 2026
Merged

bert-e merged 5 commits into
development/8.6from
improvement/ARSN-659

Conversation

@francoisferrand

@francoisferrand francoisferrand commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Last cleanup before cutting 8.6.0: clear the security advisories we can fix, then bump the version.

The workflow test tooling had picked up several vulnerable dependencies, mostly through @kie/act-js and @kie/mock-github, which haven't had a fixed release. Most of them are fixed now. simple-git is still flagged: its fix needs a major version that mock-github doesn't support yet. That only matters for our own CI tests.

On the library side, the lockfile is refreshed to pick up fixed transitive versions. OpenTelemetry is bumped as a whole family, so we no longer ship two copies of its core packages. Dependabot now groups those updates so they keep moving together.

What's still flagged (braces, sprintf-js, katex) is dev tooling only, and either has no fix upstream or would need a breaking upgrade.

Once merged, 8.6.0 can be released from development/8.6.

Issue: ARSN-659

The workflow test tooling had picked up a vulnerable handlebars (via
ts-jest) and a few stale transitive deps. Regenerate the lockfile so
everything sits on the latest compatible versions, and move the
@types/node floor to the current 24.x.

Issue: ARSN-659
@kie/act-js still asks for adm-zip ^0.5, which carries several
path-traversal and symlink advisories with no fix in that line, and
there is no newer act-js release. Resolve it to 0.6.x, which keeps the
API act-js uses, alongside the existing tar override.

simple-git (via @kie/mock-github) stays on 3.x: the fixes are only in
4.x, which drops the default export mock-github relies on.

Issue: ARSN-659
Pick up the latest compatible transitive versions before releasing.
This clears the handlebars advisories and moves http-cache-semantics
(pulled in by node-gyp through fcntl) off 4.2.0, flagged by
GHSA-ch52-4w7c-c8xp.

Issue: ARSN-659
@bert-e

bert-e commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Hello francoisferrand,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval ⭐
/bypass_build_status Bypass the build and test status ⭐
/bypass_commit_size Bypass the check on the size of the changeset TBA ⭐
/bypass_incompatible_branch Bypass the check on the source branch prefix ⭐
/bypass_jira_check Bypass the Jira issue check ⭐
/bypass_peer_approval Bypass the pull request peers' approval ⭐
/bypass_leader_approval Bypass the pull request leaders' approval ⭐
/bypass_source_branch_lineage Bypass the cross-branch contamination check ⭐
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request.
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

sdk-node and the OTLP exporters pin the 2.x core packages exactly, so
whenever our 2.x ranges resolve ahead of what sdk-node pins, yarn ends
up with two copies of core/resources/sdk-trace-base. Move the whole
family to 0.223.0 / 2.12.0, which line up again, and group the
OpenTelemetry updates in Dependabot so they keep moving in lockstep.
Ranges stay as carets so consumers can still dedupe.

Issue: ARSN-659
@francoisferrand
francoisferrand marked this pull request as ready for review October 13, 2026 20:18
@codecov

codecov Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.39%. Comparing base (e801521) to head (765bda8).
⚠️ Report is 5 commits behind head on development/8.6.

Additional details and impacted files
@@                 Coverage Diff                 @@
##           development/8.6    #2731      +/-   ##
===================================================
+ Coverage            75.38%   75.39%   +0.01%     
===================================================
  Files                  226      226              
  Lines                18633    18633              
  Branches              3863     3895      +32     
===================================================
+ Hits                 14046    14048       +2     
+ Misses                4582     4580       -2     
  Partials                 5        5              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@scality scality deleted a comment from bert-e Oct 14, 2026
@scality scality deleted a comment from bert-e Oct 14, 2026
@bert-e

bert-e commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

@francoisferrand

Copy link
Copy Markdown
Contributor Author

/approve

@bert-e

bert-e commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/8.6

The following branches have NOT changed:

  • development/6.4
  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.1
  • development/8.2
  • development/8.3
  • development/8.4
  • development/8.5

This pull request did not target the following hotfix branch(es) so they
were left untouched:

  • hotfix/7.70.20
  • hotfix/7.4.10
  • hotfix/7.4.8
  • hotfix/7.7.0
  • hotfix/7.5.0
  • hotfix/7.10.43
  • hotfix/7.4.7
  • hotfix/7.10.29
  • hotfix/7.10.2
  • hotfix/7.70.14
  • hotfix/7.9.0
  • hotfix/7.10.31
  • hotfix/7.10.57
  • hotfix/7.8.0
  • hotfix/7.70.4
  • hotfix/7.10.46
  • hotfix/7.10.36
  • hotfix/6.4.7
  • hotfix/7.4.3
  • hotfix/7.10.4
  • hotfix/7.2.0
  • hotfix/7.4.9
  • hotfix/8.2.48
  • hotfix/7.10.47
  • hotfix/7.4.2
  • hotfix/7.6.0
  • hotfix/7.10.3
  • hotfix/7.4.1
  • hotfix/7.4.0
  • hotfix/7.10.0
  • hotfix/7.4.4
  • hotfix/7.4.6
  • hotfix/7.10.1
  • hotfix/7.70.25
  • hotfix/7.4.5

Please check the status of the associated issue ARSN-659.

Goodbye francoisferrand.

The following options are set: approve

@bert-e
bert-e merged commit 765bda8 into development/8.6 Oct 14, 2026
16 checks passed
@bert-e
bert-e deleted the improvement/ARSN-659 branch October 14, 2026 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants