Skip to content
WorkspaceTemplates
The first pages of the Software Changelog template

Software Changelog

Document template for Google Docs and Word

Make a copy in Google Docs
Type
Document
Price
Free
Pages
9 · US Letter
Style
Minimal
Difficulty
Beginner
Updated
October 31, 2026

Every page (9)

Overview

Users read release notes to find out what they can do now, what might break and what they have to change. This changelog is organized in the Keep a Changelog order and ranked by impact: the version and its endpoint first, then added, changed, deprecated, removed, fixed and security items, followed by upgrade steps and known issues.

The sample documents v4.12.0 of Thistledown Cloud, released on October 14, 2026 in a staged rollout of 5%, 25% and 100%. It includes four new features, four removals with replacements, three linked fixes and two security advisories. Replace the version, date and audience first, then rewrite each item as an outcome for the user.

Useful for

  • An open source maintainer publishing release notes that follow semantic versioning sections
  • A product team announcing a release to admins, with breaking changes and a migration path up front
  • A support team preparing answers for a staged rollout, with known issues and workarounds in one place

What's included

  • Version page with the release endpoint, a parameters table and request and response examples
  • Added page with four new features, a release timeline and carry-forward actions
  • Changed page with a layered architecture diagram and a request flow
  • Deprecated and removed pages with sunset date, replacements and a migration table
  • Fixed items linked to issue numbers, and a security page with advisories and severity
  • Two-column upgrade guide with steps for administrators, known issues and where to get help

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Set the version number, release date and audience on the first page, then rewrite each highlight as what the user can now do.

  3. 3

    Move anything that breaks existing use into the removed section, with a before-and-after example and the replacement.

  4. 4

    Link every fix to its issue or ticket, delete fixes users will never notice, and keep known issues only if you have some.

  5. 5

    Delete the Make it yours page, then publish the changelog or share it with your users.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

Which sections does the changelog use?

Added, Changed, Deprecated, Removed, Fixed and Security, the same groups used by the Keep a Changelog convention. Delete any group that has no entries in your release.

Where should breaking changes go?

Put them near the top, not in the middle of a long list. The sample lists removals on their own page with a replacement and one migration step for each.

Are the company and figures real?

No. Thistledown Cloud, every person named, the issue numbers and all the figures are fictional sample content. Replace them with your own release details.

  • #changelog
  • #release-notes
  • #semantic-versioning
  • #software-release
  • #upgrade-guide
  • #open-source
  • #developer-docs
  • #google-docs

Related templates

More Google Docs templatesMore developer workflows templates

More release notes templates

See all 5

Also in Developer workflows

All developer workflows templates
Get this template

    What you get

      Use this templateSee full details

      Preparing your template…