Skip to content

chore(deps): Bump the backend group across 1 directory with 4 updates - #1065

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/backend-9e8d081a9d
Open

chore(deps): Bump the backend group across 1 directory with 4 updates#1065
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/backend-9e8d081a9d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 28, 2026

Copy link
Copy Markdown
Contributor

Bumps the backend group with 4 updates in the / directory: github.com/containerd/containerd/api, github.com/onsi/ginkgo/v2, github.com/onsi/gomega and github.com/opencontainers/cgroups.

Updates github.com/containerd/containerd/api from 1.10.0 to 1.12.0

Release notes

Sourced from github.com/containerd/containerd/api's releases.

containerd API 1.12.0

Welcome to the api/v1.12.0 release of containerd!

The 13th release for the containerd 1.x API aligns with the containerd 2.4 release.

Highlights

Image Storage

  • Include media type in content create events (#13833)

Runtime

  • Add UpdateSandbox RPC to propagate sandbox controller updates to the shim (#14105)
  • Allow specifying parent checkpoint directory when checkpointing with runc (#13699)

Deprecations

  • Deprecate containerd.io/runtime-allow-mounts shim annotation in favor of MountCapabilities bootstrap extension (#14002)
  • Deprecate task API address and version fields in runc options and move to CreateTaskRequest (#13360)

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

  • Derek McGowan
  • Maksym Pavlenko
  • Wei Fu
  • Jordan Liggitt
  • Samuel Karp
  • Kohei Tokunaga
  • Philip Laine
  • Sebastiaan van Stijn
  • Sergey Kanzhelev

Changes

  • sandbox: wire Controller.Update through to the shim (#14105)
    • 2ea4ddb32f sandbox: add UpdateSandbox RPC and forward Controller.Update to the shim
  • Prepare api/v1.12.0-rc.0 release (#14047)
  • Shim mount handler protocol (#14002)
  • chore(api): update github.com/sirupsen/logrus v1.10.2 (#14037)
    • a28910b14f chore(api): update github.com/sirupsen/logrus v1.10.2
  • Prepare release notes for api/v1.12.0-beta.0 (#13899)
    • 0ff04dc3f7 Prepare release notes for api/v1.12.0-beta.0

... (truncated)

Commits
  • c6d0192 Merge pull request #14170 from samuelkarp/prepare-api-v1.12.0
  • 5c4ea21 Prepare release notes for api/v1.12.0
  • 610d8d8 Merge pull request #14166 from samuelkarp/deprecations-and-removals-for-2.4
  • 531b3a3 tracing: remove deprecated tracing config options
  • ca8579a tracing: add tests for otlp exporter and env vars
  • ee024b7 tracing: remove deprecated otlp configs
  • f7c654f cri: remove deprecated cni bin_dir
  • 4f7de25 cri: remove enable_cdi config option
  • 830b48d cri: delay registry config removal to 2.7
  • c0c4c4a Merge pull request #14115 from dmcgowan/prepare-v2.4.0-rc
  • Additional commits viewable in compare view

Updates github.com/onsi/ginkgo/v2 from 2.32.0 to 2.33.0

Release notes

Sourced from github.com/onsi/ginkgo/v2's releases.

v2.33.0

Features

  • The JUnit reporter now records each spec's ReportEntrys as <properties> on its <testcase> element, with the entry's name and its JSON-encoded value. Thanks @​pohly! [23db51a]

Maintenance

  • Releases are now cut by a GitHub Actions workflow (Actions -> Release -> Run workflow) rather than by hand, with changelog entries collected under ## Unreleased as the work happens. See RELEASING.md. [8616ecb]

v2.32.2

2.32.2

Fixes

  • fix bug where ginkgo -race -p was taking extra long to exit [c6792b0]

v2.32.1

2.32.1

Fixes

  • Defer AfterAll until repeated spec completes [e647b3b]
Changelog

Sourced from github.com/onsi/ginkgo/v2's changelog.

2.33.0

Features

  • The JUnit reporter now records each spec's ReportEntrys as <properties> on its <testcase> element, with the entry's name and its JSON-encoded value. Thanks @​pohly! [23db51a]

Maintenance

  • Releases are now cut by a GitHub Actions workflow (Actions -> Release -> Run workflow) rather than by hand, with changelog entries collected under ## Unreleased as the work happens. See RELEASING.md. [8616ecb]

2.32.2

Fixes

  • fix bug where ginkgo -race -p was taking extra long to exit [c6792b0]

2.32.1

Fixes

  • Defer AfterAll until repeated spec completes [e647b3b]
Commits
  • 9f94149 v2.33.0
  • db78e1b changelog: entries for the JUnit ReportEntry support and the release flow
  • 8616ecb ci: release from a single workflow_dispatch button
  • d8d9cdd README: add a sponsor badge
  • ac70da6 README: dark-mode logo and a docs badge
  • 23db51a junit: support ReportEntry
  • b9e3bdd v2.32.2
  • c6792b0 fix bug where ginkgo -race -p was taking extra long to exit
  • f2d0f65 v2.32.1
  • e647b3b Defer AfterAll until repeated spec completes
  • Additional commits viewable in compare view

Updates github.com/onsi/gomega from 1.42.1 to 1.44.0

Release notes

Sourced from github.com/onsi/gomega's releases.

v1.44.0

Fixes

  • BeNumerically compares signed and unsigned integers by value: -1 no longer equals uint64(math.MaxUint64) and uint(5) is now greater than -3 (#925) [26e3c6b]
  • BeNumerically("~") no longer overflows when computing the distance between extreme integers (#928) [1955764]
  • BeNumerically("==", x, threshold) now honors the threshold for floats, as it already did for integers (#927) [10e2aca]
  • HaveKeyWithValue succeeds if any key accepted by the key matcher has a matching value, rather than depending on map iteration order (#929) [ffc577a]
  • HaveKey and HaveKeyWithValue treat key and value matcher errors like ContainElement does: a match wins, and an error is only reported when nothing matches (#926) [dc91598]
  • MatchJSON no longer treats numbers too large for a float64 as equal to one another (#930) [9d619a5]
  • MatchJSON compares integers beyond ±2^53 exactly, so neighboring large integers (e.g. IDs) no longer match; all other numbers are still compared as float64s (#931) [8ef1aa7, 630fe12]
  • HaveExactElements reports missing or extra elements that start at index 0, and reports the first extra element's index rather than the last (#934) [af1b777]
  • MatchYAML compares every document in a multi-document stream rather than only the first; empty documents (e.g. a leading or trailing ---) are ignored (#933) [2773796]
  • MatchXML ignores namespace prefixes: elements and attributes are compared by namespace URI, and the URIs declared on each element must match whatever prefix they are bound to (#932) [c0dbd89, 2565350]

v1.43.1

Maintenance

  • Update go.yaml.in/yaml/v3 to v3.0.5 [d547015]
  • Releases are now cut by a GitHub Actions workflow (Actions -> Release -> Run workflow) rather than by hand, with changelog entries collected under ## Unreleased as the work happens. Releases still ship the stripped-down tree on master-lite - tests removed and Ginkgo dropped from go.mod - and the workflow now builds it and checks it on every push. See RELEASING.md. [e9dc84d]

v1.43.0

1.43.0

Features

Add gomock adaptor extension for using Gomega matchers with gomock

Changelog

Sourced from github.com/onsi/gomega's changelog.

1.44.0

Fixes

  • BeNumerically compares signed and unsigned integers by value: -1 no longer equals uint64(math.MaxUint64) and uint(5) is now greater than -3 (#925) [26e3c6b]
  • BeNumerically("~") no longer overflows when computing the distance between extreme integers (#928) [1955764]
  • BeNumerically("==", x, threshold) now honors the threshold for floats, as it already did for integers (#927) [10e2aca]
  • HaveKeyWithValue succeeds if any key accepted by the key matcher has a matching value, rather than depending on map iteration order (#929) [ffc577a]
  • HaveKey and HaveKeyWithValue treat key and value matcher errors like ContainElement does: a match wins, and an error is only reported when nothing matches (#926) [dc91598]
  • MatchJSON no longer treats numbers too large for a float64 as equal to one another (#930) [9d619a5]
  • MatchJSON compares integers beyond ±2^53 exactly, so neighboring large integers (e.g. IDs) no longer match; all other numbers are still compared as float64s (#931) [8ef1aa7, 630fe12]
  • HaveExactElements reports missing or extra elements that start at index 0, and reports the first extra element's index rather than the last (#934) [af1b777]
  • MatchYAML compares every document in a multi-document stream rather than only the first; empty documents (e.g. a leading or trailing ---) are ignored (#933) [2773796]
  • MatchXML ignores namespace prefixes: elements and attributes are compared by namespace URI, and the URIs declared on each element must match whatever prefix they are bound to (#932) [c0dbd89, 2565350]

1.43.1

Maintenance

  • Update go.yaml.in/yaml/v3 to v3.0.5 [d547015]
  • Releases are now cut by a GitHub Actions workflow (Actions -> Release -> Run workflow) rather than by hand, with changelog entries collected under ## Unreleased as the work happens. Releases still ship the stripped-down tree on master-lite - tests removed and Ginkgo dropped from go.mod - and the workflow now builds it and checks it on every push. See RELEASING.md. [e9dc84d]

1.43.0

Features

Add gomock adaptor extension for using Gomega matchers with gomock

Commits

Updates github.com/opencontainers/cgroups from 0.0.4 to 0.1.0

Release notes

Sourced from github.com/opencontainers/cgroups's releases.

v0.1.0

What's Changed

Full Changelog: opencontainers/cgroups@v0.0.9...v0.1.0

v0.0.9

What's Changed

Full Changelog: opencontainers/cgroups@v0.0.8...v0.0.9

v0.0.8

What's Changed

New Contributors

Full Changelog: opencontainers/cgroups@v0.0.7...v0.0.8

v0.0.7

What's Changed

New Contributors

Full Changelog: opencontainers/cgroups@v0.0.6...v0.0.7

v0.0.6

What's Changed

... (truncated)

Changelog

Sourced from github.com/opencontainers/cgroups's changelog.

Releases

The release process hopes to encourage early, consistent consensus-building during project development. The mechanisms used are regular community communication on the mailing list about progress, scheduled meetings for issue resolution and release triage, and regularly paced and communicated releases. Releases are proposed and adopted or rejected using the usual project governance rules and procedures.

An anti-pattern that we want to avoid is heavy development or discussions "late cycle" around major releases. We want to build a community that is involved and communicates consistently through all releases instead of relying on "silent periods" as a judge of stability.

Parallel releases

A single project MAY consider several motions to release in parallel. However each motion to release after the initial 0.1.0 MUST be based on a previous release that has already landed.

For example, runtime-spec maintainers may propose a v1.0.0-rc2 on the 1st of the month and a v0.9.1 bugfix on the 2nd of the month. They may not propose a v1.0.0-rc3 until the v1.0.0-rc2 is accepted (on the 7th if the vote initiated on the 1st passes).

Specifications

The OCI maintains three categories of projects: specifications, applications, and conformance-testing tools. However, specification releases have special restrictions in the [OCI charter][charter]:

  • They are the target of backwards compatibility (§7.g), and
  • They are subject to the OFWa patent grant (§8.d and e).

To avoid unfortunate side effects (onerous backwards compatibility requirements or Member resignations), the following additional procedures apply to specification releases:

Planning a release

Every OCI specification project SHOULD hold meetings that involve maintainers reviewing pull requests, debating outstanding issues, and planning releases. This meeting MUST be advertised on the project README and MAY happen on a phone call, video conference, or on IRC. Maintainers MUST send updates to the dev@opencontainers.org with results of these meetings.

Before the specification reaches v1.0.0, the meetings SHOULD be weekly. Once a specification has reached v1.0.0, the maintainers may alter the cadence, but a meeting MUST be held within four weeks of the previous meeting.

The release plans, corresponding milestones and estimated due dates MUST be published on GitHub (e.g. https://github.com/opencontainers/runtime-spec/milestones). GitHub milestones and issues are only used for community organization and all releases MUST follow the project governance rules and procedures.

Timelines

Specifications have a variety of different timelines in their lifecycle.

  • Pre-v1.0.0 specifications SHOULD release on a monthly cadence to garner feedback.
  • Major specification releases MUST release at least three release candidates spaced a minimum of one week apart. This means a major release like a v1.0.0 or v2.0.0 release will take 1 month at minimum: one week for rc1, one week for rc2, one week for rc3, and one week for the major release itself. Maintainers SHOULD strive to make zero breaking changes during this cycle of release candidates and SHOULD restart the three-candidate count when a breaking change is introduced. For example if a breaking change is introduced in v1.0.0-rc2 then the series would end with v1.0.0-rc4 and v1.0.0.
  • Minor and patch releases SHOULD be made on an as-needed basis.

... (truncated)

Commits
  • 30a2293 Merge pull request #64 from kolyshkin/drop-cilium-ebpf
  • 713912d devices: drop cilium/ebpf{,link} deps
  • 974f3a5 Merge pull request #71 from kolyshkin/unsafe-tests
  • 8ef8f40 ci: skip running TestParallelConnections locally
  • d67c8a6 Merge pull request #72 from kolyshkin/fixups
  • 8bbeb6b Merge pull request #70 from kolyshkin/ci-bumps-II
  • 5ee0baa ci: replace modernize job with golangci linters
  • ed19a09 ci: bump Go versions
  • e3152db ci: bump golangci-lint, codespell, and runners
  • 30ca211 devices: setV2: add missing O_CLOEXEC
  • Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
github.com/containerd/containerd/api [>= 1.11.a, < 1.12]

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
chore(deps): Bump the backend group across 1 directory with 4 updates
fe876fa 
Bumps the backend group with 4 updates in the / directory: [github.com/containerd/containerd/api](https://github.com/containerd/containerd), [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo), [github.com/onsi/gomega](https://github.com/onsi/gomega) and [github.com/opencontainers/cgroups](https://github.com/opencontainers/cgroups).


Updates `github.com/containerd/containerd/api` from 1.10.0 to 1.12.0
- [Release notes](https://github.com/containerd/containerd/releases)
- [Changelog](https://github.com/containerd/containerd/blob/main/RELEASES.md)
- [Commits](containerd/containerd@api/v1.10.0...api/v1.12.0)

Updates `github.com/onsi/ginkgo/v2` from 2.32.0 to 2.33.0
- [Release notes](https://github.com/onsi/ginkgo/releases)
- [Changelog](https://github.com/onsi/ginkgo/blob/master/CHANGELOG.md)
- [Commits](onsi/ginkgo@v2.32.0...v2.33.0)

Updates `github.com/onsi/gomega` from 1.42.1 to 1.44.0
- [Release notes](https://github.com/onsi/gomega/releases)
- [Changelog](https://github.com/onsi/gomega/blob/master/CHANGELOG.md)
- [Commits](onsi/gomega@v1.42.1...v1.44.0)

Updates `github.com/opencontainers/cgroups` from 0.0.4 to 0.1.0
- [Release notes](https://github.com/opencontainers/cgroups/releases)
- [Changelog](https://github.com/opencontainers/cgroups/blob/main/RELEASES.md)
- [Commits](opencontainers/cgroups@v0.0.4...v0.1.0)

---
updated-dependencies:
- dependency-name: github.com/containerd/containerd/api
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: backend
- dependency-name: github.com/onsi/ginkgo/v2
  dependency-version: 2.33.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: backend
- dependency-name: github.com/onsi/gomega
  dependency-version: 1.44.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: backend
- dependency-name: github.com/opencontainers/cgroups
  dependency-version: 0.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: backend
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Sep 28, 2026
@netlify

netlify Bot commented Sep 28, 2026 •
edited
Loading

Copy link
Copy Markdown

✅ Deploy Preview for urunc canceled.

Name Link
🔨 Latest commit fe876fa
🔍 Latest deploy log https://app.netlify.com/projects/urunc/deploys/6aba8bf9c765de0008ca5208

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants