Skip to content

Commit ed700a4

Browse files
authored
Merge pull request #95786 from Dhruv-Soni11/RHDEVDOCS-6492
RHDEVDOCS-6492: Additional content creation for Pipelines 1.19 RN
2 parents 85efc1a + f2acfa2 commit ed700a4

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

modules/op-release-notes-1-19.adoc

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -555,4 +555,14 @@ spec:
555555

556556
* Before this update, users had to wrap the CLI in separate `Task` resources to back up or restore build caches. With this update, `StepAction` definitions support `fetch` and `upload`, so you can handle cache operations with a single step inside any `Task` or `Pipeline`.
557557

558-
* Before this update, pushing a cache to a registry with a self-signed certificate failed due to TLS errors. With this update, the CLI and `Task` resource support new `--insecure` flag, which enables those pushes and makes it easier to work with air-gapped development clusters and local registries.
558+
* Before this update, pushing a cache to a registry with a self-signed certificate failed due to TLS errors. With this update, the CLI and `Task` resource support new `--insecure` flag, which enables those pushes and makes it easier to work with air-gapped development clusters and local registries.
559+
560+
* Before this update, in GitLab, pipeline runs for Merge Requests (MRs) were automatically re-triggered when non-code changes occurred in {pac}, such as updating the MR description or modifying reviewers. This behavior caused unnecessary pipeline executions. With this update, this issue is fixed, and pipeline runs are only triggered by new commits.
561+
562+
* Before this update, in {pac}, a push `PipelineRun` with the `on-path-change` annotation was not triggered on pull request merge events, even when the merged pull request modified the specified paths. With this update, this issue is fixed by ensuring that the pipeline is correctly triggered when relevant path changes are introduced through a pull request merge.
563+
564+
* Before this update, {pac} attempted to parse and validate every YAML file in the `.tekton directory`, resulting in false errors for unrelated or invalid non-Tekton resources. With this update, {pac} validates only explicitly defined Tekton resources, reducing noise in pull request feedback and improving the accuracy of CI validation.
565+
566+
* Before this update, a non-domain-qualified finalizer name was used, leading to warnings in the {pac} watcher from the Kubernetes API. This issue is now resolved by using a domain-qualified finalizer name that aligns with Kubernetes conventions.
567+
568+
* Before this update, the {pac} controller terminated unexpectedly when validating GitHub webhook secrets with an invalid or expired token. With this update, this issue is fixed. The controller logs a clear error message and continues running, ensuring webhook functionality and controller availability are not disrupted.

0 commit comments

Comments
 (0)