Creates a new Sentry release for an existing organization, associating it with specified projects that must belong to that organization.
refstringAn 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').
urlstringAn optional URL that points to the release. This can be a link to a GitHub release, a CI build page, or an internal changelog.
refsarrayAn 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…
commitsarrayAn 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…
versionRequiredstringA unique identifier for this release. Can be a semantic version number, a commit hash, or any other string that uniquely identifies this release.
projectsRequiredarrayA list of project slugs that are part of this release. These projects must belong to the specified organization.
dateReleasedstringAn optional ISO 8601 timestamp indicating when the release went live. If not provided, the current time is assumed by Sentry.
organization_id_or_slugRequiredstringThe ID or slug of the Sentry organization.
dataRequiredData from the action execution
errorstringError if any occurred during the execution of the action
successfulRequiredbooleanWhether or not the action execution was successful or not
API key connection. Risk level 2 of 5.
Free Action
No published Skills explicitly reference this Action yet.