Keep a structured changelog that records every release, what changed, and who shipped it. This template organizes releases into rows with the version number, release date, change type (Feature, Fix, Improvement, Breaking Change), a description of the change, and the author. Unlike a markdown changelog file buried in your repo, a spreadsheet changelog can be shared with non-technical stakeholders via a link — product managers, customer success, and leadership can see what shipped without digging through Git history. When integrated with the API, you can auto-populate the changelog from your CI/CD pipeline. Each time a release is tagged, your deploy script adds a row with the version, description from the release notes, and the engineer who authored the commit. Over time, you build a searchable, sortable record of every change your product has ever shipped.
| Version | Date | Type | Description | Author | PR/Issue |
|---|---|---|---|---|---|
| 2.4.0 | 2026-03-22 | Feature | Added bulk row insert endpoint | Priya Nair | #412 |
| 2.3.2 | 2026-03-18 | Fix | Fixed CSV export encoding for Unicode characters | Leo Chang | #408 |
| 2.3.1 | 2026-03-15 | Improvement | Reduced spreadsheet load time by 40% | Priya Nair | #405 |
| 2.3.0 | 2026-03-10 | Feature | Added document sharing permissions API | Kenji Tanaka | #398 |
Generate this changelog programmatically with a single POST request. The API returns a shareable URL that anyone can open in the browser.
curl -X POST https://openofficeai.com/api/v1/sheets \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"title": "My Changelog",
"sheets": [{ "rows": [["Version","Date","Type","Description","Author","PR/Issue"],["2.4.0","2026-03-22","Feature","Added bulk row insert endpoint","Priya Nair","#412"],["2.3.2","2026-03-18","Fix","Fixed CSV export encoding for Unicode characters","Leo Chang","#408"]] }]
}'Returns { "id": "...", "url": "...", "created_at": "..." }. See the full API docs for formatting, formulas, and export options.
This template comes with 6 columns designed for a standard changelog workflow. Each column can be renamed, reordered, or extended through the API or the browser editor.
The semantic version number for this release (e.g., 2.4.0).
The date this version was released.
The kind of change: Feature, Fix, Improvement, Breaking Change, or Deprecation.
A concise explanation of what changed in this release.
The engineer or team member who shipped this change.
The pull request or issue number associated with this change.
This template is a starting point. Here are specific ways to adapt it to your workflow:
Add a "Impact" column (Low, Medium, High) to help users quickly assess whether a change affects their workflow.
Include a "Migration Required" boolean column for breaking changes, so developers can filter for entries that need action on their end.
Add a "Related Docs" column linking to updated documentation pages for each change, creating a bridge between your changelog and your docs site.
Yes. Set up a GitHub Action that triggers on new releases. The action reads the release tag, title, and body, formats them into a changelog row, and calls the API to append the row to your changelog spreadsheet. This eliminates manual changelog maintenance entirely.
Use the Type column with consistent values: Feature, Fix, Improvement, Breaking Change, Deprecation. You can enforce these values in your automation script. Once the data is in the spreadsheet, stakeholders can sort or filter by type to see only bug fixes or only new features.
They serve different audiences. A CHANGELOG.md file lives in your repo and is useful for developers reading the source code. A spreadsheet changelog is better for sharing with non-technical stakeholders who want a link they can open in their browser without touching your codebase.
Document your API endpoints in a structured spreadsheet that developers can reference and share. Thi...
Keep your team aligned with a project tracker that shows every task, its owner, status, and deadline...
Compare features across products, plans, or competitors in a clear matrix format. This template puts...
Sign up for free and start building spreadsheets in seconds — from the browser or via the API.