search

customerio / customerio-expo-plugin

MIT License
11 stars 9 forks source link

chore(deps): bump node-notifier and expo-module-scripts #100

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps node-notifier to 8.0.2 and updates ancestor dependency expo-module-scripts. These dependencies need to be updated together.

Updates node-notifier from 6.0.0 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"
Commits


Updates expo-module-scripts from 2.0.0 to 2.1.1

Changelog

Sourced from expo-module-scripts's changelog.

2.1.1 - 2022-08-22

🐛 Bug fixes

  • Fixed with-node.sh doesn't keep quotes when passing arguments to Node.js and caused build errors when there are spaces in target name. (#18741 by @​kudo)

2.1.0 — 2022-08-04

🎉 New features

  • Add templates/scripts/source-login-scripts.sh vendoring tool for node binary resolution in Xcode build phases scripts. (#15336 by @​kudo)

🐛 Bug fixes

  • Fixed source-login-scripts.sh error when extendedglob is enabled in zsh config. (#17024 by @​kudo)
  • Fixed expo-module prepare error if target packages contain temporary kotlin build files. (#17023 by @​kudo)
  • Improved support of nvm sourcing in iOS shell scripts. (#17109 by @​liamronancb)
  • Fixed source-login-scripts.sh ~/zlogin typo. (#17622 by @​vrgimael)
  • Deprecated the unreliable source-login-scripts.sh and sourcing the Node.js binary path from .xcode.env and .xcode.env.local. (#18330 by @​kudo)

💡 Others

  • Updated @testing-library/react-hooks to version 7.0.1. (#14552) by @​Simek)
Commits


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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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](https://github.com/customerio/customerio-expo-plugin/network/alerts).
github-actions[bot] commented 1 year ago

Pull request title looks good 👍!

If this pull request gets merged, it will not cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.0. This pull request is not a breaking change.

All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...
This project uses a special format for pull requests titles. Don't worry, it's easy! This pull request title should be in this format: ``` : short description of change being made ``` **If your pull request [introduces breaking changes](https://web.archive.org/web/20220725195319/https://nordicapis.com/what-are-breaking-changes-and-how-do-you-avoid-them/)** to the code, use this format: ``` !: short description of breaking change ``` where `` is one of the following: - `feat:` - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project. - `fix:` - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project. - `docs:` - This pull request is making documentation changes, only. - `refactor:` - A change was made that doesn't fix a bug or add a feature. - `test:` - Adds missing tests or fixes broken tests. - `style:` - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc) - `perf:` - Changes improve performance of the code. - `build:` - Changes to the build system (maven, npm, gulp, etc) - `ci:` - Changes to the CI build system (Travis, GitHub Actions, Circle, etc) - `chore:` - Other changes to project that don't modify source code or test files. - `revert:` - Reverts a previous commit that was made. ### Examples: ``` feat: edit profile photo refactor!: remove deprecated v1 endpoints build: update npm dependencies style: run formatter ``` Need more examples? Want to learn more about this format? [Check out the official docs](https://www.conventionalcommits.org/). **Note:** If your pull request does multiple things such as adding a feature _and_ makes changes to the CI server _and_ fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.
github-actions[bot] commented 1 year ago

Hey, there @dependabot[bot] 👋🤖. I'm a bot here to help you.

⚠️ Pull requests into the branch beta typically only allows changes with the types: fix. From the pull request title, the type of change this pull request is trying to complete is: chore. ⚠️

This pull request might still be allowed to be merged. However, you might want to consider make this pull request merge into a different branch other then beta.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...
This project uses a special format for pull requests titles. Don't worry, it's easy! This pull request title should be in this format: ``` : short description of change being made ``` **If your pull request [introduces breaking changes](https://web.archive.org/web/20220725195319/https://nordicapis.com/what-are-breaking-changes-and-how-do-you-avoid-them/)** to the code, use this format: ``` !: short description of breaking change ``` where `` is one of the following: - `feat:` - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project. - `fix:` - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project. - `docs:` - This pull request is making documentation changes, only. - `refactor:` - A change was made that doesn't fix a bug or add a feature. - `test:` - Adds missing tests or fixes broken tests. - `style:` - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc) - `perf:` - Changes improve performance of the code. - `build:` - Changes to the build system (maven, npm, gulp, etc) - `ci:` - Changes to the CI build system (Travis, GitHub Actions, Circle, etc) - `chore:` - Other changes to project that don't modify source code or test files. - `revert:` - Reverts a previous commit that was made. ### Examples: ``` feat: edit profile photo refactor!: remove deprecated v1 endpoints build: update npm dependencies style: run formatter ``` Need more examples? Want to learn more about this format? [Check out the official docs](https://www.conventionalcommits.org/). **Note:** If your pull request does multiple things such as adding a feature _and_ makes changes to the CI server _and_ fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.
dependabot[bot] commented 1 year ago

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.