Bump semver and appium in /example/e2e #134
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
|
It looks like you are reviewing a Dependabot upgrade PR! 🛠️ 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:
🎯 Target merge date for this PR: 16/10/2023 🎯 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 anyCRITICAL 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 thedependabot-refactor-required label to this PR and ping #ask-security for further advice.
|
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/example/e2e/semver-and-appium-7.5.4
branch
from
06bfd58 to
f81de8f
Compare
Bumps [semver](https://github.com/npm/node-semver) to 7.5.4 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.5.4 - [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.5.4) Updates `appium` from 1.21.0 to 2.1.3 - [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/[email protected]/packages/appium) --- updated-dependencies: - dependency-name: semver dependency-type: indirect - dependency-name: appium dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/example/e2e/semver-and-appium-7.5.4
branch
from
f81de8f to
f15e0cd
Compare
|
@dependabot rebase |
|
Superseded by #177. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/example/e2e/semver-and-appium-7.5.4
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps semver to 7.5.4 and updates ancestor dependency appium. These dependencies need to be updated together.
Updates
semverfrom 5.7.1 to 7.5.4Release notes
Sourced from semver's releases.
... (truncated)
Changelog
Sourced from semver's changelog.
... (truncated)
Commits
36cd334chore: release 7.5.48456d87chore: postinstall for dependabot template-oss PRdde1f00chore: postinstall for dependabot template-oss PRdffcd1bchore: bump@npmcli/template-ossfrom 4.16.0 to 4.17.0d619f66chore: postinstall for dependabot template-oss PR3bc4247chore: bump@npmcli/template-ossfrom 4.15.1 to 4.16.0cc6fde2fix: trim each range set before parsing99d8287fix: correctly parse long build ids as valid (#583)4f0f6b1chore: fix arguments in whitespace test (#574)6bd1a37chore: remove duplicate test in semver class (#575)Maintainer changes
This version was pushed to npm by npm-cli-ops, a new releaser for semver since your current version.
Updates
appiumfrom 1.21.0 to 2.1.3Release notes
Sourced from appium's releases.
... (truncated)
Changelog
Sourced from appium's changelog.
... (truncated)
Commits
a01a91dchore: publish524447echore: publish820428bchore: publishd6204b6chore: publish6082cb1docs(appium): add environment variable docs (#18994)b88ac49test(appium): add test to prove umbrella commands don't circumvent driver com...5a26111fix(appium): Update the GET /status response to be in sync with the standard ...aaf58c3feat(base-driver): Make it possible to provide settings as a map in session c...fb34ab9fix(types): update dependency type-fest to v3.13.1b85a92afix(appium): update dependency winston to v3.10.0You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.