Skip to content

chore(deps): update all-ci-updates#1859

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all-ci-updates
Open

chore(deps): update all-ci-updates#1859
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all-ci-updates

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Feb 3, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
actions/cache action patch v5.0.3v5.0.5
actions/setup-go action minor v6.2.0v6.4.0
argo-cd minor 9.3.79.5.0
cert-manager (source) minor v1.19.3v1.20.2
codecov/codecov-action action patch v5.5.2v5.5.4
fossas/fossa-action action minor v1.7.0v1.9.0
github/codeql-action action minor v4.32.1v4.35.1
kube-prometheus-stack (source) minor 81.4.281.6.9
pyroscope (source) minor 1.18.11.20.3
securego/gosec action minor v2.22.11v2.25.0
sigstore/cosign-installer action minor v4.0.0v4.1.1
zgosalvez/github-actions-ensure-sha-pinned-actions action patch v5.0.0v5.0.4

Release Notes

actions/cache (actions/cache)

v5.0.5

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.0.5

v5.0.4

Compare Source

actions/setup-go (actions/setup-go)

v6.4.0

Compare Source

What's Changed
Enhancement
  • Add go-download-base-url input for custom Go distributions by @​gdams in #​721
Dependency update
Documentation update
New Contributors

Full Changelog: actions/setup-go@v6...v6.4.0

v6.3.0

Compare Source

What's Changed

Full Changelog: actions/setup-go@v6...v6.3.0

argoproj/argo-helm (argo-cd)

v9.5.0

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

New Contributors

Full Changelog: argoproj/argo-helm@argo-cd-9.4.18...argo-cd-9.5.0

v9.4.18

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argo-workflows-1.0.7...argo-cd-9.4.18

v9.4.17

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argo-rollouts-2.40.9...argo-cd-9.4.17

v9.4.16

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argocd-image-updater-1.1.4...argo-cd-9.4.16

v9.4.15

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

New Contributors

Full Changelog: argoproj/argo-helm@argo-workflows-1.0.4...argo-cd-9.4.15

v9.4.14

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

  • fix(argo-cd): Omit runAsUser for dex when deployed on OpenShift by @​CLNRMN in #​3785

New Contributors

Full Changelog: argoproj/argo-helm@argo-workflows-1.0.3...argo-cd-9.4.14

v9.4.13

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argo-cd-9.4.12...argo-cd-9.4.13

v9.4.12

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

New Contributors

Full Changelog: argoproj/argo-helm@argo-cd-9.4.11...argo-cd-9.4.12

v9.4.11

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argocd-image-updater-1.1.3...argo-cd-9.4.11

v9.4.10

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argo-cd-9.4.9...argo-cd-9.4.10

v9.4.9

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argo-cd-9.4.8...argo-cd-9.4.9

v9.4.8

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argo-cd-9.4.7...argo-cd-9.4.8

v9.4.7

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

New Contributors

Full Changelog: argoproj/argo-helm@argo-cd-9.4.6...argo-cd-9.4.7

v9.4.6

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

New Contributors

Full Changelog: argoproj/argo-helm@argo-cd-9.4.5...argo-cd-9.4.6

v9.4.5

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

New Contributors

Full Changelog: argoproj/argo-helm@argo-cd-9.4.4...argo-cd-9.4.5

v9.4.4

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argo-cd-9.4.3...argo-cd-9.4.4

v9.4.3

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argo-workflows-0.47.4...argo-cd-9.4.3

v9.4.2

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argocd-image-updater-1.1.0...argo-cd-9.4.2

v9.4.1

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

New Contributors

Full Changelog: argoproj/argo-helm@argo-workflows-0.47.3...argo-cd-9.4.1

v9.4.0

Compare Source

A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.

What's Changed

Full Changelog: argoproj/argo-helm@argo-workflows-0.47.2...argo-cd-9.4.0

cert-manager/cert-manager (cert-manager)

v1.20.2

