Problem/Motivation

Release Varbase Components 3.0.1 from the 3.0.x branch, for the Varbase 10.1.x line on Drupal ~11.4.

Proposed resolution

  • Re-running the pipeline at b46e135e failed: core 11.4.6 with Twig 3.30.0 returns a 500 on every page. Fixed in CI by #3629875, MR !76.
  • Tagged 3.0.1 at 8dec98c1, the merge of !76, after the green 3.0.x pipeline 997084. Released in varbase_components-3.0.1.
  • Publish the release node, then mirror the branch and tag to GitHub.

AI-Generated: Yes

Remaining tasks

  • ✅ File an issue
  • ✅ Addition/Change/Update/Fix
  • ✅ Testing to ensure no regression
  • ➖ Automated unit/functional testing coverage
  • ➖ Developer Documentation support
  • ➖ User Guide Documentation support
  • ➖ 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

Release notes snippet

  • task: #3607736 Require Drupal core ~11.4.0 (was ~11.3.0) and declare drupal/ds and drupal/field_group directly.
  • fix: #3615796 Resolve the PHPStan findings raised by the updated analyzers.
  • task: #3615770 Switch the Varbase functional testing suite to Varbase E2E.
  • task: #3625757 Update @vardot/varbase-e2e to 2.0.7.
  • task: #3614572 Add the default .gitlab and .github issue and merge request templates.
  • task: #3629875 Run the 3.0.x CI on Drupal core 11.4.9, which has the Twig 3.30 fix.

Comments

rajab natshah created an issue. See original summary.

rajab natshah’s picture

Issue summary: View changes
rajab natshah’s picture

Assigned: rajab natshah » Unassigned
Issue summary: View changes
Status: Active » Fixed

✅ Released in varbase_components-3.0.1.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.