task: #3621162 Set the recipe version to 1.0.0-rc1

Release plan issue: #3621162

Problem / Motivation

drupal/educare 1.0.x carries version: 1.0.x-dev and pins all 19 drupal/varbase_*_base / drupal/vartheme_bs5_educare requirements to the 1.0.x-dev branch. A release must pin releases, not development branches.

This is also a step towards the 1.0.0 stable release. Drupal CMS ships minimum-stability: stable, so on a stock drupal/cms project composer require drupal/educare:~1 cannot resolve a pre-release today without overriding the stability setting.

Proposed resolution

One bump commit, no functional change to the recipe:

• composer.json: version 1.0.x-dev -> 1.0.0-rc1.
• composer.json: the 18 drupal/varbase_*_base requirements and drupal/vartheme_bs5_educare move from 1.0.x-dev back to ~1.0.0, restoring the shape the 1.0.0-beta1 tag had.
• README.md: version badge 1.0.0-beta1 -> 1.0.0-rc1, including its ?ref=.
• CHANGELOG.md: the 1.0.0-rc1 entry and its two compare link references.

Deliberately untouched: drupal/core ^11.3, the 13 drupal/drupal_cms_* ~2, drupal/easy_email_express ~1, drupal/recipe_installer_kit ~1.

What ~1.0.0 resolves to

Every one of the 19 was checked against its published releases, so none of these constraints is unresolvable:

• 17 of the 18 base recipes have a stable 1.0.0.
• drupal/varbase_auth_base -> 1.0.0-rc1.
• drupal/vartheme_bs5_educare -> 1.0.0-rc1, released today. updates.drupal.org lists it ahead of 1.0.0-alpha5, so ~1.0.0 really does resolve to rc1 and not to the older alpha.

Remaining tasks

• Review and merge.
• Tag 1.0.0-rc1 and publish the release node.
• Back to DEV.

Checkpoints

• Follows the Drupal coding standards.
• composer.json re-parsed as JSON after editing.
• Every changed dependency constraint verified against its published releases.
• No functional change to the recipe.
• Reviewed by a human.
• Code review by maintainers.

AI-Generated: Yes