Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/op-configuring-retention-policy-results.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ spec:
result:
options:
configMaps:
config-results-retention-policy:
tekton-results-config-results-retention:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exact name - tekton-results-config-results-retention-policy

data:
runAt: "3 5 * * 0" #<1>
maxRetention: "30" #<2>
Expand Down
6 changes: 5 additions & 1 deletion modules/op-release-notes-1-20-0.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -280,10 +280,14 @@ spec:
.{tekton-triggers}
* Before this update, using a `TriggerGroup` with multiple triggers and extensions caused a data race and controller panic. With this update, the controller handles multiple triggers without errors.

[id="pipelines-known-issues-1-20-0"]
== Known issues

* During upgrade, if you do not explicitly set `defaultRetention`, the previously configured `maxRetention` value may be lost. To avoid unintended retention behavior, ensure that `defaultRetention` is explicitly set before or during the upgrade.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they cant set before upgrade. They have to check the value of maxRetetion before upgrade and set that to defualtRetention post upgrade.


[id="pipelines-deprecated-features-1-20-0"]
== Deprecated features

* The `maxRetention` parameter in {tekton-results} retention agent is deprecated. Use `defaultRetention`.
* The `maxRetention` parameter in {tekton-results} retention agent is deprecated. Use `defaultRetention` instead.

* The `chain` command is deprecated and will be removed in a future release.
26 changes: 26 additions & 0 deletions modules/op-release-notes-1-20-2.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
// This module is included in the following assemblies:
// * release_notes/op-release-notes-1-20.adoc

:_mod-docs-content-type: REFERENCE
[id="op-release-notes-1-20-2_{context}"]
= Release notes for {pipelines-title} 1.20.2

With this update, {pipelines-title} General Availability (GA) 1.20.2 is available on {OCP} 4.15 and later versions.

[id="fixed-issues-1-20-2_{context}"]
== Fixed issues

.Operator

Custom Hub catalog configuration fix::
With this update, you can successfully configure custom hub catalogs such as TektonHub, ArtifactHub, or other custom hubs through the `TektonConfig` specification. The system now correctly preserves the configured catalog type in the {pac} config map, ensuring consistent and reliable catalog behavior across the environment.

.User interface

Navigation tab no longer disappears and installation UI no longer crashes after {OCP} upgrade::
With this update, pagination functions correctly when the `data_source` filter is set to `archived`. In the previous release, scrolling failed to load additional `PipelineRun` results because the UI client expected the `nextPageToken` field, while the API returned `next_page_token`. This mismatch prevented the `onScroll` callback from creating the next page request, causing pagination to stop after the first page. The UI has been updated to support `next_page_token`, and additional results load as expected when scrolling.

.Tekton Config

Retention Configuration Update::
If the `maxRetention` field is carried over from a previous version during an upgrade, it will continue to take precedence over the `defaultRetention` field. In such cases, you must manually remove the deprecated `maxRetention` field and configure the `defaultRetention` field with the desired value. This behavior is intentional to prevent breaking existing setups during upgrades. Starting in version {pipelines-title} v1.20.2, the preferred and supported configuration method is using the `defaultRetention` field in the `config-retention` config map.
3 changes: 3 additions & 0 deletions release_notes/op-release-notes-1-20.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,9 @@ include::modules/op-release-notes-1-20-0.adoc[leveloffset=+1]
// Release notes for Red Hat OpenShift Pipelines 1.20.1
include::modules/op-release-notes-1-20-1.adoc[leveloffset=+1]

// Release notes for Red Hat OpenShift Pipelines 1.20.2
include::modules/op-release-notes-1-20-2.adoc[leveloffset=+1]


//Additional resources 1.20
.Additional resources
Expand Down