Skip to content
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

refactor: Upgrade npmlog from 4.1.2 to 7.0.1 #228

Merged
merged 1 commit into from
Oct 22, 2023

Conversation

parseplatformorg
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade npmlog from 4.1.2 to 7.0.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


Warning: This is a major version upgrade, and may be a breaking change.

  • The recommended version is 7 versions ahead of your current version.
  • The recommended version was released a year ago, on 2022-10-19.
Release notes
Package name: npmlog
  • 7.0.1 - 2022-10-19

    7.0.1 (2022-10-19)

    Bug Fixes

  • 7.0.0 - 2022-10-14

    7.0.0 (2022-10-14)

    ⚠️ BREAKING CHANGES

    • npmlog is now compatible with the following semver range for node: ^14.17.0 || ^16.13.0 || >=18.0.0

    Features

    Dependencies

  • 6.0.2 - 2022-04-20

    6.0.2 (2022-04-20)

    Dependencies

    • update gauge requirement from ^4.0.0 to ^4.0.1 (cf52b06)
    • update gauge requirement from ^4.0.1 to ^4.0.2 (#96) (53063a9)
    • update gauge requirement from ^4.0.2 to ^4.0.3 (#101) (929686c)
  • 6.0.1 - 2022-02-09

    Bug Fixes

    • evaluate this.heading only once (3633d33)
    • notice: change blue foreground to cyan (eba1a41)

    Dependencies

    • @ npmcli/template-oss@2.7.1 (5e7b9f4)
    • are-we-there-yet@3.0.0 (7aefa36)

    v5.0.1

    • update are-we-there-yet to v2.0.0.

    v5.0.0

    • Drop support for node versions 6 and 8
    • Fix bug where gauge was enabled when paused

    v4.0.2

    • Added installation instructions.

    v4.0.1

    • Fix bugs where log.progressEnabled got out of sync with how gauge kept
      track of these things resulting in a progressbar that couldn't be disabled.

    v4.0.0

    • Allow creating log levels that are an empty string or 0.

    v3.1.2

    • Update to gauge@1.6.0 adding support for default values for template
      items.

    v3.1.1

    • Update to gauge@1.5.3 to fix to 1.x compatibility when it comes to
      when a progress bar is enabled. In 1.x if you didn't have a TTY the
      progress bar was never shown. In 2.x it merely defaults to disabled,
      but you can enable it explicitly if you still want progress updates.

    v3.1.0

    • Update to gauge@2.5.2:
      • Updates the signal-exit dependency which fixes an incompatibility with
        the node profiler.
      • Uses externalizes its ansi code generation in console-control-strings
    • Make the default progress bar include the last line printed, colored as it
      would be when printing to a tty.

    v3.0.0

    • Switch to gauge@2.0.0, for better performance, better look.
    • Set stderr/stdout blocking if they're tty's, so that we can hide a
      progress bar going to stderr and then safely print to stdout. Without
      this the two can end up overlapping producing confusing and sometimes
      corrupted output.

    v2.0.0

    • Make the error event non-fatal so that folks can use it as a prefix.

    v1.0.0

    • Add progress bar with gauge@1.1.0
  • 6.0.0 - 2021-11-16

    6.0.0

  • 5.0.1 - 2021-09-02

    5.0.1

  • 5.0.0 - 2021-07-22

    5.0.0

  • 4.1.2 - 2017-06-26

    4.1.2

from npmlog GitHub release notes
Commit messages
Package name: npmlog

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Upgrade npmlog from 4.1.2 to 7.0.1 refactor: Upgrade npmlog from 4.1.2 to 7.0.1 Oct 22, 2023
@parse-github-assistant
Copy link

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

@codecov
Copy link

codecov bot commented Oct 22, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (089149b) 100.00% compared to head (67fd27c) 100.00%.
Report is 1 commits behind head on master.

❗ Current head 67fd27c differs from pull request most recent head a424d67. Consider uploading reports for the commit a424d67 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #228   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines          277       277           
=========================================
  Hits           277       277           

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

Copy link
Member

@mtrezza mtrezza left a comment

Choose a reason for hiding this comment

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

Looks good; the only breaking change seems to be the requirement of Node 14+

@mtrezza mtrezza merged commit 5536102 into master Oct 22, 2023
4 checks passed
stage88 added a commit to stage88/parse-server-push-adapter that referenced this pull request Nov 17, 2023
refactor: Upgrade npmlog from 4.1.2 to 7.0.1 (parse-community#228)
@parseplatformorg
Copy link
Contributor Author

🎉 This change has been released in version 5.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants