Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 7, 2025

Bumps semver to 7.6.3 and updates ancestor dependency appium. These dependencies need to be updated together.

Updates semver from 5.7.1 to 7.6.3

Release notes

Sourced from semver's releases.

v7.6.3

7.6.3 (2024-07-16)

Bug Fixes

Documentation

v7.6.2

7.6.2 (2024-05-09)

Bug Fixes

v7.6.1

7.6.1 (2024-05-04)

Bug Fixes

Dependencies

Chores

v7.6.0

7.6.0 (2024-01-31)

Features

Chores

... (truncated)

Changelog

Sourced from semver's changelog.

7.6.3 (2024-07-16)

Bug Fixes

Documentation

7.6.2 (2024-05-09)

Bug Fixes

7.6.1 (2024-05-04)

Bug Fixes

Dependencies

Chores

7.6.0 (2024-01-31)

Features

Chores

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by npm-cli-ops, a new releaser for semver since your current version.


Updates appium from 1.21.0 to 2.14.1

Release notes

Sourced from appium's releases.

appium@2.14.1

2.14.1 (2025-01-06)

Bug Fixes

  • appium: Do not update BiDi commands for drivers which don't support it (#20879) (13d8b03)
  • execute-driver-plugin: update dependency webdriverio to v9.5.1 (#20875) (93e4288)
  • support: update dependency teen_process to v2.2.3 (#20882) (488e5de)

appium@2.13.1

2.13.1 (2024-12-05)

Bug Fixes

  • docutils: update dependency lilconfig to v3.1.3 (#20803) (93fa5cc)
  • support: update dependency axios to v1.7.9 (#20811) (69f100a)
  • support: update dependency teen_process to v2.2.2 (#20808) (c91683f)
  • types: update dependency type-fest to v4.30.0 (#20802) (8590432)

appium@2.13.0

2.13.0 (2024-12-02)

Features

  • base-driver: Allow to prefix feature names with automation names (#20793) (942057d)

Bug Fixes

  • types: update dependency type-fest to v4.29.1 (#20795) (6ba31fe)

appium@2.12.2

2.12.2 (2024-11-29)

Bug Fixes

  • appium: correctly handle git/github install types (fix #20781) (#20788) (522f05d)
  • appium: update dependency winston to v3.16.0 (275da08)
  • appium: update dependency winston to v3.17.0 (#20736) (f91d8c8)
  • docutils: update dependency yaml to v2.6.1 (#20762) (a5389e6)
  • support: update dependency axios to v1.7.8 (#20778) (f9920e2)
  • types: update dependency type-fest to v4.27.0 (#20754) (d6b4079)
  • types: update dependency type-fest to v4.28.0 (#20775) (a25d8f1)
  • types: update dependency type-fest to v4.29.0 (#20783) (b6aa5ac)

appium@2.12.1

... (truncated)

Changelog

Sourced from appium's changelog.

2.14.1 (2025-01-06)

Bug Fixes

  • appium: Do not update BiDi commands for drivers which don't support it (#20879) (13d8b03)
  • execute-driver-plugin: update dependency webdriverio to v9.5.1 (#20875) (93e4288)
  • support: update dependency teen_process to v2.2.3 (#20882) (488e5de)

2.14.0 (2025-01-02)

Features

  • appium: Add session.status BiDi command (#20839) (64e768e)
  • appium: allow drivers to define their own bidi commands (#20828) (a917ec6)
  • appium: Update entry point resolution logic for ESM extensions (#20866) (bbfc040)

Bug Fixes

2.13.1 (2024-12-05)

Bug Fixes

  • docutils: update dependency lilconfig to v3.1.3 (#20803) (93fa5cc)
  • support: update dependency axios to v1.7.9 (#20811) (69f100a)
  • support: update dependency teen_process to v2.2.2 (#20808) (c91683f)
  • types: update dependency type-fest to v4.30.0 (#20802) (8590432)

2.13.0 (2024-12-02)

Features

... (truncated)

Commits
  • 3467f32 chore: publish
  • 488e5de fix(support): update dependency teen_process to v2.2.3 (#20882)
  • 13d8b03 fix(appium): Do not update BiDi commands for drivers which don't support it (...
  • 93e4288 fix(execute-driver-plugin): update dependency webdriverio to v9.5.1 (#20875)
  • 6742808 chore: publish
  • 990a066 fix(execute-driver-plugin): update dependency webdriverio to v9.5.0 (#20871)
  • 389a3e8 fix(docutils): update dependency yaml to v2.7.0 (#20870)
  • 588381e test(appium): Delete obsolete todo
  • 3fc57a1 test(appium): Update Bidi over ssl test (#20868)
  • bbfc040 feat(appium): Update entry point resolution logic for ESM extensions (#20866)
  • Additional commits viewable in compare view

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 <dependency name> 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.

@github-management-service

It looks like you are reviewing a Dependabot upgrade PR! 🛠️
That’s great! Keeping our packages up to date to fix security issues in our stack is super important. Team Application Security wants to help make this process as easy and low friction as possible while still moving at pace.

We aim to merge Dependabot PRs within the below timeframes. The objectives are based on the severity of the security vulnerability we are mitigating with the upgrade:

Severity Target Merge (days)
CRITICAL 7 days
HIGH 14 days
MEDIUM 30 days
LOW 90 days

🎯 Target merge date for this PR: 21/01/2025 🎯

FAQ

What if we aren’t vulnerable to this particular CVE? Do we still have to upgrade the package? It’s still a good idea to upgrade the package if we can. With new code patterns and paths being introduced every day, we have no guarantee that we won’t later make ourselves vulnerable. Keeping packages up to date as a matter of due course is also good hygiene.
What if we’re not vulnerable and upgrading is going to be a lot of work? In these cases it’s a good idea to list out the steps you took to confirm we are not vulnerable in this PR. The PR can then be closed and the corresponding Dependabot Alert should be dismissed with the triage steps included as a comment. Please get in touch with Team Application Security via #ask-security before dismissing any CRITICAL alerts.
This is a major version upgrade that requires substantial code refactoring. What should I do? If the upgrade requires substantial refactoring then it is possible that we will miss the objectives we have outlined above. In these cases, you should add the dependabot-refactor-required label to this PR and ping #ask-security for further advice.

@github-management-service github-management-service requested a review from a team January 7, 2025 13:24
@github-management-service

Hello @intercom/team-messenger 👋 this PR fixes a security vulnerability (GHSA-c2qf-rxjj-qqgw) in a repository you own - intercom/intercom-react-native. We have obligation to update our dependencies in a timely manner in order to keep our applications secure. Please take a look at the PR and merge it as soon as possible.

‼️ Note - If no action is taken, an attempt will be made to merge this PR automatically on 2025-01-08 ‼️

@github-management-service

@dependabot rebase

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 7, 2025

Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

@github-management-service

@dependabot squash and merge

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 7, 2025

Dependabot tried to merge this PR, but received the following error from GitHub:

You're not authorized to push to this branch. Visit https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches for more information.

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/example/e2e/multi-13233ec2f8 branch from 2d1e557 to 616bdf7 Compare January 7, 2025 18:40
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 7, 2025

Dependabot tried to merge this PR, but received the following error from GitHub:

At least 1 approving review is required by reviewers with write access. You're not authorized to push to this branch. Visit https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected

Bumps [semver](https://github.com/npm/node-semver) to 7.6.3 and updates ancestor dependency [appium](https://github.com/appium/appium/tree/HEAD/packages/appium). These dependencies need to be updated together.


Updates `semver` from 5.7.1 to 7.6.3
- [Release notes](https://github.com/npm/node-semver/releases)
- [Changelog](https://github.com/npm/node-semver/blob/main/CHANGELOG.md)
- [Commits](npm/node-semver@v5.7.1...v7.6.3)

Updates `appium` from 1.21.0 to 2.14.1
- [Release notes](https://github.com/appium/appium/releases)
- [Changelog](https://github.com/appium/appium/blob/master/packages/appium/CHANGELOG.md)
- [Commits](https://github.com/appium/appium/commits/appium@2.14.1/packages/appium)

---
updated-dependencies:
- dependency-name: semver
  dependency-type: indirect
- dependency-name: appium
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/example/e2e/multi-13233ec2f8 branch from 616bdf7 to de82b41 Compare January 7, 2025 18:53
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 7, 2025

Looks like these dependencies are up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Jan 7, 2025
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/example/e2e/multi-13233ec2f8 branch January 7, 2025 23:15
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.

2 participants