Optional
description?: stringA short description of the release.
Optional
featuredImage?: stringThe URL to an image that may be prominently displayed with the release note.
Zero or more release notes containing the locale and content. Multiple note messages may be specified to support release notes in a wide variety of languages.
Specifies optional, custom, properties
A collection of issues that have been resolved.
Optional
socialImage?: stringThe URL to an image that may be used in messaging on social media platforms.
Textual strings that aid in the discovery, search, and retrieval of the associated object. Tags often serve as a way to group or categorize similar or related objects by various attributes. Examples include "json-parser", "object-persistence", "text-to-image", "translation", and "object-detection".
Optional
timestamp?: TimestampThe date and time (timestamp) when the release note was created.
Optional
title?: stringThe title of the release.
The software versioning type. It is RECOMMENDED that the release type use one of 'major', 'minor', 'patch', 'pre-release', or 'internal'. Representing all possible software release types is not practical, so standardizing on the recommended values, whenever possible, is strongly encouraged.
Optional alternate names the release may be referred to. This may include unofficial terms used by development and marketing teams (e.g. code names).