Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package kargo-cli for openSUSE:Factory 
checked in at 2026-02-03 21:29:28
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/kargo-cli (Old)
 and      /work/SRC/openSUSE:Factory/.kargo-cli.new.1995 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "kargo-cli"

Tue Feb  3 21:29:28 2026 rev:44 rq:1330419 version:1.9.2

Changes:
--------
--- /work/SRC/openSUSE:Factory/kargo-cli/kargo-cli.changes      2026-02-02 
14:56:34.706028465 +0100
+++ /work/SRC/openSUSE:Factory/.kargo-cli.new.1995/kargo-cli.changes    
2026-02-03 21:30:55.511200534 +0100
@@ -1,0 +2,10 @@
+Mon Feb 02 13:47:50 UTC 2026 - Johannes Kastl 
<[email protected]>
+
+- Update to version 1.9.2:
+  no CLI-related changes
+  Dependencies:
+  * chore(backport release-1.9): chore(deps): bump
+    github.com/golang-jwt/jwt/v5 from 5.3.0 to 5.3.1 in the
+    go-patch group (#5694)
+
+-------------------------------------------------------------------

Old:
----
  kargo-cli-1.9.1.obscpio

New:
----
  kargo-cli-1.9.2.obscpio

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ kargo-cli.spec ++++++
--- /var/tmp/diff_new_pack.R04T1l/_old  2026-02-03 21:30:57.835298865 +0100
+++ /var/tmp/diff_new_pack.R04T1l/_new  2026-02-03 21:30:57.839299035 +0100
@@ -19,7 +19,7 @@
 %define executable_name kargo
 
 Name:           kargo-cli
-Version:        1.9.1
+Version:        1.9.2
 Release:        0
 Summary:        CLI for the Kubernetes Application lifecycle orchestration
 License:        Apache-2.0

++++++ _service ++++++
--- /var/tmp/diff_new_pack.R04T1l/_old  2026-02-03 21:30:57.923302589 +0100
+++ /var/tmp/diff_new_pack.R04T1l/_new  2026-02-03 21:30:57.931302927 +0100
@@ -3,7 +3,7 @@
     <param name="url">https://github.com/akuity/kargo</param>
     <param name="scm">git</param>
     <param name="exclude">.git</param>
-    <param name="revision">v1.9.1</param>
+    <param name="revision">v1.9.2</param>
     <param name="versionformat">@PARENT_TAG@</param>
     <param name="versionrewrite-pattern">v(.*)</param>
     <param name="changesgenerate">enable</param>

++++++ _servicedata ++++++
--- /var/tmp/diff_new_pack.R04T1l/_old  2026-02-03 21:30:57.979304958 +0100
+++ /var/tmp/diff_new_pack.R04T1l/_new  2026-02-03 21:30:57.991305466 +0100
@@ -1,6 +1,6 @@
 <servicedata>
 <service name="tar_scm">
                 <param name="url">https://github.com/akuity/kargo</param>
-              <param 
name="changesrevision">e594e1508d679aff1a64961cd59cd87a6fb1a6f9</param></service></servicedata>
+              <param 
name="changesrevision">141a6cd104f855d404119b78c5ae2646c66ea9e4</param></service></servicedata>
 (No newline at EOF)
 

++++++ kargo-cli-1.9.1.obscpio -> kargo-cli-1.9.2.obscpio ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/kargo-cli-1.9.1/charts/kargo/templates/api/configmap.yaml 
new/kargo-cli-1.9.2/charts/kargo/templates/api/configmap.yaml
--- old/kargo-cli-1.9.1/charts/kargo/templates/api/configmap.yaml       
2026-01-31 03:11:53.000000000 +0100
+++ new/kargo-cli-1.9.2/charts/kargo/templates/api/configmap.yaml       
2026-02-02 13:44:17.000000000 +0100
@@ -23,6 +23,7 @@
   SECRET_MANAGEMENT_ENABLED: "true"
   {{- end }}
   SYSTEM_RESOURCES_NAMESPACE: {{ quote 
.Values.global.systemResources.namespace }}
+  SHARED_RESOURCES_NAMESPACE: {{ quote 
.Values.global.sharedResources.namespace }}
   PERMISSIVE_CORS_POLICY_ENABLED: {{ quote 
.Values.api.permissiveCORSPolicyEnabled }}
   {{- if .Values.api.adminAccount.enabled }}
   ADMIN_ACCOUNT_ENABLED: "true"
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/kargo-cli-1.9.1/docs/docs/100-roadmap.md 
new/kargo-cli-1.9.2/docs/docs/100-roadmap.md
--- old/kargo-cli-1.9.1/docs/docs/100-roadmap.md        2026-01-31 
03:11:53.000000000 +0100
+++ new/kargo-cli-1.9.2/docs/docs/100-roadmap.md        2026-02-02 
13:44:17.000000000 +0100
@@ -29,28 +29,35 @@
 
 ## In Progress
 
-### v1.9.0
+### v1.10.0
 
-__Expected:__ November, 2025
+**Expected:** TBD
 
-This release is focused on:
+* UI to begin transition to new API
 
-* Facilitating external automation and other integrations via Kargo-managed
-  service accounts.
-* Improving Warehouse performance through more aggressive caching.
-* Relieving confusion over "global" vs "cluster-scoped" credentials and other
-  Secrets through careful, minimally breaking refactoring.
-* Extending webhook compatibility to unspecified repository hosts via a generic
-  webhook receiver.
+* Remaining scope TBD
 
-### v1.8.0
+## Completed
 
-__Expected:__ October, 2025
+### v1.9.0
 
-This release is focused on UI enhancements and general "quality-of-life"
-improvements, but also boasts a grab bag of small features.
+Focused on stability, performance, and usability.
 
-## Completed
+Introduced:
+
+* A new, RESTful API
+* User-generated API tokens
+* Opt-in Warehouse caching
+* Configurable rate limits
+* Refined everything related to Secret/credentials management
+* A large slate of small
+
+See [release notes](./80-release-notes/90-v1.9.0.md) for full details.
+
+### v1.8.0
+
+This small release focused on UI enhancements and general "quality-of-life"
+improvements, as well as a grab bag of small features.
 
 ### v1.7.0
 
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/kargo-cli-1.9.1/docs/docs/80-release-notes/100-deprecations.md 
new/kargo-cli-1.9.2/docs/docs/80-release-notes/100-deprecations.md
--- old/kargo-cli-1.9.1/docs/docs/80-release-notes/100-deprecations.md  
2026-01-31 03:11:53.000000000 +0100
+++ new/kargo-cli-1.9.2/docs/docs/80-release-notes/100-deprecations.md  
2026-02-02 13:44:17.000000000 +0100
@@ -11,15 +11,19 @@
 
 ## Deprecations
 
-The table below summarizes features that have been deprecated and either 
removed or scheduled for removal.
+The table below summarizes features that have been deprecated and either 
removed
+or scheduled for removal.
 
 | Feature | Deprecated In | Removed In | Replacement/Notes |
 |---------|---------------|------------|-------------------|
-| `Warehouse`'s container image subscription's `semverConstraint` field | 
[v1.7.0](./92-v1.7.0.md#new-deprecations) | Scheduled for v1.9.0 | Users should 
migrate to using the [`constraint 
field`](https://docs.kargo.io/user-guide/how-to-guides/working-with-warehouses/#image-selection-strategies)
 field which accepts the same value but is named to better indicate it can also 
be used for tag selection (e.g. `latest`) when the image selection strategy is 
set to `Digest`. |
+| The Connect-based API | [v1.9.0](./90-v1.9.0.md) | Scheduled for v1.12.0 | A 
new, RESTful API has been introduced. Most users will not be impacted beyond 
simply needing to upgrade their CLI when upgrading the back end to v1.9.0 or 
greater. |
+| "global credentials namespace(s)" | [v1.9.0](./90-v1.9.0.md) | Scheduled for 
v1.12.0 | Replaced with "shared secrets namespace." See [release 
notes](./90-v1.9.0.md#-the-secret-shuffle) and 
[docs](../40-operator-guide/40-security/40-managing-secrets.md#transitioning) 
for details. |
+| "cluster secrets namespace" | [v1.9.0](./90-v1.9.0.md) | Scheduled for 
v1.12.0 | Replaced with "system resources namespace." See [release 
notes](./90-v1.9.0.md#-the-secret-shuffle) and 
[docs](../40-operator-guide/40-security/40-managing-secrets.md#transitioning) 
for details. |
+| `Warehouse`'s container image subscription's `semverConstraint` field | 
[v1.7.0](./92-v1.7.0.md#new-deprecations) | [v1.9.0](./90-v1.9.0.md) | Users 
should migrate to using the 
[`constraint`](https://docs.kargo.io/user-guide/how-to-guides/working-with-warehouses/#image-selection-strategies)
 field which, accepts the same value but is named to better indicate it can 
also be used for tag selection (e.g. `latest`) when the image selection 
strategy is set to `Digest`. |
 | `Project` specification | [v1.5.0](./94-v1.5.0.md#new-deprecations) | 
[v1.7.0](./92-v1.7.0.md#breaking-changes) | Users should migrate to the 
dedicated [`ProjectConfig` 
resource](../50-user-guide/20-how-to-guides/20-working-with-projects.md#project-configuration).
 This resource kind accepts a `.spec` identitical to the `Project`, but allows 
for fine-grain permissions. |
 | `secrets` object in the Promotion variables | 
[v1.5.0](./94-v1.5.0.md#new-deprecations) | 
[v1.7.0](./92-v1.7.0.md#breaking-changes) | Users should migrate to the 
[`secret()` 
function](../50-user-guide/60-reference-docs/40-expressions.md#promotion-variables)
 which resolves Secrets on-demand, reducing overhead. |
 | `prNumber` field in `git-open-pr` Promotion Step output | 
[v1.5.0](./94-v1.5.0.md#new-deprecations) | 
[v1.7.0](./92-v1.7.0.md#breaking-changes) | Users should migrate to using [the 
`pr.id`](../50-user-guide/60-reference-docs/30-promotion-steps/git-open-pr.md#output)
 for referencing pull request IDs. |
-| `messageFromSteps` of `git-commit` Promotion Step | 
[v1.3.0](./96-v1.3.0.md#new-deprecations) | Scheduled for v1.5.0 | Use the 
`message` field in combination with expressions. Refer to the 
[documentation](https://main.docs.kargo.io/user-guide/reference-docs/promotion-steps/git-commit/#composed-commit-message)
 for more information. |
+| `messageFromSteps` of `git-commit` Promotion Step | 
[v1.3.0](./96-v1.3.0.md#new-deprecations) | [v1.5.0](./94-v1.5.0.md) | Use the 
`message` field in combination with expressions. Refer to the 
[documentation](https://main.docs.kargo.io/user-guide/reference-docs/promotion-steps/git-commit/#composed-commit-message)
 for more information. |
 | Promotion Steps Fields | 
[v1.1.0](./98-v1.1.0.md#new-and-updated-promotion-steps) | 
[v1.3.0](./96-v1.3.0.md#breaking-changes) | Several fields in promotion steps, 
such as `prNumberFromStep` in the `git-wait-for-pr` step, are now deprecated. 
These fields were originally the only way to reference output from previous 
promotion steps. With the introduction of expressions, these fields have 
outlived their purpose, as expressions like `${{ outputs['open-pr'].pr.id }}` 
present a more flexible and straightforward way to reference the same output. 
[more info](./98-v1.1.0.md#new-and-updated-promotion-steps) |
 | `helm-update-image` step | 
[v1.1.0](./98-v1.1.0.md#new-and-updated-promotion-steps) | 
[v1.3.0](./96-v1.3.0.md#breaking-changes) | Use the more flexible `yaml-update` 
step. [more info](./98-v1.1.0.md#new-and-updated-promotion-steps) |
 | Legacy Promotion Mechanisms | v0.9.0 | 
[v1.0.0](./99-v1.0.0.md#breaking-changes) | Migrate to promotion steps. [more 
info](./99-v1.0.0.md#breaking-changes) |
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' 
old/kargo-cli-1.9.1/docs/docs/80-release-notes/90-v1.9.0.md 
new/kargo-cli-1.9.2/docs/docs/80-release-notes/90-v1.9.0.md
--- old/kargo-cli-1.9.1/docs/docs/80-release-notes/90-v1.9.0.md 1970-01-01 
01:00:00.000000000 +0100
+++ new/kargo-cli-1.9.2/docs/docs/80-release-notes/90-v1.9.0.md 2026-02-02 
13:44:17.000000000 +0100
@@ -0,0 +1,216 @@
+πŸš€ Our most significant release since v1.0.0. Although feature-packed, this
+release focuses heavily on improving performance, stability, and overall user
+experience.
+
+## 🚨 Breaking Changes {#breaking-changes}
+
+* The `SemVerConstraint` field, deprecated in v1.7, has been removed. Use the
+  
[`constraint`](https://docs.kargo.io/user-guide/how-to-guides/working-with-warehouses/#image-selection-strategies)
+  field instead.
+
+* **CLI Upgrade Required:** Due to unavoidable breaking changes in how
+  `Warehouse` and `Freight` types are serialized as protocol buffers, users
+  upgrading the Kargo back end to v1.9.0 **must** also
+  [upgrade their CLI](https://github.com/akuity/kargo/releases/tag/v1.9.0).
+
+## ⚠️ New Deprecations {#new-deprecations}
+
+* The Connect-based API is deprecated in favor of a new, RESTful API. The older
+  API will be removed entirely in Kargo v1.12.0.
+  [The New REST API](#the-new-rest-api) section below has further details.
+
+* **Image and Commit Tag Filtering**: The `allowTags` and `ignoreTags` fields
+  are deprecated in favor of
+  [`allowTagsRegexes` and 
`ignoreTagsRegexes`](https://docs.kargo.io/user-guide/how-to-guides/working-with-warehouses#allow-tags-regexes-constraint).
+  Artifact discovery will fail if the deprecated fields are non-empty beginning
+  in v1.11.0. These fields will be removed in v1.13.0.
+
+## πŸ’ͺ Big Changes {#big-changes}
+
+### πŸ•ΊπŸ» The Secret Shuffle {#the-secret-shuffle}
+
+Users have been confused by the proper use of "global credentials namespace(s)"
+and the "cluster secrets namespace." To resolve this, v1.9.0 institutes changes
+in terminology:
+
+* **Shared resources namespace** (replaces "global credentials namespace(s)"):
+  The place to store resources (like repository credentials) available to all
+  Projects. "Shared" signals that anything here is accessible by all Projects.
+
+* **System resources namespace** (replaces "cluster secrets namespace"): The
+  place to store namespaced resources referenced by cluster-scoped 
configuration
+  (`ClusterConfig`). "System" signals this is private property of the operator;
+  not for sharing.
+
+Refer to the 
[documentation](https://docs.kargo.io/operator-guide/security/managing-secrets)
+for further details.
+
+#### Transitioning
+
+In conjunction with the terminology change, the default namespaces for shared
+and system resources are changing accordingly to: `kargo-shared-resources` and
+`kargo-system-resources`. These are overridable at install/upgrade time, 
meaning
+it's possible to simply set them to their legacy values if you wish.
+
+Kargo v1.9.0 automatically migrates `Secret`s from old to new locations (if 
they
+differ):
+
+* **Kargo Enterprise users**: Unaffected.
+* **Multiple global credentials namespaces configured**: Manual consolidation
+  required before upgrade (automated migration cannot resolve name conflicts).
+* **Fresh installs**: No action needed.
+* **"Clickops" users**: No action needed.
+* **"GitOps" users**: No immediate action required. Continue syncing to 
original
+  locations; Kargo will sync to new locations. **The migration tool will be
+  removed in v1.11.0** -- update your manifests before then.
+
+#### πŸ–₯️ Better UI and CLI Support {#better-ui-and-cli-support}
+
+The UI and CLI now have improved support for managing shared and system-level
+resources, including `ConfigMap`s.
+
+### πŸ’€ The New REST API {#the-new-rest-api}
+
+Breaking changes in Kubernetes v1.35 make it difficult to represent Kubernetes
+resource types, including our own CRDs, as protocol buffers, which 
Connect-based
+APIs require. Beginning with Kubernetes v1.36, it will be impossible. This
+currently prevents Kargo from upgrading its Kubernetes dependencies beyond
+v1.34.x.
+
+To resolve this, v1.9.0 introduces a new RESTful API as an eventual replacement
+for the legacy, Connect-based API. The legacy API will continue to be served
+alongside its replacement through v1.11.x. It will be removed in v1.12.0, at
+which time Kargo can resume freely updating its Kubernetes dependencies.
+
+The CLI already uses the new REST API. By transitioning now (when a CLI upgrade
+is already required), we avoid forcing another upgrade when the legacy API is
+removed. The new API is also significantly easier to integrate with using 
`curl`
+or clients generated from `swagger.json`.
+
+The UI continues to use the legacy API at this time.
+
+## ✨ Other Noteworthy Features {#other-noteworthy-features}
+
+### πŸ”‘ API Tokens {#api-tokens}
+
+Provision API tokens (JWTs) via UI or CLI, associated with system-level or
+Project-level roles. Tokens are easily used with the `kargo` CLI and `curl`.
+Refer to the
+[documentation](https://docs.kargo.io/user-guide/security/api-tokens) for 
details.
+
+### πŸ“¦ Warehouse Performance {#warehouse-performance}
+
+Two new optimizations address the pain of slow container image discovery caused
+by registry rate limits:
+
+* **Opt-in metadata caching:** Docker tags are mutable, which until now has
+  prevented safely caching image metadata by tag. Now, individual `Warehouse`
+  image repository subscriptions can opt-in to tag-based caching if not relying
+  in any way on mutable tags. Operators can set system-level policy to forbid,
+  allow, require, or force this caching. Refer to the
+  
[documentation](https://docs.kargo.io/user-guide/how-to-guides/working-with-warehouses#caching-image-metadata-by-tag)
+  for details.
+
+* **Configurable rate limits:** Kargo has historically enforced conservative
+  client-side rate limits. Operators can now tune this, though caution is
+  advised -- raising limits too high can degrade performance. This initial
+  implementation is system-wide and tunable in the chart; per-registry control
+  may come later.
+
+### πŸͺ The Generic Webhook Receiver {#the-generic-webhook-receiver}
+
+Not all artifact repositories support webhooks (notably ECR). The new generic
+webhook receiver is highly configurable, allowing users to describe how 
incoming
+requests should be parsed to trigger Warehouse refreshes. Refer to the
+[documentation](https://docs.kargo.io/user-guide/reference-docs/webhook-receivers/generic)
+for details.
+
+### Smaller Improvements
+
+* **Azure Container Registry Workload Identity**: Workload identity-based
+  authentication to ACR, though not as robust as GAR/ECR support due to Azure
+  complexities.
+  
([docs](https://docs.kargo.io/user-guide/security/managing-secrets#azure-container-registry-acr))
+
+* **Helm charts in GAR**: Warehouses can now subscribe to Helm charts in Google
+  Artifact Registry.
+  
([docs](https://docs.kargo.io/user-guide/how-to-guides/working-with-warehouses#helm-chart-repository-subscriptions))
+
+* **Alternative Expression Delimiters**: Use `${% %}` instead of `${{ }}` when
+  expressions contain closing braces (e.g., JSON objects).
+  ([docs](https://docs.kargo.io/user-guide/reference-docs/expressions#syntax))
+
+* **Semantic Version Parsing**: New `semverParse()` function breaks semver
+  strings into components.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/expressions#semverparseversion))
+
+* **Accessing Shared Resources**: New `sharedSecret()` and `sharedConfigMap()`
+  functions access resources from the shared namespace. `sharedSecret()` is
+  limited to "generic credentials" to prevent exposure of repository
+  credentials.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/expressions#functions))
+
+* **Live Log Streaming for Verifications**: View verification logs in near-real
+  time while in progress.
+  ([docs](https://docs.kargo.io/user-guide/how-to-guides/verification))
+
+### πŸͺœ New and Improved Promotion Steps {#new-and-improved-promotion-steps}
+
+* `git-clone`: Now supports sparse checkouts and submodules.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/git-clone))
+
+* `git-push`: Can force push (use with caution).
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/git-push))
+
+* `git-wait-for-pr`: PR links now visible in the UI.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/git-wait-for-pr))
+
+* `yaml-merge`: Merges multiple YAML files into one.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/yaml-merge))
+
+* `yaml-parse` / `json-parse`: Can now parse lists directly.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/yaml-parse),
+  
[docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/json-parse))
+
+* `helm-template`: New `ignoreMissingValueFiles` option; supports literal 
string
+  values.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/helm-template))
+
+* `kustomize-build`: New output formatting option.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/kustomize-build))
+
+* `http`: More flexible response body parsing.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/http))
+  
+* `argocd-update`: Now able to identify App(s) to update or sync based on 
labels.
+  
([docs](https://docs.kargo.io/user-guide/reference-docs/promotion-steps/argocd-update))
+
+## πŸ™ Special Thanks {#special-thanks}
+
+Thank you to community members who made their first contributions in this
+release or a recent v1.8 patch release!
+
+* @chiukapoor
+* @jfgrea27
+* @filip-aipl
+* @kejne
+* @kwoodson
+* @prune998
+* @GooglyBlox
+* @lindhe
+* @Deepam02
+* @aryasoni98
+* @Demivan
+* @codyja
+* @aslafy-z
+* @csz-akuity
+* @vadasambar
+* @rklonner
+* @DavidS-ovm
+* @BWagener
+* @singhvibhanshu
+* @ksawerykarwacki
+* @likelymichael
+* @hairyhum
+
+**Full Changelog**: 
[v1.8.9...v1.9.0](https://github.com/akuity/kargo/compare/v1.8.9...v1.9.0)
\ No newline at end of file
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/kargo-cli-1.9.1/go.mod new/kargo-cli-1.9.2/go.mod
--- old/kargo-cli-1.9.1/go.mod  2026-01-31 03:11:53.000000000 +0100
+++ new/kargo-cli-1.9.2/go.mod  2026-02-02 13:44:17.000000000 +0100
@@ -44,7 +44,7 @@
        github.com/go-openapi/swag v0.23.0
        github.com/go-openapi/validate v0.25.1
        github.com/gogo/protobuf v1.3.2
-       github.com/golang-jwt/jwt/v5 v5.3.0
+       github.com/golang-jwt/jwt/v5 v5.3.1
        github.com/google/go-containerregistry v0.20.7
        github.com/google/go-github/v76 v76.0.0
        github.com/google/uuid v1.6.0
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/kargo-cli-1.9.1/go.sum new/kargo-cli-1.9.2/go.sum
--- old/kargo-cli-1.9.1/go.sum  2026-01-31 03:11:53.000000000 +0100
+++ new/kargo-cli-1.9.2/go.sum  2026-02-02 13:44:17.000000000 +0100
@@ -275,8 +275,8 @@
 github.com/gofrs/uuid v4.0.0+incompatible/go.mod 
h1:b2aQJv3Z4Fp6yNu3cdSllBxTCLRxnplIgP/c0N/04lM=
 github.com/gogo/protobuf v1.3.2 h1:Ov1cvc58UF3b5XjBnZv7+opcTcQFZebYjWzi34vdm4Q=
 github.com/gogo/protobuf v1.3.2/go.mod 
h1:P1XiOD3dCwIKUDQYPy72D8LYyHL2YPYrpS2s69NZV8Q=
-github.com/golang-jwt/jwt/v5 v5.3.0 
h1:pv4AsKCKKZuqlgs5sUmn4x8UlGa0kEVt/puTpKx9vvo=
-github.com/golang-jwt/jwt/v5 v5.3.0/go.mod 
h1:fxCRLWMO43lRc8nhHWY6LGqRcf+1gQWArsqaEUEa5bE=
+github.com/golang-jwt/jwt/v5 v5.3.1 
h1:kYf81DTWFe7t+1VvL7eS+jKFVWaUnK9cB1qbwn63YCY=
+github.com/golang-jwt/jwt/v5 v5.3.1/go.mod 
h1:fxCRLWMO43lRc8nhHWY6LGqRcf+1gQWArsqaEUEa5bE=
 github.com/golang/protobuf v1.5.4 
h1:i7eJL8qZTpSEXOPTxNKhASYpMn+8e5Q6AdndVa1dWek=
 github.com/golang/protobuf v1.5.4/go.mod 
h1:lnTiLA8Wa4RWRcIUkrtSVa5nRhsEGBg48fD6rSs7xps=
 github.com/google/btree v1.1.3 h1:CVpQJjYgC4VbzxeGVHfvZrv1ctoYCAI8vbl07Fcxlyg=

++++++ kargo-cli.obsinfo ++++++
--- /var/tmp/diff_new_pack.R04T1l/_old  2026-02-03 21:31:00.791423938 +0100
+++ /var/tmp/diff_new_pack.R04T1l/_new  2026-02-03 21:31:00.795424107 +0100
@@ -1,5 +1,5 @@
 name: kargo-cli
-version: 1.9.1
-mtime: 1769825513
-commit: e594e1508d679aff1a64961cd59cd87a6fb1a6f9
+version: 1.9.2
+mtime: 1770036257
+commit: 141a6cd104f855d404119b78c5ae2646c66ea9e4
 

++++++ vendor.tar.gz ++++++
/work/SRC/openSUSE:Factory/kargo-cli/vendor.tar.gz 
/work/SRC/openSUSE:Factory/.kargo-cli.new.1995/vendor.tar.gz differ: char 13, 
line 1

Reply via email to