uuid:
  - value: f9c3fa81-7fb6-42e0-ab93-f62c9e8669cf
langcode:
  - value: en
type:
  - target_id: daily_email
    target_type: node_type
    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
  - value: '2025-07-31T23:21:20+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: 'Do you keep a changelog?'
created:
  - value: '2025-07-27T23:20:54+00:00'
changed:
  - value: '2025-07-31T23:21:20+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: ''
    pid: null
    langcode: en
body:
  - value: |-
      A changelog is a simple file that file that documents notable changes in your application.

      Drupal has previously used [a CHANGELOG.txt file][0] and many open source projects use a CHANGELOG.md file.

      If you want people to use your application, you should document any new additions, changes or removals so people can see the project is maintained and prepare for any breaking changes in upcoming versions.

      This is also true for internal projects, in case any stakeholders want to know when a certain feature was released, or what was released in a given timeframe.

      The format I like is from <https://keepachangelog.com>.

      It's a Markdown file that shows additions, changes and removals grouped by release numbers, like 1.0.0.

      It uses anchor links to make the headings clickable, and links them to tags or diffs within the Git repository for people to see the commits and code changes between each release.

      As it's a Markdown file, it's easy to update for each release.

      I also like that the example Changelog on the website is the changelog for the format itself.

      I recently started to port one of my bash scripts [to a Go application][1], and decided to use this format in that repository - for me and for potential future users.

      If you don't keep a changelog in your application, I'd suggest trying this format.

      [0]: https://api.drupal.org/api/drupal/CHANGELOG.txt/7.x
      [1]: https://code.oliverdavies.uk/opdavies/git-repo-updater
    format: markdown
    processed: |
      <p>A changelog is a simple file that file that documents notable changes in your application.</p>
      <p>Drupal has previously used <a href="https://api.drupal.org/api/drupal/CHANGELOG.txt/7.x">a CHANGELOG.txt file</a> and many open source projects use a CHANGELOG.md file.</p>
      <p>If you want people to use your application, you should document any new additions, changes or removals so people can see the project is maintained and prepare for any breaking changes in upcoming versions.</p>
      <p>This is also true for internal projects, in case any stakeholders want to know when a certain feature was released, or what was released in a given timeframe.</p>
      <p>The format I like is from <a href="https://keepachangelog.com">https://keepachangelog.com</a>.</p>
      <p>It's a Markdown file that shows additions, changes and removals grouped by release numbers, like 1.0.0.</p>
      <p>It uses anchor links to make the headings clickable, and links them to tags or diffs within the Git repository for people to see the commits and code changes between each release.</p>
      <p>As it's a Markdown file, it's easy to update for each release.</p>
      <p>I also like that the example Changelog on the website is the changelog for the format itself.</p>
      <p>I recently started to port one of my bash scripts <a href="https://code.oliverdavies.uk/opdavies/git-repo-updater">to a Go application</a>, and decided to use this format in that repository - for me and for potential future users.</p>
      <p>If you don't keep a changelog in your application, I'd suggest trying this format.</p>
    summary: ''
field_daily_email_cta:
  - target_type: node
    target_uuid: c74de3cf-5362-4d08-935a-a9d0d22fcb94