Drupal.org change notifications - Upcoming changes to packaging & to support contrib sember

26 views

Skip to first unread message

Drupal.org change notifications

unread,

Jan 24, 2020, 1:47:12 PM1/24/20

to Drupal.org change notifications

Software related change records:

https://www.drupal.org/list-changes/drupalorg

Infrastructure related change records:

https://www.drupal.org/list-changes/infrastructure

Packaging pipeline updates, and changes to support contrib semver

Packaging pipeline changes
The requirements for packaging Drupal releases have evolved over the years. Particularly with the release of Drupal 8.8.* and all later versions, we can no longer provide a simple packaged git checkout in order to start a Drupal project, we must instead ensure that the packaged artifact has used composer create project. Supporting that requires managing dependency resolution in a more complex way.

As a result, we're doing an overhaul of the packaging pipeline, both to support these additional requirements, and to make our packaging system more robust for future changes. The initial deployment will add the architectural robustness needed to allow us to rapidly follow with additional deployments to meet these new requirements.

Change record: https://www.drupal.org/node/3108650

Issue: https://www.drupal.org/node/3108650

Status: Initial round of changes to be deployed week of Jan 27, 2020

Drupal.org release version number format changing patch component to minor
Releases made on Drupal.org have their version numbers parsed into components, including major, minor, and patch. Patch is being replaced with minor, in preparation for allowing contrib projects to use the full semver format. This should be a transparent change, as the Drupal.org composer endpoint already presents project versions in this way, and update status xml will continue reporting the old version number components for legacy compatibility. See the change record for more details.

Change record: https://www.drupal.org/node/3108616

Issue: https://www.drupal.org/project/drupalorg/issues/3104912

Status: To be deployed week of Jan 27, 2020

Updating Drupal.org contributed module version requirements to allow semver
Releases made for contributed projects on Drupal.org must follow specific version number formatting requirements. Currently this is {API compatibility}-{major}.{minor}[-(alpha|beta|RC){number}]. Future releases will be allowed to use semantic versioning, {major}.{minor}.{patch}[-(alpha|beta|RC){number}], dropping the API compatibility component and adding a patch component.

Drupal.org’s Composer endpoint reformats legacy version numbers to semantic versioning, the patch component is always 0. Semantic-versioned releases will go into the 8.x composer endpoint, so Drupal 8, 9, and later sites may install them. There will be restrictions on version numbering to avoid conflicts; for example, if a project has 8.x-1.0 released, they will not be able to release 1.0.0 too