From bb14a4826f86929276dc16e7bacf23fc85eeef1c Mon Sep 17 00:00:00 2001
From: Alif Putra Winata <98870352+arfshl@users.noreply.github.com>
Date: Wed, 8 Jul 2026 10:55:53 +0700
Subject: [PATCH] Fix CI build schedule broken links

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index b5be4049c0..ea7a3d5b2f 100644
--- a/README.md
+++ b/README.md
@@ -153,7 +153,7 @@ Due to the transition from MV2 to MV3, we cannot update our filters remotely. To
 
 ### Auto-update cycle
 
-We have set up an automated update cycle that regularly syncs with fresh releases from the [`@adguard/dnr-rulesets`](https://www.npmjs.com/package/@adguard/dnr-rulesets) npm package. The update frequency is configured in our [CI build schedule](../bamboo-specs/auto-build.yaml). This ensures our extension stays up-to-date with the latest filter rules.
+We have set up an automated update cycle that regularly syncs with fresh releases from the [`@adguard/dnr-rulesets`](https://www.npmjs.com/package/@adguard/dnr-rulesets) npm package. The update frequency is configured in our [CI build schedule](bamboo-specs/auto-build.yaml). This ensures our extension stays up-to-date with the latest filter rules.
 
 To deploy new releases as soon as possible, we have implemented all the steps outlined in Chrome's [Skip Review documentation](https://developer.chrome.com/docs/webstore/skip-review). This allows us to publish updates to the Chrome Web Store without waiting for the full review cycle.