Skip to content

Commit bddb45c

Browse files
committed
[RHDEVDOCS-6885] Release notes for Pipelines 1.20.1
reviews no1 reviews no2 reviews no3 reviews no4 reviews no5 review no6
1 parent 0a7d361 commit bddb45c

File tree

2 files changed

+31
-0
lines changed

2 files changed

+31
-0
lines changed
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
// This module is included in the following assemblies:
2+
// * release_notes/op-release-notes-1-20.adoc
3+
4+
:_mod-docs-content-type: REFERENCE
5+
[id="op-release-notes-1-20-1_{context}"]
6+
= Release notes for {pipelines-title} 1.20.1
7+
8+
With this update, {pipelines-title} General Availability (GA) 1.20.1 is available on {OCP} 4.15 and later versions.
9+
10+
[id="fixed-issues-1-20-1_{context}"]
11+
== Fixed issues
12+
13+
.Operator
14+
15+
* Before this update, the `tekton-operator-proxy-webhook` admission webhook validated all namespaces, including control-plane namespaces (`kube-\*`, `openshift-*`), which could cause webhook certificate issues to affect unrelated system components, such as the Network Operator, during namespace reconciliation. With this update, the webhook excludes control-plane namespaces from validation, preventing certificate issues from impacting other cluster operators while keeping the existing certificate renewal logic intact and improving isolation.
16+
17+
.{pac}
18+
19+
* Before this update, commit status handling and pipeline execution for GitLab forks would fail unexpectedly when {pac} fell back to posting comments for status updates when permissions were restricted on forked projects, and PipelineRuns would fail if the configured token lacked read access to the source repository. With this update, {pac} attempts to set commit status on both the source (fork) and target (upstream) projects, only posting a comment if both attempts fail. Additionally, {pac} attempts to proactively verify that the configured token includes the `read_repository` scope before running a pipeline, failing early with a clear error message if access is insufficient.
20+
21+
* Before this update, the {pac} dynamic variable `revision` returned the SHA of the original commit instead of the latest HEAD merge commit after upgrading to {pipelines-shortname} 1.19. With this update, the changes introduced in 1.19 are reverted and the `revision` variable always fetches the SHA of the HEAD merge commit as expected.
22+
23+
* Before this update, when upgrading to 1.20.0, the `hub-catalog-name` field in the {pac} config map was set to the deprecated {tekton-hub} catalog name `tekton`. With this update, the field defaults to the {artifact-hub} catalog name, and you can override it with a custom value.
24+
25+
.User interface
26+
27+
* Before this update, after upgrading {OCP} to 4.19.15 or greater, the *Navigation* tab intermittently disappeared, and the Pipeline Operator installation UI could crash after creating a PipelineRun on Sandbox clusters. These issues were caused by a race condition introduced by new flags in {OCP}. With this update, the race condition is resolved.

release_notes/op-release-notes-1-20.adoc

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,10 @@ include::modules/op-tkn-pipelines-compatibility-support-matrix.adoc[leveloffset=
3131
// Release notes for Red Hat OpenShift Pipelines 1.20.0
3232
include::modules/op-release-notes-1-20-0.adoc[leveloffset=+1]
3333

34+
// Release notes for Red Hat OpenShift Pipelines 1.20.1
35+
include::modules/op-release-notes-1-20-1.adoc[leveloffset=+1]
36+
37+
3438
//Additional resources 1.20
3539
.Additional resources
3640
* xref:../secure/using-buildah-ns-tekton-task.adoc#op-differences-between-buildah-buildah-ns-tasks_using-buildah-ns-tekton-task[Differences between `buildah` and `buildah-ns` tasks]

0 commit comments

Comments
 (0)