RHDEVDOCS-6524: Content removal and modification for some issues in the Pipelines 1.19 RN

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

@@ -249,39 +249,18 @@ spec:
 [id="tekton-cache-new-features-1-19_{context}"]
 === Tekton Cache
 
-* With this update, the `tekton-caches` tool can automatically detect and use common cache directories when the `--path` flag is not specified. The system inspects the workspace and applies sensible defaults, such as `$GOMODCACHE`, `~/.npm`, and `~/.m2`.
+* With this update, parameter naming conventions across the `StepAction` feature are unified for consistency. The casing of `cache-fetch` and `cache-upload` step actions is now consistent with that of `git-clone`.
 
-* With this update, build caching is no longer limited to predefined paths for Go and Maven builds. You can use a new `--buildCommand <dir>` flag to snapshot and cache any directory, enabling support for additional build systems like `Rust (target/)`, `Gradle (.gradle/)`, or custom toolchains.
-
-* With this update, parameter naming conventions across the `StepActions` feature are unified for consistency. The casing of `git-clone` step actions is now consistent with that of `cache-fetch` and `cache-upload`.
-
-* With this update, the `tekton-caches` tool can be pushed to and retrieved from Google Cloud Storage (GCS) buckets, in addition to existing OCI registry support. To enable this, set the cache backend to a `gcs://bucket/path` URI.
+* With this update, the `tekton-caches` tool can push to and retrieve from Google Cloud Storage (GCS) buckets, in addition to existing OCI registry support. To enable this, set the cache backend to a `gs://bucket/path` URI.
 
 * With this update, you can store cache archives in any S3 compatible bucket, including on-premises solutions such as MinIO or cloud providers such as AWS. To use this feature, specify a URL, such as `s3://my-bucket/cache` as the cache backend.
 
 * With this update, cache archives are compressed using `Gzip` before being uploaded. This reduces object storage costs and speeds up data transfer, especially for large caches such as `Go` modules.
 
-* With this update, restored caches retain their original file mode bits, ensuring that executable scripts and other permission-sensitive files function correctly. Previously, restored files defaulted to 0600 permissions, which could prevent scripts from running as expected.
+* With this update, restored caches default to `0777` permission, ensuring that executable scripts and other permission-sensitive files function correctly. Previously, restored files defaulted to `0600` permissions, which could prevent scripts from running as expected.
 
 * With this update, running on Google Kubernetes Engine (GKE) with Workload Identity Federation (WIF) no longer requires embedding key files in tasks. Instead, you can now mount projected volume tokens, eliminating the need for long-lived credentials and improving security.
 
-* With this update, the CLI and `Task` components use a consistent environment variable for provider credentials. Set the `CRED_STORE` value to `/tekton/creds/creds.json` to support this value across all supported backends, including OCI, GCS, and S3.
-+
-.Example for enabling the `CRED_STORE=/tekton/creds/creds.json` environment variable
-[source,yaml]
-----
-apiVersion: tekton.dev/v1
-kind: TaskRun
-containers:
-- name: cache
-  env:
-  - name: CRED_STORE
-    value: /tekton/creds/creds.json
-  volumeMounts:
-  - name: creds
-    mountPath: /tekton/creds
-----
-
 * With this update, the code paths for GCS and S3 backends are unified using the `gocloud.dev` library. This abstraction simplifies support of additional storage providers, such as Azure Blob Storage or local filesystems.
 
 * With this update, the `fetch` command is improved to automatically create the destination folder if it does not exist in a new workspace. Previously, the command would fail in such cases, requiring you to create a directory manually.