8000 Remove mocha, chalk by pluma · Pull Request #15739 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

Remove mocha, chalk #15739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Mar 1, 2022
Merged

Remove mocha, chalk #15739

merged 5 commits into from
Mar 1, 2022

Conversation

pluma
Copy link
Contributor
@pluma pluma commented Feb 15, 2022

Scope & Purpose

This PR removes mocha and chalk. These are internal (undocumented) dependencies that cause unnecessary noise during audits and are no longer used as of 3.8 (see #14501, #14505).

  • 💩 Bugfix

Checklist

  • 📖 CHANGELOG entry made
  • Backports
    • Backport for 3.9: (Please link PR)

Related Information

  • GitHub issue / Jira ticket: ES-1015

@pluma pluma added this to the 3.10 milestone Feb 15, 2022
@pluma pluma self-assigned this Feb 15, 2022
@cla-bot cla-bot bot added the cla-signed label Feb 15, 2022
@pluma pluma mentioned this pull request Feb 15, 2022
3 tasks
Copy link
Contributor
@ajurdak ajurdak left a comment

Choose a reason for hiding this comment

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

LGTM.

@pluma
Copy link
Contributor Author
pluma commented Feb 16, 2022

Build failure is unrelated. Restarted jenkins.

@pluma
Copy link
Contributor Author
pluma commented Feb 16, 2022

jenkins is green

@pluma
Copy link
8000
Contributor Author
pluma commented Feb 28, 2022

Rerunning jenkins after merge.

@pluma pluma merged commit 9d9fc6a into devel Mar 1, 2022
@pluma pluma deleted the feature/remove-mocha-chalk branch March 1, 2022 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
40F1
Development

Successfully merging this pull request may close these issues.

3 participants
0