Sentry Update Release Details For Organization

• refstring
  Commit reference (e.g., a branch name, tag, or commit SHA) to associate with this release; useful if a tagged version has been provided.
• urlstring
  A URL that points to the release. For instance, this can be the path to an online interface to the source code, such as a GitHub URL, or a link to a release announcement.
• refsarray
  Indicates or updates the start and end commits for each repository in a release. Head commits require ``repository`` and ``commit`` (HEAD SHA), and can optionally include ``previousCommit`` (SHA of previous release's HEAD) for initial data sends or corrections.
• commitsarray
  List of commit data to associate or update for this release; can add new commits or modify existing ones if Sentry's commit tracking needs adjustment.
• versionstring

  Required
  The version identifier of the release to be updated (e.g., '1.0.0', 'my-project@2.3.12'). This identifier must be unique within the organization.
• dateReleasedstring
  ISO 8601 timestamp indicating when the release went live (e.g., '2023-10-26T10:00:00Z'). If not provided, Sentry uses the current time, but an existing dateReleased will not be overwritten unless a new value is provided.
• organization_id_or_slugstring

  Required
  The unique ID or human-readable slug of the Sentry organization.

• 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

No verified related use cases are linked yet.

No published Skills explicitly reference this Action yet.