uuid: - value: 123f0530-1218-4db1-b8ce-aecf38d8ec41 langcode: - value: en type: - target_id: daily_email target_type: node_type target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7 revision_timestamp: - value: '2025-05-11T09:00:40+00:00' revision_uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 revision_log: { } status: - value: true uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 title: - value: | Semantic versioning created: - value: '2023-05-19T00:00:00+00:00' changed: - value: '2025-05-11T09:00:40+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2023/05/19/semantic-versioning langcode: en body: - value: |
The version number of a release is a key indicator of whether it’s compatible with existing code.
Semantic versioning is a popular approach used by Drupal core, and many contributed modules, themes and distributions.
It uses version numbers like 1.0.0 to show the major, minor and patch versions.
If the second or third number changes, e.g. 1.1.0 or 1.0.1, the release contains new backwards-compatible features or fixes, so it’s safe to update.
If the first number changes, e.g. 2.0.0, the release is not backwards compatible and contains breaking changes that you’ll need to review and update your code accordingly.
format: full_html processed: |The version number of a release is a key indicator of whether it’s compatible with existing code.
Semantic versioning is a popular approach used by Drupal core, and many contributed modules, themes and distributions.
It uses version numbers like 1.0.0 to show the major, minor and patch versions.
If the second or third number changes, e.g. 1.1.0 or 1.0.1, the release contains new backwards-compatible features or fixes, so it’s safe to update.
If the first number changes, e.g. 2.0.0, the release is not backwards compatible and contains breaking changes that you’ll need to review and update your code accordingly.
summary: null field_daily_email_cta: { }