Bumped the CI database cache version to 'v26.7.1'.

[AlexSkrypnyk]

Summary

The CI database cache is shared across all branches for a given day: it is keyed by a hardcoded develop branch name plus a per-day timestamp, and is populated with a sanitized database dump on the first build of the day. A build populated that shared cache with a .data directory that was missing db.sql. Because CircleCI's and GitHub Actions' cache-save steps never overwrite an existing key, every subsequent build on both providers restored that same incomplete .data directory for the rest of the day, so the build job's provision step failed with "Unable to import database from file."

Changes

• Bumped the cache-key version prefix from v26.7.0 to v26.7.1 across every restore and save key in .circleci/config.yml, .circleci/vortex-test-common.yml, and .github/workflows/build-test-deploy.yml (16 identical substitutions).
• The new prefix makes every existing cache key miss on both CircleCI and GitHub Actions, forcing a fresh database dump download and repopulating .data with a valid db.sql under the new key.
• Follows the same fix pattern as the precedent commit 036340646 ("Bumped the CI database cache version to 'v26.7.0'."), which resolved an earlier occurrence of the same poisoned-cache failure.

Before / After

BEFORE - poisoned cache serves every build for the rest of the day (key prefix stuck at v26.7.0)

  +----------------------------------------------------------------------+
  | 06:00 build   -> DB dump incomplete -> .data/ saved WITHOUT db.sql   |
  |               -> save_cache key = v26.7.0-<branch>-<fallback>-<ts>   |
  +----------------------------------------------------------------------+
                                    |
                                    |  save_cache never overwrites an existing key
                                    v
  +----------------------------------------------------------------------+
  | 06:15..23:59  -> restore_cache HIT (v26.7.0-...)                     |
  |               -> .data/ restored WITHOUT db.sql                      |
  |               -> provision -> FAIL "Unable to import database"      |
  +----------------------------------------------------------------------+

AFTER - version bump forces a clean cache for the rest of the day (key prefix now v26.7.1)

  +----------------------------------------------------------------------+
  | next build    -> restore_cache MISS (v26.7.1-... never cached)       |
  |               -> fresh DB dump downloaded -> .data/db.sql present    |
  |               -> save_cache key = v26.7.1-<branch>-<fallback>-<ts>   |
  +----------------------------------------------------------------------+
                                    |
                                    |  clean .data/ now stored under the new key
                                    v
  +----------------------------------------------------------------------+
  | every later build -> restore_cache HIT (v26.7.1-...)                 |
  |               -> .data/db.sql present -> provision -> OK             |
  +----------------------------------------------------------------------+

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 58 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1e7b3d1d-9d0a-4b66-bf64-4a72b38b8f85

📥 Commits

Reviewing files that changed from the base of the PR and between 0a9ffdc and cca73a2.

📒 Files selected for processing (3)

• .circleci/config.yml
• .circleci/vortex-test-common.yml
• .github/workflows/build-test-deploy.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/bump-db-cache

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.55% (204/207)

Per-class coverage

Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

[AlexSkrypnyk]

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.55% (204/207)

Per-class coverage

Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

[github-actions]

📖 Documentation preview for this pull request has been deployed to Netlify:

https://6a4dfd72f2c01f9577e88e0d--vortex-docs.netlify.app

This preview is rebuilt on every commit and is not the production documentation site.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.25%. Comparing base (0a9ffdc) to head (cca73a2).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2779      +/-   ##
==========================================
- Coverage   86.69%   86.25%   -0.45%     
==========================================
  Files          96       89       -7     
  Lines        4727     4568     -159     
  Branches       47        3      -44     
==========================================
- Hits         4098     3940     -158     
+ Misses        629      628       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.