Skip to content

chore(deps): replace cni and cns versions with v1.6.35#7757

Merged
cameronmeissner merged 1 commit intomainfrom
jainriya/cns-cni-1.6.35
Feb 4, 2026
Merged

chore(deps): replace cni and cns versions with v1.6.35#7757
cameronmeissner merged 1 commit intomainfrom
jainriya/cns-cni-1.6.35

Conversation

@rejain789
Copy link
Contributor

What this PR does / why we need it:
This pr updates the cni + cns version to 1.6.35-0

Which issue(s) this PR fixes:

Fixes #

Copilot AI review requested due to automatic review settings January 30, 2026 18:20
@github-actions github-actions bot added the components This pull request updates cached components on Linux or Windows VHDs label Jan 30, 2026
@github-actions
Copy link
Contributor

Changes cached containers or packages on windows VHDs

Please get a Windows SIG member to approve.

The following dif file shows any additions or deletions from what will be cached on windows VHDs organised by VHD type.

  • Additions are new things cached.
  • Deletions are things no longer cached.
diff --git a/vhd_files/2019-containerd.txt b/vhd_files/2019-containerd.txt
index 4bb5c69..5999f0c 100644
--- a/vhd_files/2019-containerd.txt
+++ b/vhd_files/2019-containerd.txt
@@ -56 +56 @@ mcr.microsoft.com/containernetworking/azure-cni:v1.5.44
-mcr.microsoft.com/containernetworking/azure-cni:v1.6.32
+mcr.microsoft.com/containernetworking/azure-cni:v1.6.35-0
@@ -59 +59 @@ mcr.microsoft.com/containernetworking/azure-cns:v1.5.49
-mcr.microsoft.com/containernetworking/azure-cns:v1.6.33
+mcr.microsoft.com/containernetworking/azure-cns:v1.6.35-0
diff --git a/vhd_files/2022-containerd-gen2.txt b/vhd_files/2022-containerd-gen2.txt
index 4ef305b..0257582 100644
--- a/vhd_files/2022-containerd-gen2.txt
+++ b/vhd_files/2022-containerd-gen2.txt
@@ -106 +106 @@ mcr.microsoft.com/containernetworking/azure-cni:v1.5.44
-mcr.microsoft.com/containernetworking/azure-cni:v1.6.32
+mcr.microsoft.com/containernetworking/azure-cni:v1.6.35-0
@@ -109 +109 @@ mcr.microsoft.com/containernetworking/azure-cns:v1.5.49
-mcr.microsoft.com/containernetworking/azure-cns:v1.6.33
+mcr.microsoft.com/containernetworking/azure-cns:v1.6.35-0
diff --git a/vhd_files/2022-containerd.txt b/vhd_files/2022-containerd.txt
index a6d61d8..06351fa 100644
--- a/vhd_files/2022-containerd.txt
+++ b/vhd_files/2022-containerd.txt
@@ -106 +106 @@ mcr.microsoft.com/containernetworking/azure-cni:v1.5.44
-mcr.microsoft.com/containernetworking/azure-cni:v1.6.32
+mcr.microsoft.com/containernetworking/azure-cni:v1.6.35-0
@@ -109 +109 @@ mcr.microsoft.com/containernetworking/azure-cns:v1.5.49
-mcr.microsoft.com/containernetworking/azure-cns:v1.6.33
+mcr.microsoft.com/containernetworking/azure-cns:v1.6.35-0
diff --git a/vhd_files/2025-gen2.txt b/vhd_files/2025-gen2.txt
index aa715fd..dfe2fe2 100644
--- a/vhd_files/2025-gen2.txt
+++ b/vhd_files/2025-gen2.txt
@@ -36 +36 @@ mcr.microsoft.com/containernetworking/azure-cni:v1.5.44
-mcr.microsoft.com/containernetworking/azure-cni:v1.6.32
+mcr.microsoft.com/containernetworking/azure-cni:v1.6.35-0
@@ -39 +39 @@ mcr.microsoft.com/containernetworking/azure-cns:v1.5.49
-mcr.microsoft.com/containernetworking/azure-cns:v1.6.33
+mcr.microsoft.com/containernetworking/azure-cns:v1.6.35-0
diff --git a/vhd_files/2025.txt b/vhd_files/2025.txt
index d9b00ac..63d9f58 100644
--- a/vhd_files/2025.txt
+++ b/vhd_files/2025.txt
@@ -36 +36 @@ mcr.microsoft.com/containernetworking/azure-cni:v1.5.44
-mcr.microsoft.com/containernetworking/azure-cni:v1.6.32
+mcr.microsoft.com/containernetworking/azure-cni:v1.6.35-0
@@ -39 +39 @@ mcr.microsoft.com/containernetworking/azure-cns:v1.5.49
-mcr.microsoft.com/containernetworking/azure-cns:v1.6.33
+mcr.microsoft.com/containernetworking/azure-cns:v1.6.35-0
diff --git a/vhd_files/23H2-gen2.txt b/vhd_files/23H2-gen2.txt
index 2b95911..018c4f4 100644
--- a/vhd_files/23H2-gen2.txt
+++ b/vhd_files/23H2-gen2.txt
@@ -56 +56 @@ mcr.microsoft.com/containernetworking/azure-cni:v1.5.44
-mcr.microsoft.com/containernetworking/azure-cni:v1.6.32
+mcr.microsoft.com/containernetworking/azure-cni:v1.6.35-0
@@ -59 +59 @@ mcr.microsoft.com/containernetworking/azure-cns:v1.5.49
-mcr.microsoft.com/containernetworking/azure-cns:v1.6.33
+mcr.microsoft.com/containernetworking/azure-cns:v1.6.35-0
diff --git a/vhd_files/23H2.txt b/vhd_files/23H2.txt
index 9dfd0f5..94a5a1f 100644
--- a/vhd_files/23H2.txt
+++ b/vhd_files/23H2.txt
@@ -56 +56 @@ mcr.microsoft.com/containernetworking/azure-cni:v1.5.44
-mcr.microsoft.com/containernetworking/azure-cni:v1.6.32
+mcr.microsoft.com/containernetworking/azure-cni:v1.6.35-0
@@ -59 +59 @@ mcr.microsoft.com/containernetworking/azure-cns:v1.5.49
-mcr.microsoft.com/containernetworking/azure-cns:v1.6.33
+mcr.microsoft.com/containernetworking/azure-cns:v1.6.35-0

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Azure CNI and CNS (Container Networking Service) components to version 1.6.35-0, aligning both networking components to the same version for compatibility.

Changes:

  • Updated azure-cni from v1.6.32 to v1.6.35-0 in both Windows and multi-architecture configurations
  • Updated azure-cns from v1.6.33 to v1.6.35-0 in both Windows and multi-architecture configurations

@rejain789 rejain789 changed the title Replace cni and cns versions with v1.6.35 chore(deps) Replace cni and cns versions with v1.6.35 Jan 30, 2026
@awesomenix awesomenix changed the title chore(deps) Replace cni and cns versions with v1.6.35 chore(deps): replace cni and cns versions with v1.6.35 Jan 31, 2026
@cameronmeissner cameronmeissner merged commit 0b7d41f into main Feb 4, 2026
46 of 52 checks passed
@cameronmeissner cameronmeissner deleted the jainriya/cns-cni-1.6.35 branch February 4, 2026 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

components This pull request updates cached components on Linux or Windows VHDs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments