[dependabot]

Bumps github.com/opencontainers/cgroups from 0.0.7 to 0.1.0.

Release notes

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

v0.1.0

What's Changed

• devices: drop cilium/ebpf{,link} deps by @​kolyshkin in opencontainers/cgroups#64

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

v0.0.9

What's Changed

• devices: work around kernel OOB write in BPF_PROG_QUERY by @​kolyshkin in opencontainers/cgroups#69
• ci: bump Go, golangci-lint, codespell, and runners by @​kolyshkin in opencontainers/cgroups#70
• Misc fixups by @​kolyshkin in opencontainers/cgroups#72
• ci: skip running TestParallelConnections locally by @​kolyshkin in opencontainers/cgroups#71

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

v0.0.8

What's Changed

• getallpids: Ignore removed cgroups by @​halaney in opencontainers/cgroups#67
• v2: set memory.oom.group => OOMPolicy in systemd by @​tych0 in opencontainers/cgroups#41
• build(deps): bump actions/checkout from 6 to 7 by @​dependabot[bot] in opencontainers/cgroups#63
• build(deps): bump actions/cache from 5 to 6 by @​dependabot[bot] in opencontainers/cgroups#65
• build(deps): bump actions/setup-go from 6 to 7 by @​dependabot[bot] in opencontainers/cgroups#68

New Contributors

• @​tych0 made their first contribution in opencontainers/cgroups#41
• @​halaney made their first contribution in opencontainers/cgroups#67

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

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

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coveralls]

Coverage Report for CI Build 40039189944

Coverage remained the same at 44.982%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	13610
Covered Lines:	6122
Line Coverage:	44.98%
Coverage Strength:	0.45 hits per line

---

💛 - Coveralls

[cdesiniotis]

@dependabot rebase

[cdesiniotis]

/ok to test 4871587