From f0b36c1c5f2fc8a33abcd4a17f40d3a20335b115 Mon Sep 17 00:00:00 2001 From: pm-dev563 Date: Wed, 4 Feb 2026 17:51:48 +0700 Subject: [PATCH] Fix newline --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index f3dea3e..03e8ce7 100644 --- a/README.md +++ b/README.md @@ -264,8 +264,7 @@ But if you do not add the resolution strategy as a cache-suffix (see [Caching do they will have the same cache key. This means the first job which starts uploading its cache will win and all other job will fail -uploading the cache, -because they try to upload with the same cache key. +uploading the cache, because they try to upload with the same cache key. You might see errors like `Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists`