Bump tough-cookie and selenium-standalone in /BlazorDialog #13
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.
Removes tough-cookie. It's no longer used after updating ancestor dependency selenium-standalone. These dependencies need to be updated together.
Removes
tough-cookie
Updates
selenium-standalone
from 6.16.0 to 6.24.0Release notes
Sourced from selenium-standalone's releases.
Changelog
Sourced from selenium-standalone's changelog.
... (truncated)
Commits
39f4a1c
6.24.07e575d6
selenium v4 fixes #554 #449 (#556)a912029
fix "chroimum" typo (#544)da28d38
chore(deps): update ubuntu:latest docker digest to aba80b7 (#547)4acbac5
chore(deps): update dependency doctoc to v2 (#523)16aa034
chore(deps): update dependency eslint-plugin-prettier to v3.3.0 (#531)1baa8ec
chore(deps): update dependency husky to v4.3.6 (#530)554c8f3
chore(deps): update dependency eslint to v7.15.0 (#524)8aa85d7
chore(deps): update dependency husky to v4.3.5 (#527)aad5b77
chore(deps): update dependency eslint-config-prettier to v7 (#526)Maintainer changes
This version was pushed to npm by mgrybyk, a new releaser for selenium-standalone since your current version.
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.