Skip to content

NIFI-9460: Update Lodash to 4.17.21#5605

Merged
mtien-apache merged 2 commits intoapache:mainfrom
sardell:NIFI-9460
Dec 16, 2021
Merged

NIFI-9460: Update Lodash to 4.17.21#5605
mtien-apache merged 2 commits intoapache:mainfrom
sardell:NIFI-9460

Conversation

@sardell
Copy link
Contributor

@sardell sardell commented Dec 15, 2021

Thank you for submitting a contribution to Apache NiFi.

Please provide a short description of the PR here:

Description of PR

NIFI-9460: Update Lodash version to 4.17.21

This PR bumps lodash to 4.17.21 in nifi-registry. In addition, I changed the NiFi UI deps to use lodash instead of lodash-core. I did this because lodash-core is still using an older version of lodash and there is no indication they will update to utilize the 4.17.21 release (see current open issues).

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced
    in the commit message?

  • Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

  • Has your PR been rebased against the latest commit within the target branch (typically main)?

  • Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

  • Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
  • Have you written or updated unit tests to verify your changes?
  • Have you verified that the full build is successful on JDK 8?
  • Have you verified that the full build is successful on JDK 11?
  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
  • If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
  • If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

@@ -18,28 +18,28 @@
"dependencies": {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Although there appear to be many changes in this file, most are a result of npm re-ordering the dependencies alphabetically after removing lodash-core and installing lodash@4.17.21 (this happens whenever an npm command is run that changes the package.json file).

@sardell sardell marked this pull request as ready for review December 15, 2021 15:57
@mtien-apache
Copy link
Contributor

Reviewing

@mtien-apache mtien-apache self-requested a review December 16, 2021 21:35
Copy link
Contributor

@mtien-apache mtien-apache left a comment

Choose a reason for hiding this comment

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

Thanks for the PR @sardell! LGTM. Verified npm audit does not list lodash as a vulnerability.

@mtien-apache mtien-apache merged commit 293919f into apache:main Dec 16, 2021
krisztina-zsihovszki pushed a commit to krisztina-zsihovszki/nifi that referenced this pull request Jun 28, 2022
* NIFI-9460: update lodash transitive dep in registry

* NIFI-9460: use lodash instead of lodash-core

Merged apache#5605 into main.
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.

2 participants