Skip to content

chore(deps): Update testing-tools#1027

Merged
mchmarny merged 2 commits into
mainfrom
renovate/testing-tools
May 27, 2026
Merged

chore(deps): Update testing-tools#1027
mchmarny merged 2 commits into
mainfrom
renovate/testing-tools

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
fluxcd/flux2 testing_tools patch v2.8.7v2.8.8
helmfile/helmfile testing_tools patch v1.5.1v1.5.2

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

fluxcd/flux2 (fluxcd/flux2)

v2.8.8

Compare Source

Highlights

Flux v2.8.8 is a patch release that includes CVE fixes via go-git v5.19.1 (source-controller, image-automation-controller), reliability fixes in helm-controller and source-controller, the move of Helm back to upstream v4.2.0, support for GCP sovereign cloud artifact registries, and dependency updates. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Fixes:

  • Add a configurable HTTP timeout for artifact fetching, preventing fetches that could block indefinitely and stall reconciliations (helm-controller)
  • Fix unbounded memory growth caused by a Kubernetes client transport retry wrapper accumulating on every reconcile (helm-controller)
  • Stop force-applying non-CRD objects placed under a chart's crds/ directory (helm-controller)
  • Fix the Helm test action failing to find releases with names longer than 53 characters (helm-controller)
  • Improve path handling in the source reconcilers (source-controller)
  • Support Helm semver build-metadata encoding in OCIRepository tags (source-controller)

Improvements:

  • Update go-git to v5.19.1 which fixes CVE-2026-45571 and CVE-2026-45570 (source-controller, image-automation-controller)
  • Move Helm back to upstream v4.2.0 (source-controller, helm-controller)
  • Add support for GCP sovereign cloud artifact registries (source-controller, image-reflector-controller)
  • Upgrade Kubernetes to 1.36.1 (source-controller, helm-controller)
  • Update fluxcd/pkg dependencies

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.7...v2.8.8

helmfile/helmfile (helmfile/helmfile)

v1.5.2

Compare Source

What's Changed

New Contributors

Full Changelog: helmfile/helmfile@v1.5.1...v1.5.2


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: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.

@github-actions github-actions Bot requested a review from a team as a code owner May 25, 2026 06:30
@github-actions github-actions Bot added dependencies Pull requests that update a dependency file renovate labels May 25, 2026
@github-actions
Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: .settings.yaml
Post-upgrade command './tools/update-helmfile-checksums v1.5.2' has not been added to the allowed list in allowedCommands

@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot Bot commented May 25, 2026

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.

@github-actions github-actions Bot force-pushed the renovate/testing-tools branch from 5e428d3 to bbf596b Compare May 27, 2026 06:29
@mchmarny mchmarny merged commit 6ab97f1 into main May 27, 2026
19 of 21 checks passed
@mchmarny mchmarny deleted the renovate/testing-tools branch May 27, 2026 11:13
@github-actions
Copy link
Copy Markdown
Contributor Author

Coverage Report ✅

Metric Value
Coverage 77.0%
Threshold 75%
Status Pass
Coverage Badge
![Coverage](https://img.shields.io/badge/coverage-77.0%25-green)

No Go source files changed in this PR.

mchmarny added a commit that referenced this pull request May 27, 2026
PR #1027 bumped testing_tools.helmfile v1.5.1 -> v1.5.2 but the
Renovate postUpgradeTask that refreshes helmfile_checksums did not
run, leaving the four per-arch SHA256 entries pinned at v1.5.1
values. Both .github/actions/install-e2e-tools (via tools/setup-tools)
and .github/actions/setup-build-tools verify the downloaded helmfile
tarball against these pinned checksums, so E2E and CLI E2E started
failing on every PR rebased onto main after #1027 merged (PR #1040
and others).

Refresh the four checksums by running
tools/update-helmfile-checksums v1.5.2, which is the same script the
Renovate postUpgradeTask invokes. No other code or doc references
the stale digests.
mchmarny added a commit that referenced this pull request May 27, 2026
RENOVATE_ALLOWED_POST_UPGRADE_COMMANDS only matched the chainsaw
checksum refresh script, so Renovate silently refused to run the
helmfile postUpgradeTask defined in .github/renovate.json5. The bump
in #1027 advanced testing_tools.helmfile from v1.5.1 to v1.5.2 while
leaving testing_tools.helmfile_checksums pinned at v1.5.1 values,
which broke E2E and CLI E2E for every PR rebased onto main (already
fixed at runtime in 2cd479f).

Replace the chainsaw-specific regex with a pattern matching every
tools/update-*-checksums script. The two existing scripts
(update-chainsaw-checksums, update-helmfile-checksums) share an
identical shape: fetch the upstream release's checksums.txt and
rewrite the per-arch block in .settings.yaml. Future per-arch
checksum-pinned dependencies follow the same pattern, so a broader
regex eliminates the dual-edit failure mode without widening the
trust boundary beyond "checksum-refresher scripts we author".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file renovate size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant