build(deps): bump github.com/containers/gvisor-tap-vsock from 0.7.3 to 0.7.4 #2511
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [github.com/containers/gvisor-tap-vsock](https://github.com/containers/gvisor-tap-vsock) from 0.7.3 to 0.7.4. - [Release notes](https://github.com/containers/gvisor-tap-vsock/releases) - [Commits](containers/gvisor-tap-vsock@v0.7.3...v0.7.4) --- updated-dependencies: - dependency-name: github.com/containers/gvisor-tap-vsock dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Maybe we should create a cherry-pick release? |
|
Or just release v0.22.1 from the current master, after merging this one, but before merging other major changes |
I would call it v0.23.0 if you go that route. There have been almost 100 PRs merged since 0.22.0. Most of them are dependabot and fuzzers, but we also have updated templates, which I think should not go into a patch release. |
Every patch release has always updated templates |
dependabot
bot
deleted the
dependabot/go_modules/github.com/containers/gvisor-tap-vsock-0.7.4
branch
|
We can continue the discussion in: |
Bumps github.com/containers/gvisor-tap-vsock from 0.7.3 to 0.7.4.
Release notes
Sourced from github.com/containers/gvisor-tap-vsock's releases.
Commits
2b36bddMerge pull request #373 from arixmkii/fix-qemu-socket3021c37Merge pull request #369 from containers/dependabot/go_modules/golang.org/x/cr...86ac8a2build(deps): bump golang.org/x/crypto from 0.24.0 to 0.25.0839f8e5go.mod: Update go to 1.2154ba3e9go.mod: Update github.com/insomniacslk/dhcp to latest git mainae9b91aFix OS specific url handling for unix:// scheme in transporta3a9c41Merge pull request #370 from Luap99/ENOBUFS0e970bftest: fix broken dns TXT lookup test7782952handle ENOBUFS when writing to VM socket6dbbe08Merge pull request #365 from containers/dependabot/go_modules/github.com/miek...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 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)