Create a new release for the given Organization. Releases are used by
Sentry to improve its error reporting abilities by correlating
first seen events with the release that might have introduced the
Releases are also necessary for sourcemaps and other debug features
that require manual upload for functioning well.
the slug of the organization the release belongs to.
a version identifier for this release. Can be a version number, a commit hash etc.
an optional commit reference. This is useful if a tagged version has been provided.
a URL that points to the release. This can be the path to an online interface to the sourcecode for instance.
a list of project slugs that are involved in this release
an optional date that indicates when the release went live. If not provided the current time is assumed.
an optional list of commit data to be associated with the release. Commits must include parameters id (the sha of the commit), and can optionally include repository, message, patch_set, author_name, author_email, and timestamp. See release without integration example.
an optional way to indicate the start and end commits for each repository included in a release. Head commits must include parameters repository and commit (the HEAD sha). They can optionally include previousCommit (the sha of the HEAD of the previous release), which should be specified if this is the first time you’ve sent commit data. commit may contain a range in the form of previousCommit..commit