An optional commit reference, such as a branch name or a tag. This is useful if a tagged version has been provided (e.g., `version` is 'v1.0.0' and `ref` is 'refs/tags/v1.0.0').
urlstring
An optional URL that points to the release. This can be a link to a GitHub release, a CI build page, or an internal changelog.
refsarray
An optional way to indicate the start and end commits for each repository included in a release. Head commits must include `repository` and `commit` (the HEAD SHA). They can optionally include `previousCommit` (the SHA of the HEAD of the previous release), which should be specif…
commitsarray
An optional list of commit data to be associated with the release. Commits must include the `id` parameter (the SHA of the commit). Optionally, include `repository`, `message`, `patch_set`, `author_name`, `author_email`, and `timestamp` for richer integration and better suspect…
versionstring
Required
A unique identifier for this release. Can be a semantic version number, a commit hash, or any other string that uniquely identifies this release.
projectsarray
Required
A list of project slugs that are part of this release. These projects must belong to the specified organization.
dateReleasedstring
An optional ISO 8601 timestamp indicating when the release went live. If not provided, the current time is assumed by Sentry.
organization_id_or_slugstring
Required
The ID or slug of the Sentry organization.
Observable output
data
Required
Data from the action execution
errorstring
Error if any occurred during the execution of the action
successfulboolean
Required
Whether or not the action execution was successful or not