Updated 'drevops/mariadb-drupal-data' to '26.10.0'.

[AlexSkrypnyk]

Summary

The database-nightly job in .circleci/config.yml now pins VORTEX_DB_IMAGE_BASE to drevops/mariadb-drupal-data:26.10.0, and SEED_URL/SEED_SHA256 in .vortex/tests/update-test-assets point at the 26.10.0 release asset of seed.sh, so both places Vortex pins the image track the same release.

The pins sat on 2 older releases, 26.8.1 for the image and 26.7.0 for seed.sh, so they missed what 26.10.0 changes for every database-in-image site: when the data directory is already populated, entrypoint.bash writes the password-less client .my.cnf into ${MARIADB_DATA_DIR} (/home/db-data) and adds a default [mysql] database=, FORCE_MYSQL_UPGRADE becomes a deprecated alias of MARIADB_FORCE_UPGRADE, and the base image moves to uselagoon/mariadb-10.11-drupal:26.9.0. seed.sh gains SANITIZE_PROCEED and SANITIZE_FILE, renames DST_IMAGE to DESTINATION_IMAGE, and no longer prints a Docker Hub link or skips :latest for destinations on other registries.

After merge, CircleCI projects scaffolded or updated from the template get 26.10.0 in database-nightly, and the next update-test-assets run seeds with the 26.10.0 script. PR CI executes neither pin, because database-nightly runs only on the nightly-db schedule and update-test-assets is run by hand, so the release was verified locally (see Verification). The installer fixtures don't change: they store drevops/mariadb-drupal-data:__VERSION__.

Before / After

BEFORE
┌───────────────────────────────────────────────┐
│ .circleci/config.yml (database-nightly job)   │
│   VORTEX_DB_IMAGE_BASE                        │──► drevops/mariadb-drupal-data:26.8.1
├───────────────────────────────────────────────┤
│ .vortex/tests/update-test-assets              │
│   SEED_URL, SEED_SHA256                       │──► seed.sh from the 26.7.0 release (d97c184b...)
└───────────────────────────────────────────────┘

AFTER
┌───────────────────────────────────────────────┐
│ .circleci/config.yml (database-nightly job)   │
│   VORTEX_DB_IMAGE_BASE                        │──► drevops/mariadb-drupal-data:26.10.0 (d76f8ffe...)
├───────────────────────────────────────────────┤
│ .vortex/tests/update-test-assets              │
│   SEED_URL, SEED_SHA256                       │──► seed.sh from the 26.10.0 release (1bc8062d...)
└───────────────────────────────────────────────┘

Changes

• .circleci/config.yml - VORTEX_DB_IMAGE_BASE in the database-nightly job.
• .vortex/tests/update-test-assets - SEED_URL and SEED_SHA256 move to the 26.10.0 asset together.

Verification

Nothing was published: seeding pushed to a throwaway local registry, and the seeded images were only tagged locally.

• 26.10.0 is upstream commit 15685d12, 1 commit past 0a357719, the :canary build the end-to-end test ran against. That commit changes seed.sh, its tests and docs, but not the Dockerfile or entrypoint.bash, and /lagoon/entrypoints/9999-mariadb-init.bash and /etc/mysql/my.cnf are byte-identical in the 26.10.0 image (sha256:d76f8ffe...) and the canary build (sha256:6fcdfa9e...).
• End to end, on the canary build: the drupal database from drevops/vortex-dev-mariadb-drupal-data-test-11.x:1.40.0 was re-seeded with BASE_IMAGE=drevops/mariadb-drupal-data:canary, and testAhoyWorkflowDatabaseFromImageStorageInImage passed against the result: OK (1 test, 401 assertions). It covers ahoy build from the image, ahoy reload-db, drush updb, ahoy export-db into a .tar and the Behat smoke tests. The export step is the one the relocated .my.cnf affects: vortex-export-db-image runs mysql -e and mariadb-upgrade --force inside the container with no credentials.
• Seeding, on the release: the same dump was re-seeded with the 26.10.0 seed.sh asset and BASE_IMAGE=drevops/mariadb-drupal-data:26.10.0, and all 3 stages passed. The untagged destination localhost:5055/... was reported as ...:latest, and the run ended on the pushed reference rather than a Docker Hub link.
• SEED_URL serves a file matching SEED_SHA256, byte-identical to seed.sh at the 26.10.0 tag.
• ahoy update-snapshots: 157/157 scenarios passed, 0 fixtures updated.

Left alone

• update-test-assets passes no BASE_IMAGE, so seed.sh seeds onto drevops/mariadb-drupal-data:latest, which is the same build as 26.10.0 (sha256:d76f8ffe...).
• The drevops/vortex-dev-mariadb-drupal-data-* test images, which pick up 26.10.0 the next time update-test-assets runs.
• VORTEX_DB_IMAGE_BASE is pulled but never used by the database build; that's tracked in 'VORTEX_DB_IMAGE_BASE' is pulled but never used to build the database container #3177.
• The v26.8.1 cache key prefixes in the CI configs, which carry the Vortex release version and aren't related to this image.

Release notes: https://github.com/drevops/mariadb-drupal-data/releases/tag/26.10.0

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository UI
• Review profile: ASSERTIVE
• Plan: Team
• Run ID: 3e19c9ac-bf01-48b4-9d7b-e676d130ecde

📥 Commits

Reviewing files that changed from the base of the PR and between 0c95c51 and ce15fba.

📒 Files selected for processing (2)

• .circleci/config.yml
• .vortex/tests/update-test-assets

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 0 remain after this review.

---

Walkthrough

The nightly database image and test seed asset references now use release 26.10.0. The seed asset script also uses the checksum for that release.

Changes

Release 26.10.0 update

Layer / File(s)	Summary
Update database and seed asset references .circleci/config.yml, .vortex/tests/update-test-assets	The nightly database job now uses drevops/mariadb-drupal-data:26.10.0. The seed asset URL and SHA-256 value now match release 26.10.0.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to ce15f

The release references are aligned, and the seed asset passed checksum verification. No identified issue prevents merging after normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: updating the MariaDB Drupal data image to version 26.10.0.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{A rabbit checks the version line
And finds the seed asset in time
The image hops to twenty-six ten
Its checksum matches, clear again
Then off I go through fields of green}

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

[github-actions]

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

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

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

[github-actions]

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   100.00% (233/233)

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:   100.00% (233/233)

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:   100.00% (233/233)

Per-class coverage

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