Problem/Motivation
The 3.1.x branch targets Drupal ~11.4.0, but its GitLab CI composer job overrides before_script without a job-level DRUPAL_CORE variable, so the DrupalCI template default wins and the job (and the webship-js-test browser job that depends on it) actually build and run on Drupal 11.3.12, not 11.4. The pipeline reports green while never validating the real ~11.4 target.
Steps to reproduce
Proposed resolution
Add job-level variables: DRUPAL_CORE: "11.4.0" and IGNORE_PROJECT_DRUPAL_CORE_VERSION: "1" to the composer job in .gitlab-ci.yml so the whole pipeline resolves and tests against Drupal ~11.4.0.
Remaining tasks
- ✅ File an issue about this project
- ✅ Addition/Change/Update/Fix to this project
- ❌ Testing to ensure no regression
- ➖ Automated unit/functional testing coverage
- ➖ Developer Documentation support on feature change/addition
- ➖ User Guide Documentation support on feature change/addition
- ➖ UX/UI designer responsibilities
- ➖ Accessibility and Readability
- ❌ Reviewed by a human
- ❌ Code review by maintainers
- ❌ Full testing and approval
- ❌ Credit contributors
- ❌ Review with the product owner
- ❌ Update Release Notes
- ✅ Release
User interface changes
- N/A
API changes
- N/A
Data model changes
- N/A
Release notes snippet
- N/A
Issue fork varbase_components-3609254
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
rajab natshahComment #4
rajab natshah✅ Released varbase_components-3.1.1
Comment #6
rajab natshahComment #7
rajab natshah