Skip to content

Bumped the CI database cache version to 'v26.7.0'.#2710

Merged
AlexSkrypnyk merged 1 commit into
mainfrom
feature/db-cache-bump
Jun 24, 2026
Merged

Bumped the CI database cache version to 'v26.7.0'.#2710
AlexSkrypnyk merged 1 commit into
mainfrom
feature/db-cache-bump

Conversation

@AlexSkrypnyk

Copy link
Copy Markdown
Member

Summary

Bumps the CI database cache-key version prefix from v26.6.0 to v26.7.0 to force a fresh CI database cache for the 1.40.0 release cycle and keep the cache prefix one Lagoon cycle ahead of the current uselagoon/* container tags. The generated .circleci/vortex-test-common.yml is regenerated from .circleci/config.yml (auto-generated file; never hand-edited).

Changes

  • .circleci/config.yml and .github/workflows/build-test-deploy.yml: cache key prefix v26.6.0 -> v26.7.0.
  • .circleci/vortex-test-common.yml: regenerated from config.yml (generated file; not hand-edited).

Screenshots

N/A

Before / After

Before (v26.6.0):
┌─────────────────────────────────────────────────────┐
│  restore_cache key: v26.6.0-<branch>-<ts>           │
│        │                                             │
│        ▼                                             │
│  Cache HIT → restores prior DB dump from last cycle  │
│  (potentially stale data from pre-1.40.0 builds)    │
└─────────────────────────────────────────────────────┘

After (v26.7.0):
┌─────────────────────────────────────────────────────┐
│  restore_cache key: v26.7.0-<branch>-<ts>           │
│        │                                             │
│        ▼                                             │
│  Cache MISS → fresh DB download + sanitise + save   │
│  (clean slate for the 1.40.0 cycle)                 │
└─────────────────────────────────────────────────────┘

@coderabbitai

coderabbitai Bot commented Jun 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@AlexSkrypnyk, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 13 minutes and 26 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 5f3ad750-51b1-4220-b207-b71f6677c831

📥 Commits

Reviewing files that changed from the base of the PR and between 380cae7 and d1d1620.

📒 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/db-cache-bump

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

@AlexSkrypnyk AlexSkrypnyk moved this from BACKLOG to In progress in Vortex 1.x Jun 24, 2026
@AlexSkrypnyk AlexSkrypnyk added this to the 1.40.0 milestone Jun 24, 2026
@github-actions

Copy link
Copy Markdown

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.58% (208/211)
Per-class coverage
Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

@AlexSkrypnyk

This comment has been minimized.

2 similar comments
@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk

Copy link
Copy Markdown
Member Author

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.58% (208/211)
Per-class coverage
Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

@github-actions

Copy link
Copy Markdown

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

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

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

@codecov

codecov Bot commented Jun 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.22%. Comparing base (380cae7) to head (d1d1620).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2710      +/-   ##
==========================================
- Coverage   86.67%   86.22%   -0.45%     
==========================================
  Files          96       89       -7     
  Lines        4719     4560     -159     
  Branches       47        3      -44     
==========================================
- Hits         4090     3932     -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.

@AlexSkrypnyk AlexSkrypnyk merged commit 0363406 into main Jun 24, 2026
34 checks passed
@AlexSkrypnyk AlexSkrypnyk deleted the feature/db-cache-bump branch June 24, 2026 05:29
@github-project-automation github-project-automation Bot moved this from In progress to Release queue in Vortex 1.x Jun 24, 2026
@AlexSkrypnyk AlexSkrypnyk added the Needs review Pull request needs a review from assigned developers label Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs review Pull request needs a review from assigned developers

Projects

Status: Release queue

Development

Successfully merging this pull request may close these issues.

1 participant