Skip to content

Bump github.com/containerd/containerd from 1.7.35 to 1.7.36 in the go-dependencies group - #87

Merged
friegger merged 1 commit into
mainfrom
dependabot/go_modules/go-dependencies-ec9a2b6552
Oct 9, 2026
Merged

friegger merged 1 commit into
mainfrom
dependabot/go_modules/go-dependencies-ec9a2b6552

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 8, 2026

Copy link
Copy Markdown
Contributor

Bumps the go-dependencies group with 1 update: github.com/containerd/containerd.

Updates github.com/containerd/containerd from 1.7.35 to 1.7.36

Release notes

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

containerd 1.7.36

Welcome to the v1.7.36 release of containerd!

The thirty-sixth patch release for containerd 1.7 contains various fixes and updates including a security patch.

Security Updates

Highlights

Image Storage

  • Ensure all layers are fetched when multiple manifests in an index share a config descriptor (#14142)

Runtime

  • Mask /proc/interrupts and CPU thermal throttle sysfs paths in Linux containers by default (#14184)

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

Contributors

  • Samuel Karp
  • Chris Henzie
  • Derek McGowan

Changes

  • b0ab39c205 Prepare release notes for v1.7.36
  • 670a5de22f Merge commit from fork
  • a3a39e5873 Bound Walk references
  • ffc673f859 Bound Dispatch concurrency and references
  • pkg/oci: mask thermal interrupt info (#14184)
  • core/unpack: fetch layers of every config-sharing manifest (#14142)
    • 4684c683c2 core/unpack: fetch layers of every config-sharing manifest
    • 7fba9f7c3c Create new imagetest package

Dependency Changes

This release has no dependency changes

... (truncated)

Changelog

Sourced from github.com/containerd/containerd's changelog.

Versioning and Release

This document details the versioning and release plan for containerd. Stability is a top goal for this project, and we hope that this document and the processes it entails will help to achieve that. It covers the release process, versioning numbering, backporting, API stability and support horizons.

If you rely on containerd, it would be good to spend time understanding the areas of the API that are and are not supported and how they impact your project in the future.

This document will be considered a living document. Supported timelines, backport targets and API stability guarantees will be updated here as they change.

If there is something that you require or this document leaves out, please reach out by filing an issue.

Releases

Releases of containerd will be versioned using dotted triples, similar to Semantic Version. For the purposes of this document, we will refer to the respective components of this triple as <major>.<minor>.<patch>. The version number may have additional information, such as alpha, beta and release candidate qualifications. Such releases will be considered "pre-releases".

Major and Minor Releases

Major and minor releases of containerd will be made from main. Releases of containerd will be marked with GPG signed tags and announced at https://github.com/containerd/containerd/releases. The tag will be of the format v<major>.<minor>.<patch> and should be made with the command git tag -s v<major>.<minor>.<patch>.

After a minor release, a branch will be created, with the format release/<major>.<minor> from the minor tag. All further patch releases will be done from that branch. For example, once we release v1.0.0, a branch release/1.0 will be created from that tag. All future patch releases will be done against that branch.

Release Cadence

Since containerd v2.3 in April 2026, minor releases are provided on a time basis with a cadence of 4 months. New minor releases are scheduled for April, August, and December of each year. This cadence is synchronized with the Kubernetes release schedule to ensure that new features in containerd can be smoothly adopted by new Kubernetes releases.

The maintainers will maintain a roadmap and milestones for each release, however,

... (truncated)

Commits
  • 2892c20 Merge pull request #14229 from samuelkarp/prepare-release-1.7.36
  • cac5660 Prepare release notes for v1.7.36
  • 670a5de Merge commit from fork
  • a3a39e5 Bound Walk references
  • ffc673f Bound Dispatch concurrency and references
  • e594492 Merge pull request #14184 from samuelkarp/cherry-pick-c176f-to-release/1.7
  • 19334a4 pkg/oci: mask thermal interrupt info
  • a81ea12 Merge pull request #14142 from chrishenzie/unpack-shared-config-1.7
  • 4684c68 core/unpack: fetch layers of every config-sharing manifest
  • 7fba9f7 Create new imagetest package
  • See full diff in compare view

Dependabot compatibility score

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

Bumps the go-dependencies group with 1 update: [github.com/containerd/containerd](https://github.com/containerd/containerd).


Updates `github.com/containerd/containerd` from 1.7.35 to 1.7.36
- [Release notes](https://github.com/containerd/containerd/releases)
- [Changelog](https://github.com/containerd/containerd/blob/main/RELEASES.md)
- [Commits](containerd/containerd@v1.7.35...v1.7.36)

---
updated-dependencies:
- dependency-name: github.com/containerd/containerd
  dependency-version: 1.7.36
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-dependencies
...

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 Oct 8, 2026
@dependabot
dependabot Bot requested review from a team as code owners October 8, 2026 19:54
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Oct 8, 2026
@friegger
friegger merged commit 5313988 into main Oct 9, 2026
9 checks passed
@friegger
friegger deleted the dependabot/go_modules/go-dependencies-ec9a2b6552 branch October 9, 2026 05:49
@hardikdr hardikdr added the area/iaas Issues related to IronCore IaaS development. label Oct 9, 2026
@hardikdr hardikdr added this to Roadmap Oct 9, 2026
@github-project-automation github-project-automation Bot moved this to Done in Roadmap Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/iaas Issues related to IronCore IaaS development. dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants