chore(deps): update inspektor-gadget (minor)

[renovate]

This PR contains the following updates:

Package	Update	Change
ig	minor	0.54.1-6.azl3 → 0.55.0-1.azl3
ig	minor	0.54.1-ubuntu26.04u6 → 0.55.0-ubuntu26.04u1
ig	minor	0.54.1-ubuntu24.04u6 → 0.55.0-ubuntu24.04u1
ig	minor	0.54.1-ubuntu22.04u6 → 0.55.0-ubuntu22.04u1
ig	minor	0.54.1-ubuntu20.04u6 → 0.55.0-ubuntu20.04u1

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[Copilot]

Pull request overview

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Updates the recorded “ig” component versions for Ubuntu 20.04/22.04/24.04/26.04 in the shared components manifest.

Changes:

• Bump ig latestVersion from 0.54.1-...u5 to 0.55.0-...u1 for Ubuntu 20.04, 22.04, 24.04, and 26.04.

[github-actions]

Windows Unit Test Results

  3 files   12 suites   54s ⏱️
389 tests 389 ✅ 0 💤 0 ❌
392 runs  392 ✅ 0 💤 0 ❌

Results for commit b2953c4.

♻️ This comment has been updated with latest results.

[aks-node-assistant]

TL;DR: PR gate build 175695612 failed multiple Linux VHD Build VHD jobs on the recurring inspektor-gadget component version skew signature.

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=175695612
Failed job/stage/task: build2204arm64gen2containerd, build2204gen2containerd, build2604minimalgen2containerd / Build VHD / Test-Scan-Cleanup artifact publish.
Signature: inspektor-gadget-ig-ig-gadgets-upstream-mismatch.
First failing step: Build VHD exits 2 repeatedly; downstream disk-usage.txt and bcc-tools-installation.log publish failures are collateral because the VHD jobs did not complete normally.
Likely root cause: PR-change-caused component dependency skew: this PR updates inspektor-gadget to 0.55.0 while existing AzureLinux entries still include 0.54.1, matching the existing gate signature.
Assessment: PR-change-caused dependency/package regression is more likely than infra, test-code, CSE/provisioning, or Packer image-generation flake because the same signature recurs on inspektor-gadget update PRs and impacts multiple OS jobs consistently.
Confidence: high.
Strongest alternative: transient package fetch/build infra failure; less likely because retries repeat the same Build VHD exit path across several jobs and the PR changes only inspektor-gadget component metadata.
Recommended owner/action: PR author/AgentBaker VHD component owner should align ig and ig-gadgets/upstream versions across all OS entries, then rerun the gate.
Evidence: build summary, failed Build VHD job logs, retry history, PR changed files.
Wiki: inspektor-gadget-ig-ig-gadgets-upstream-mismatch (https://dev.azure.com/msazure/09706533-03bf-4b43-9a9b-b49c75429646/_wiki/wikis/ed4a85e9-1085-4151-a39b-2753523eba2b?pagePath=%2fAKS%2fSIGs%20and%20Teams%2fAKS%20Components%2fSIG%3a%20Node%20Lifecycle%2fAI%20Agent%20Knowledge%2fAgentBaker%20Gate%20PR%20Pipeline%20Flakiness%2fNoisy%20Active%20Items)

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[aks-node-assistant]

🔍 AgentBaker Linux Gate Detective — Build 176009763

Failed job/stage: Multiple Build VHD jobs (stage: build) — 7 VHD flavors failed (build2604minimalgen2containerd, build2204gen2containerd, build2204arm64gen2containerd, buildAzureLinuxV3gen2, buildAzureLinuxV3ARM64gen2fips, build2004fipsgen2containerd, build2404gen2containerd)

TL;DR

All VHD builds fail during Packer provisioning because ig (0.55.0) and ig-gadgets (0.54.1) have mismatched upstream versions. This is a PR-change-caused failure: PR 9166 bumped ig in components.json but did not update ig-gadgets to match the same upstream version.

Failure Details

Primary failure	Build VHD — Packer provisioning exit 1: [ig] ig (0.55.0-ubuntu26.04u1) and ig-gadgets (0.54.1-ubuntu20.04u1) must share upstream version, found 0.55.0 vs 0.54.1
Signature ID	inspektor-gadget-ig-gadgets-version-skew
Classification	VHD build — dependency/package change-caused
Confidence	High — Packer provisioning script explicitly enforces upstream version parity between ig and ig-gadgets; PR 9166 changed ig version without ig-gadgets
Likely cause	components.json bumped ig to 0.55.0 but ig-gadgets remained at 0.54.1; VHD provisioning enforces upstream version parity
Strongest alternative	External package registry published a breaking ig-gadgets update concurrently — less likely given explicit mismatch cites PR-owned component versions
Recommended action	PR author: bump ig-gadgets in components.json to 0.55.x matching ig upstream, ensuring both share the same major.minor.patch

Evidence

• Build: 176009763 · 7 Build VHD tasks failed (exit code 2) · PR: #9166
• Packer log (e.g. Log 422): [ig] ig (0.55.0-ubuntu26.04u1) and ig-gadgets (0.54.1-ubuntu20.04u1) must share upstream version
• Multiple independent VHD flavors all hit identical error — confirms components.json-level issue, not per-distro flake
• Wiki: inspektor-gadget-ig-gadgets-version-skew

^{Automated analysis by Clawpilot AgentBaker Linux Gate Detective · Aug 11, 2026}

[Burak Ok (burak-ok)]

The ig-gadgets package always lags 1-3 days behind the ig package