Release Notes and Upcoming Changes
Validated on 26 Jan 2026 • Last edited on 5 May 2026
Use release notes for shipped changes. Use upcoming changes for future or ongoing changes that need more context, preparation, or follow-up documentation.
Release Notes
Use a release note when the change has already shipped and users mainly need to know what changed.
Release notes are usually short. In many cases, one paragraph is enough.
A good release note usually answers these questions:
- What changed?
- Who or what does it affect?
- When did it happen?
- Does the user need to do anything?
- What is the availability or release status?
When relevant, state the release status of the feature or product change, such as private preview, public preview, or general availability.
Common Release Note Types
| Type | What to include | Example |
|---|---|---|
| Feature launches | What is now available, the release status when relevant, and a link to product documentation if needed. | GPU Droplets now support feature X in all regions in public preview. See the product documentation for setup instructions. |
| Deprecations | What is being deprecated, when the deprecation takes effect, and what users should use or do instead. | Support for Ubuntu 20.04 images on App Platform ends on June 1, 2026. Migrate to Ubuntu 22.04 before that date. |
| Pricing or policy changes | What is changing, when it changes, who is affected, and whether users need to take action. | Beginning July 1, 2026, Spaces pricing changes for customers on legacy plans. Review the updated pricing page to confirm your new rates. |
| Maintenance or rollouts | What is changing, when it is rolling out, and what users should expect. | We are rolling out control panel updates between April 1 and April 15, 2026. |
Release Note Example
Managed databases now support example feature X in all regions in general availability. See the product documentation for setup instructions.Upcoming Changes
Use an upcoming change when the change has not happened yet, is rolling out over time, may require user preparation or action, or needs more explanation than a standard release note.
Upcoming changes are usually longer than release notes because they explain the change, timing, impact, and any required preparation.
An upcoming change usually includes:
- What is changing?
- When is it expected to happen?
- Who is affected?
- What do users need to do, if anything?
- Any important deadlines, limitations, or rollout details
- Links to related documentation
Lead with the change and timing. Do not bury deadlines or required actions near the end of the article.
Use a clear, descriptive title that states the change.
Good title patterns include:
Tax collection for Eastasia beginning April 2020Deprecation of Example Feature on June 1, 2026Changes to Spaces pricing in July 2026
Upcoming Change Example
Beginning April 1, 2026, we will update tax collection for customers in Eastasia.
This change affects non-business customers in Eastasia and business customers that do not have a valid BBT ID on file.
If your business has a registered BBT ID, add it to your billing profile before April 1, 2026.
For more information, see the billing documentation.Key Differences
Release notes announce a shipped change. They are usually shorter and focus on what changed and any immediate user impact.
Upcoming changes prepare users for a future or ongoing change. They are usually longer and focus on timing, impact, and any action users need to take before the change happens.