Skip to content

chore(deps): update ghcr.io/fluxcd/source-controller docker tag to v1.9.2#232

Open
Varashi wants to merge 1 commit into
mainfrom
renovate/ghcr.io-fluxcd-source-controller-1.x
Open

chore(deps): update ghcr.io/fluxcd/source-controller docker tag to v1.9.2#232
Varashi wants to merge 1 commit into
mainfrom
renovate/ghcr.io-fluxcd-source-controller-1.x

Conversation

@Varashi

@Varashi Varashi commented Jun 17, 2026

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Update Change
ghcr.io/fluxcd/source-controller minor v1.8.5v1.9.2

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

fluxcd/source-controller (ghcr.io/fluxcd/source-controller)

v1.9.2

Compare Source

Changelog

v1.9.2 changelog

Container images

  • docker.io/fluxcd/source-controller:v1.9.2
  • ghcr.io/fluxcd/source-controller:v1.9.2

Supported architectures: linux/amd64, linux/arm64 and linux/arm/v7.

The container images are built on GitHub hosted runners and are signed with cosign and GitHub OIDC.
To verify the images and their provenance (SLSA level 3), please see the security documentation.

v1.9.1

Compare Source

Changelog

v1.9.1 changelog

Container images

  • docker.io/fluxcd/source-controller:v1.9.1
  • ghcr.io/fluxcd/source-controller:v1.9.1

Supported architectures: linux/amd64, linux/arm64 and linux/arm/v7.

The container images are built on GitHub hosted runners and are signed with cosign and GitHub OIDC.
To verify the images and their provenance (SLSA level 3), please see the security documentation.

v1.9.0

Compare Source

Changelog

v1.9.0 changelog

Container images

  • docker.io/fluxcd/source-controller:v1.9.0
  • ghcr.io/fluxcd/source-controller:v1.9.0

Supported architectures: linux/amd64, linux/arm64 and linux/arm/v7.

The container images are built on GitHub hosted runners and are signed with cosign and GitHub OIDC.
To verify the images and their provenance (SLSA level 3), please see the security documentation.


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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate.

@coderabbitai

coderabbitai Bot commented Jun 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Varashi, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 2f938917-62d7-4540-92fc-61a8bf5ce68f

📥 Commits

Reviewing files that changed from the base of the PR and between 966823a and 07b8899.

📒 Files selected for processing (1)
  • cluster-talos/kubernetes/bootstrap/flux-system/gotk-components.yaml

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Jun 17, 2026

Copy link
Copy Markdown

kustomization diff:

--- cluster-talos/kubernetes/bootstrap Kustomization: flux-system/flux-system Deployment: flux-system/source-controller

+++ cluster-talos/kubernetes/bootstrap Kustomization: flux-system/flux-system Deployment: flux-system/source-controller

@@ -47,13 +47,13 @@

           value: /tmp/.sigstore
         - name: GOMEMLIMIT
           valueFrom:
             resourceFieldRef:
               containerName: manager
               resource: limits.memory
-        image: ghcr.io/fluxcd/source-controller:v1.8.5
+        image: ghcr.io/fluxcd/source-controller:v1.9.2
         imagePullPolicy: IfNotPresent
         livenessProbe:
           httpGet:
             path: /healthz
             port: healthz
         name: manager

@Varashi Varashi force-pushed the renovate/ghcr.io-fluxcd-source-controller-1.x branch from 2e41973 to 28790b4 Compare June 30, 2026 18:02
@Varashi Varashi changed the title chore(deps): update ghcr.io/fluxcd/source-controller docker tag to v1.9.0 chore(deps): update ghcr.io/fluxcd/source-controller docker tag to v1.9.1 Jun 30, 2026
@Varashi Varashi force-pushed the renovate/ghcr.io-fluxcd-source-controller-1.x branch from 28790b4 to 07b8899 Compare July 7, 2026 12:02
@Varashi Varashi changed the title chore(deps): update ghcr.io/fluxcd/source-controller docker tag to v1.9.1 chore(deps): update ghcr.io/fluxcd/source-controller docker tag to v1.9.2 Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant