You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/op-release-notes-1-9.adoc
+47-1Lines changed: 47 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -358,7 +358,7 @@ spec:
358
358
359
359
// .PAC
360
360
361
-
* Before this update, {pac} did not get updated values from the {pac} ConfigMap object. With this update, this issue is fixed and {pac} ConfigMap object looks for any new changes.
361
+
* Before this update, {pac} did not get updated values from the {pac} `ConfigMap` object. With this update, this issue is fixed and the {pac} `ConfigMap` object looks for any new changes.
362
362
// Savita Ashture
363
363
364
364
* Before this update, {pac} controller did not wait for the `tekton.dev/pipeline` label to be updated and added the `checkrun id` label, which would cause race conditions. With this update, the {pac} controller waits for the `tekton.dev/pipeline` label to be updated and then adds the `checkrun id` label, which helps to avoid race conditions.
@@ -373,3 +373,49 @@ spec:
373
373
* Before this update, a pull request failed if the user in the annotation provided values by using a regex form, for example, `refs/head/rel-*`. The pull request failed because it was missing `refs/heads` in its base branch. With this update, the prefix is added and checked that it matches. This resolves the issue and the pull request is successful.
374
374
// Savita Ashture
375
375
376
+
[id="release-notes-1-9-1_{context}"]
377
+
== Release notes for {pipelines-title} General Availability 1.9.1
378
+
379
+
With this update, {pipelines-title} General Availability (GA) 1.9.1 is available on {product-title} 4.11 and later.
380
+
381
+
[id="fixed-issues-1-9-1_{context}"]
382
+
== Fixed issues
383
+
384
+
* Before this update, the `tkn pac repo list` command did not run on Microsoft Windows. This update fixes the issue, and now you can run the `tkn pac repo list` command on Microsoft Windows.
385
+
386
+
* Before this update, {pac} watcher did not receive all the configuration change events. With this update, the {pac} watcher is updated, and now the {pac} watcher does not miss the configuration change events.
387
+
388
+
* Before this update, the pods created by {pac}, such as `TaskRuns` or `PipelineRuns` could not access custom certificates exposed by the user in the cluster. This update fixes the issue, and you can now access custom certificates from the `TaskRuns` or `PipelineRuns` pods in the cluster.
389
+
390
+
* Before this update, on a cluster enabled with FIPS, the `tekton-triggers-core-interceptors` core interceptor used in the `Trigger` resource did not function after the Pipelines Operator was upgraded to version 1.9. This update resolves the issue. Now, OpenShift uses MInTLS 1.2 for all its components. As a result, the `tekton-triggers-core-interceptors` core interceptor updates to TLS version 1.2and its functionality runs accurately.
391
+
392
+
* Before this update, when using a pipeline run with an internal OpenShift image registry, the URL to the image had to be hardcoded in the pipeline run definition. For example:
When using a pipeline run in the context of {pac}, such hardcoded values prevented the pipeline run definitions from being used in different clusters and namespaces.
403
+
+
404
+
With this update, you can use the dynamic template variables instead of hardcoding the values for namespaces and pipeline run names to generalize pipeline run definitions. For example:
* Before this update, {pac} used the same GitHub token to fetch a remote task available in the same host only on the default GitHub branch. This update resolves the issue. Now {pac} uses the same GitHub token to fetch a remote task from any GitHub branch.
415
+
416
+
[id="known-issues-1-9-1_{context}"]
417
+
== Known issues
418
+
419
+
* The value for `CATALOG_REFRESH_INTERVAL`, a field in the Hub API `ConfigMap` object used in the Tekton Hub CR, is not getting updated with a custom value provided by the user.
420
+
+
421
+
Workaround: None. You can track the issue link:https://issues.redhat.com/browse/SRVKP-2854[SRVKP-2854].
0 commit comments