fix: #3617356 Re-mint the stale Canvas component version pins

Rajab Natshahrequested to merge
issue/varbase_starter-3617356:3617356-stale-canvas-component into 1.0.x

Fixes #3617356.

Four Canvas component config entities shipped in the recipe carried an active_version hash that no longer matched the version Drupal Canvas mints from the SDC definitions on disk, and three component instances pinned a component_version that was stale in the same way. Same class of defect as the Card Logo fix in #3607733.

Component active_version

Component Shipped Minted
canvas.component.sdc.vartheme_bs5.card-hero 7b18bf9051fa6725 ecdc62ca524b348a
canvas.component.sdc.vartheme_bs5.icon-toggle 5a87298f3691cd43 c42c2d3c773c4f6c
canvas.component.sdc.vartheme_bs5.share 64add9738be2892f 24d3cc5800d6bb4f
canvas.component.sdc.webshare.share 64add9738be2892f 24d3cc5800d6bb4f

Instance component_version

Config Component Shipped Minted
canvas.page_region.vartheme_bs5.header sdc.vartheme_bs5.icon-toggle 5a87298f3691cd43 c42c2d3c773c4f6c
canvas.page_region.vartheme_bs5.footer block.system_menu_block.secondary 31ecc6cc06f17d4e 7206ccf6a90c8941
canvas.pattern.footer_global block.system_menu_block.secondary 31ecc6cc06f17d4e 7206ccf6a90c8941

No component loses a version: each previously active settings block is archived under its original hash key (7b18bf9051fa6725, 5a87298f3691cd43, 64add9738be2892f), so a tree still pinned to an older version keeps resolving, and the new active block holds the current definitions.

Verified against an installed site running Vartheme BS5 5.0.0-rc3, Webshare 2.0.0-beta2 and Drupal Canvas 1.10.1 by loading every Component config entity after a rebuild and comparing it to the recipe: 120 component pins and 152 instance pins, zero mismatches after the change.

Config only, 7 files. Composer validate, YAML lint (174 files, 0 invalid), Cspell, ESLint and Cucumber dry-run were run locally with gitlab-ci-local and pass; the install and functional testing stages run here.

AI-Generated: Yes

Checkpoints:

  • File an issue
  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Automated unit testing coverage
  • Automated functional testing coverage
  • UX/UI designer responsibilities
  • Readability
  • Accessibility
  • Performance
  • Security
  • Developer Documentation
  • User Guide Documentation
  • Reviewed by human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Release notes snippet
  • Release
Edited by Rajab Natshah

Merge request reports