Skip to content

Chores: bump dependencies - #2542

Merged
bert-e merged 12 commits into
development/2.16from
improvement/ZENKO-5364
Sep 22, 2026
Merged

bert-e merged 12 commits into
development/2.16from
improvement/ZENKO-5364

Conversation

@SylvainSenechal

@SylvainSenechal SylvainSenechal commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

ISSUE: ZENKO-5364

!! : The diff is small, mostly YARN.LCOK !

The PR is not that useful, i created it because I was starting to work on bumping Azurite, and I wanted to update libraries before. But it turns out there are enough updates to justify first creating this PR before the Azurite PR

  • Ran yarn upgrade for functional tests and workflow tests
  • Bump Mocha version from 11 to 12
  • Along with the bump of Macha, deprecated mocha-junit-reporter, which has not been updated for more than 3 years, and was not compatible with mocha-junit-reporter. Replaced directly with an exporter available in Mocha.
  • Bump Scubaclient to 1.2.0
  • Many bump in /Workflow tests, plus removed a few useless deps (ts-node, ts-jest)

@bert-e

bert-e commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Hello sylvainsenechal,

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.

Comment thread tests/functional/mocha/mocha-reporter.json Outdated
…lt-in xunit reporter

mocha-junit-reporter is unmaintained and broken on mocha 12 due to its use of pre-class prototypal inheritance. The built-in xunit reporter produces equivalent JUnit XML and has no extra dependency.

Issue: ZENKO-5364
@scality scality deleted a comment from bert-e Sep 21, 2026
@bert-e

bert-e commented Sep 21, 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

@SylvainSenechal
SylvainSenechal marked this pull request as ready for review September 21, 2026 16:02
@SylvainSenechal
SylvainSenechal requested review from a team, DarkIsDude and delthas September 21, 2026 16:02
@@ -111,8 +111,11 @@ def merge_reports(output_file, input_files):
all_testsuites.extend(testsuites)

except ET.ParseError as e:

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not related to the pr but I just hit this bug :

4 CTST rerun, one of them I cancelled manually : End up with a file thats not parsable and it fails the whole archive step, forcing us to rerun the whole ci.

Possible further improvement that I left : Only continue on parse error when its not the latest run file

"jest": "^30.5.2",
"js-yaml": "^5.4.2",
"sinon": "^22.1.0",
"ts-jest": "^29.4.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ts-jest@^29.4.12 is not compatible with jest@^30.5.2. ts-jest 29.x targets Jest 29 and will likely fail at runtime with Jest 30's changed transformer API. Bump to ts-jest@^30.0.0 to match the Jest major version.

Suggested change
"ts-jest": "^29.4.12",
"ts-jest": "^30.0.0",

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok big guy, ts-jest 30 doesn't exist

module.exports = {
reporterEnabled: 'spec, xunit',
xunitReporterOptions: {
output: process.env.MOCHA_FILE || '_reports/test-results.xml',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we ok with that ? "testsuitesTitle": "{id}" what was the goal of that ?


# Ensure test results dir exists for Mocha JUnit reporter
mkdir -p "$(dirname "$MOCHA_FILE")"
# Ensure test results dir exists for Mocha xunit reporter

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need that (mocha don't do it directly?) ? Why this change ?

@SylvainSenechal

Copy link
Copy Markdown
Contributor Author

/approve

@bert-e

bert-e commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

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

  • ✔️ development/2.16

The following branches have NOT changed:

  • development/2.10
  • development/2.11
  • development/2.12
  • development/2.13
  • development/2.14
  • development/2.15
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

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

  • hotfix/2.13.5

Please check the status of the associated issue ZENKO-5364.

Goodbye sylvainsenechal.

The following options are set: approve

@bert-e
bert-e merged commit f3dd3b5 into development/2.16 Sep 22, 2026
40 of 42 checks passed
@bert-e
bert-e deleted the improvement/ZENKO-5364 branch September 22, 2026 18:30
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