Compare Source

v1.20.2 fixes invalid YAML generated in the Helm chart when both webhook.config
and webhook.volumes are defined, and bumps Go to 1.26.2 along with dependencies
to address reported vulnerabilities.

Changes by Kind

Bug or Regression
Other (Cleanup or Flake)

v1.20.1

Compare Source

v1.20.0

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

v1.20.0 adds alpha support for the new ListenerSet resource, adds support for Azure Private DNS; parentRefs are no longer required when using ACME with Gateway API, and OtherNames was promoted to Beta.

Changes by Kind

Feature
  • Added a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. (#​8370, @​jcpunk)
  • Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} (#​8256, @​tareksha)
  • Added support for specifying imagePullSecrets in the startupapicheck-job Helm template to enable pulling images from private registries. (#​8186, @​mathieu-clnk)
  • Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. (#​8355, @​dancmeyers)
  • Added parentRef override annotations on the Certificate resource. (#​8518, @​hjoshi123)
  • Added support for azure private zones for dns01 issuer. (#​8494, @​hjoshi123)
  • Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. (#​7642, @​robertlestak)
  • Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget (#​7728, @​jcpunk)
  • For Venafi provider, read venafi.cert-manager.io/custom-fields annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. (#​8301, @​k0da)
  • Improve error message when CA issuers are misconfigured to use a clashing secret name (#​8374, @​majiayu000)
  • Introduce a new Ingress annotation acme.cert-manager.io/http01-ingress-ingressclassname to override http01.ingress.ingressClassName field in HTTP-01 challenge solvers. (#​8244, @​lunarwhite)
  • Update global.nodeSelector to helm chart to perform a merge and allow for a single nodeSelector to be set across all services. (#​8195, @​StingRayZA)
  • Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. (#​8228, @​terinjokes)
  • Added experimental XListenerSets feature gate (#​8394, @​hjoshi123)
Documentation
Bug or Regression
  • Adds logs for cases when acme server returns us a fatal error in the order controller (#​8199, @​Peac36)
  • Fixed an issue where kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#​8160, @​inteon)
  • Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. (#​8232, @​eleanor-merry)
  • Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. (#​8456, @​tkna)
  • Fix unregulated retries with the DigitalOcean DNS-01 solver
    Add full detailed DNS-01 errors to the events attached to the Challenge, for easier debugging (#​8221, @​wallrj-cyberark)
  • Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. (#​8403, @​calm329)
  • Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#​8424, @​SlashNephy)
  • Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. (#​8443, @​alviss7)
  • Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#​8173, @​erikgb)
  • Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. (#​8469, @​SgtCoDFish)
  • Update Go to v1.25.5 to fix CVE-2025-61727 and CVE-2025-61729 (#​8290, @​octo-sts[bot])
  • When Prometheus monitoring is enabled, the metrics label is now set to the intended value of cert-manager. Previously, it was set depending on various factors (namespace cert-manager is installed in and/or Helm release name). (#​8162, @​LiquidPL)
Other (Cleanup or Flake)

v1.19.4

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

v1.19.4 is a simple patch release to fix some reported vulnerabilities - notably CVE-2026-24051 and CVE-2025-68121. All users should upgrade.

Changes by Kind
Bug or Regression
codecov/codecov-action (codecov/codecov-action)

v5.5.4

Compare Source

This is a mirror of v5.5.2. v6 will be released which requires node24

What's Changed

Full Changelog: codecov/codecov-action@v5.5.3...v5.5.4

v5.5.3

Compare Source

What's Changed

Full Changelog: codecov/codecov-action@v5.5.2...v5.5.3

fossas/fossa-action (fossas/fossa-action)

v1.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: fossas/fossa-action@v1.8.0...v1.9.0

v1.8.0

Compare Source

github/codeql-action (github/codeql-action)

v4.35.1

Compare Source

v4.35.0

Compare Source

v4.34.1

Compare Source

  • Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #​3762

v4.34.0

Compare Source

  • Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #​3569
  • We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #​3584
  • Update default CodeQL bundle version to 2.25.0. #​3585

v4.33.0

Compare Source

  • Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #​3562

    To opt out of this change:

    • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #​3557

  • The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #​3559

  • Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #​3563

  • Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #​3564

  • A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #​3570

v4.32.6

Compare Source

v4.32.5

Compare Source

  • Repositories owned by an organization can now set up the github-codeql-disable-overlay custom repository property to disable improved incremental analysis for CodeQL. First, create a custom repository property with the name github-codeql-disable-overlay and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to true to disable improved incremental analysis. For more information, see Managing custom properties for repositories in your organization. This feature is not yet available on GitHub Enterprise Server. #​3507
  • Added an experimental change so that when improved incremental analysis fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. #​3487
  • The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. #​3515
  • Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. #​3516
  • Added an experimental change which lowers the minimum disk space requirement for improved incremental analysis, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. #​3498
  • Added an experimental change which allows the start-proxy action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. #​3512
  • The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. #​3503, #​3504

v4.32.4

Compare Source

  • Update default CodeQL bundle version to 2.24.2. #​3493
  • Added an experimental change which improves how certificates are generated for the authentication proxy that is used by the CodeQL Action in Default Setup when private package registries are configured. This is expected to generate more widely compatible certificates and should have no impact on analyses which are working correctly already. We expect to roll this change out to everyone in February. #​3473
  • When the CodeQL Action is run with debugging enabled in Default Setup and private package registries are configured, the "Setup proxy for registries" step will output additional diagnostic information that can be used for troubleshooting. #​3486
  • Added a setting which allows the CodeQL Action to enable network debugging for Java programs. This will help GitHub staff support customers with troubleshooting issues in GitHub-managed CodeQL workflows, such as Default Setup. This setting can only be enabled by GitHub staff. #​3485
  • Added a setting which enables GitHub-managed workflows, such as Default Setup, to use a nightly CodeQL CLI release instead of the latest, stable release that is used by default. This will help GitHub staff support customers whose analyses for a given repository or organization require early access to a change in an upcoming CodeQL CLI release. This setting can only be enabled by GitHub staff. #​3484

v4.32.3

Compare Source

  • Added experimental support for testing connections to private package registries. This feature is not currently enabled for any analysis. In the future, it may be enabled by default for Default Setup. #​3466

v4.32.2

Compare Source

prometheus-community/helm-charts (kube-prometheus-stack)

v81.6.9

Compare Source

kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

What's Changed

Full Changelog: prometheus-community/helm-charts@kube-prometheus-stack-81.6.8...kube-prometheus-stack-81.6.9

v81.6.8

Compare Source

kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

What's Changed

Full Changelog: prometheus-community/helm-charts@kube-prometheus-stack-81.6.7...kube-prometheus-stack-81.6.8

v81.6.7

Compare Source

kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

What's Changed

  • [kube-prometheus-stack] Update kube-prometheus-stack dependency non-major updates by @​renovate[bot] in #​6645

Full Changelog: prometheus-community/helm-charts@kube-prometheus-stack-81.6.6...kube-prometheus-stack-81.6.7

v81.6.6

Compare Source

kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

What's Changed

New Contributors

Full Changelog: prometheus-community/helm-charts@kube-prometheus-stack-81.6.5...kube-prometheus-stack-81.6.6

v81.6.5

Compare Source

kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

What's Changed

  • [kube-prometheus-stack] Update ghcr.io/jkroepke/kube-webhook-certgen Docker tag to v1.7.7 by @​renovate[bot] in #​6642

Full Changelog: prometheus-community/helm-charts@prometheus-operator-admission-webhook-0.36.2...kube-prometheus-stack-81.6.5

[v81.6.4](https://redirect.github.com/prometheus-community/helm-charts/releases/tag/kube-prometheus-stack-81


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.

👻 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.

@renovate renovate bot added the renovate label Feb 3, 2026
@codecov
Copy link
Copy Markdown

codecov bot commented Feb 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 11.58%. Comparing base (0744924) to head (bcb4cdb).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1859      +/-   ##
==========================================
+ Coverage   11.56%   11.58%   +0.01%     
==========================================
  Files         248      248              
  Lines       11405    11405              
==========================================
+ Hits         1319     1321       +2     
+ Misses      10041    10040       -1     
+ Partials       45       44       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot force-pushed the renovate/all-ci-updates branch from d877ca3 to 86e21d8 Compare February 3, 2026 08:45
@renovate renovate bot changed the title chore(deps): update helm release argo-cd to v9.4.0 chore(deps): update all-ci-updates Feb 3, 2026
@renovate renovate bot force-pushed the renovate/all-ci-updates branch 6 times, most recently from ab312f3 to 1298913 Compare February 10, 2026 06:11
Copilot AI review requested due to automatic review settings February 10, 2026 06:11
Copy link
Copy Markdown

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.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 1298913 to 29746f8 Compare February 10, 2026 14:13
Copilot AI review requested due to automatic review settings February 11, 2026 13:47
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 29746f8 to 85fb4f9 Compare February 11, 2026 13:47
Copy link
Copy Markdown

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.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@renovate renovate bot force-pushed the renovate/all-ci-updates branch 2 times, most recently from afb89d0 to a93eca1 Compare February 12, 2026 09:32
Copilot AI review requested due to automatic review settings February 12, 2026 09:32
Copy link
Copy Markdown

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.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@renovate renovate bot force-pushed the renovate/all-ci-updates branch 2 times, most recently from b230f2c to 77a997a Compare February 13, 2026 02:46
@renovate renovate bot requested review from Copilot and removed request for Copilot February 13, 2026 02:46
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 77a997a to 4e4eed2 Compare February 13, 2026 05:33
@renovate renovate bot requested review from Copilot and removed request for Copilot February 13, 2026 05:33
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 4e4eed2 to 838e439 Compare February 13, 2026 14:14
@renovate renovate bot review requested due to automatic review settings February 13, 2026 14:14
Copilot AI review requested due to automatic review settings February 21, 2026 01:13
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 4bb04db to dc422bc Compare February 21, 2026 01:13
@renovate renovate bot review requested due to automatic review settings February 21, 2026 01:13
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from dc422bc to 8bd5026 Compare February 22, 2026 20:46
@renovate renovate bot requested review from Copilot and removed request for Copilot February 22, 2026 20:46
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 8bd5026 to 2044a0b Compare February 24, 2026 19:47
@renovate renovate bot requested review from Copilot and removed request for Copilot February 24, 2026 19:47
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 2044a0b to 63bad14 Compare March 1, 2026 08:08
@renovate renovate bot requested review from Copilot and removed request for Copilot March 1, 2026 08:08
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 63bad14 to ce82372 Compare March 1, 2026 20:37
@renovate renovate bot review requested due to automatic review settings March 1, 2026 20:37
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from ce82372 to 013b2fe Compare March 2, 2026 13:42
@renovate renovate bot requested review from Copilot and removed request for Copilot March 2, 2026 13:42
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 013b2fe to 387106c Compare March 2, 2026 22:33
@renovate renovate bot requested review from Copilot and removed request for Copilot March 2, 2026 22:33
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 387106c to de5de61 Compare March 3, 2026 14:36
@renovate renovate bot review requested due to automatic review settings March 3, 2026 14:36
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from de5de61 to 40739aa Compare March 5, 2026 22:56
@renovate renovate bot requested review from Copilot and removed request for Copilot March 5, 2026 22:56
@renovate renovate bot force-pushed the renovate/all-ci-updates branch from 40739aa to 8e0d477 Compare March 7, 2026 02:51
Copilot AI review requested due to automatic review settings March 7, 2026 02:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant