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

Bump node-notifier from 5.4.5 to 8.0.2 #12

Merged
merged 2 commits into from
Mar 17, 2021

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 17, 2021

Bumps node-notifier from 5.4.5 to 8.0.2.

Changelog

Sourced from node-notifier's changelog.

v8.0.2

  • Fixes potential security issue with non-escaping input parameters for notify-send.

v8.0.0

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

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

v7.0.1

  • Fixes import of uuid, removes deprecation warnings

v7.0.0

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"

v6.0.0

Breaking Changes

  • Dropped support for node v6. As of v6 we currently support node versions 8, 10, and 12 (latest).
  • Updated to the latest version of SnoreToast. This removes support for the wait option in that environment as it is now always on. Prepares the way for other new features added to the WindowsToaster.

Other

  • Update to latest version of dependencies.

v5.4.4

  • Fixes potential security issue with non-escaping input parameters for notify-send.

v5.4.3

  • Fixes potential security issue with non-escaping input parameters for notify-send.

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 17, 2021
@newerton newerton merged commit 2d10648 into master Mar 17, 2021
@newerton newerton deleted the dependabot/npm_and_yarn/node-notifier-8.0.2 branch March 17, 2021 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant