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

Update dependency node-notifier to v8 [SECURITY] #54

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 23, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
node-notifier 6.0.0 -> 8.0.1 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2020-7789

This affects the package node-notifier before 8.0.1. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.


Release Notes

mikaelbr/node-notifier

v8.0.1

Compare Source

v8.0.0

Compare Source

Breaking changes:

  • Expire time for notify-send is made to match macOS and Windows with default time of 10 seconds. The API is changed to take seconds as input and converting it to milliseconds before passing it on to notify-send. See #​341.

v7.0.2

Compare Source

  • Updates dependencies
  • Fixes issue with haning Windows notifications when disabled (#​335)

v7.0.1

Compare Source

  • Fixes import of uuid, removes deprecation warnings

v7.0.0

Compare Source

Features
  • NotifySend support for app-name (#​299, see docs)
Breaking Changes
  • All notify messages now have auto bound context to make it easier to pass as variables/arguments (#​306)
  • Updated snoreToast to version 0.7.0 with new input features (#​293)
  • Breaking snoreToast: Sanitizing data now changes "timedout" to "timeout"

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

None yet

1 participant