Update xwp/stream requirement from ^3.9.0 to ^3.9.3

[dependabot]

Updates the requirements on xwp/stream to permit the latest version.

Commits

• f04e73f 905683d Merge pull request #1436 from xwp/release/3.9.3
• fe99b53 905683d Merge pull request #1436 from xwp/release/3.9.3
• 1062414 61a5ab9 Merge pull request #1435 from xwp/fix/remove-uninstallation
• 5a4c887 ea4a1fa Merge pull request #1432 from xwp/fix/cve-2022-43450
• 5e4c152 eb08c13 Merge pull request #1394 from xwp/release/3.9.2
• 44f72b4 1c1880b Release 3.9.1
• See full diff 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 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)

[hm-backport]

The backport to v12-branch failed:

Commits ["f770364f46e1a0a85363b1fe07045f074d8bc4a1"] could not be cherry-picked on top of v12-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v12-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick f770364f46e1a0a85363b1fe07045f074d8bc4a1
# Create a new branch with these backported commits.
git checkout -b backport-260-to-v12-branch
# Push it to GitHub.
git push --set-upstream origin backport-260-to-v12-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

Then, create a pull request where the base branch is v12-branch and the compare/head branch is backport-260-to-v12-branch.

[hm-backport]

The backport to v14-branch failed:

Commits ["f770364f46e1a0a85363b1fe07045f074d8bc4a1"] could not be cherry-picked on top of v14-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v14-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick f770364f46e1a0a85363b1fe07045f074d8bc4a1
# Create a new branch with these backported commits.
git checkout -b backport-260-to-v14-branch
# Push it to GitHub.
git push --set-upstream origin backport-260-to-v14-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

Then, create a pull request where the base branch is v14-branch and the compare/head branch is backport-260-to-v14-branch.

[hm-backport]

The backport to v15-branch failed:

Commits ["f770364f46e1a0a85363b1fe07045f074d8bc4a1"] could not be cherry-picked on top of v15-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v15-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick f770364f46e1a0a85363b1fe07045f074d8bc4a1
# Create a new branch with these backported commits.
git checkout -b backport-260-to-v15-branch
# Push it to GitHub.
git push --set-upstream origin backport-260-to-v15-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

Then, create a pull request where the base branch is v15-branch and the compare/head branch is backport-260-to-v15-branch.

[hm-backport]

The backport to v13-branch failed:

Commits ["f770364f46e1a0a85363b1fe07045f074d8bc4a1"] could not be cherry-picked on top of v13-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v13-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick f770364f46e1a0a85363b1fe07045f074d8bc4a1
# Create a new branch with these backported commits.
git checkout -b backport-260-to-v13-branch
# Push it to GitHub.
git push --set-upstream origin backport-260-to-v13-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

Then, create a pull request where the base branch is v13-branch and the compare/head branch is backport-260-to-v13-branch.