task: #3621040 Release Varbase Components 4.0.0

Rajab Natshahrequested to merge
issue/varbase_components-3616970:3621040-release-4-0-0 into 4.0.x

Release Varbase Components 4.0.0, the first stable release on the 4.0.x line.

Part of the Plan: Release Varbase Components 4.0.0 issue. This is the critical-path blocker for the Varbase 11 stable train: varbase_content_base, varbase_blog_base, varbase_events_base and varbase_news_base currently require 4.0.x-dev and cannot pin ~4.0.0 until the stable tag exists.

Problem / Motivation

varbase_components is a tag-only project: neither composer.json nor varbase_components.info.yml carries a version key, so drupal.org packaging injects the version from the tag. The only place the release version is written by hand is the README release badge, which still advertises 4.0.0-rc1.

Tagging 4.0.0 while the README badge and its pipeline link still point at 4.0.0-rc1 would ship a stable release advertising a release candidate.

Proposed resolution

Update the README release badge and its pipelines?ref= link from 4.0.0-rc1 to 4.0.0. One line, one commit. Nothing else in the repository carries the version string (verified by grepping README.md, composer.json, package.json, .github/ and .gitlab/), and the project ships no CHANGELOG.

-[![Varbase Components](https://img.shields.io/badge/Varbase%20Components-4.0.0--rc1-0d6efc?labelColor=001d38&style=flat-square)](https://git.drupalcode.org/project/varbase_components/-/pipelines?ref=4.0.0-rc1)
+[![Varbase Components](https://img.shields.io/badge/Varbase%20Components-4.0.0-0d6efc?labelColor=001d38&style=flat-square)](https://git.drupalcode.org/project/varbase_components/-/pipelines?ref=4.0.0)

The 4.0.0 tag is cut at this branch tip once the MR is merged and the pipeline is green.

Remaining tasks

  • Bump the README release badge to 4.0.0
  • Confirm no other file carries the version (tag-only project)
  • Green pipeline
  • Merge into 4.0.x
  • Tag 4.0.0 and push to the canonical repository and the GitHub mirror
  • Create the release node on drupal.org

API changes

None. Documentation-only change; no PHP, config, schema, service or route is touched.

Data model changes

None.

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

Merge request reports