Update an Organization's Release

Go to Product

Update a release. This can change some metadata associated with the release (the ref, url, and dates).

Options

Organization Id or Slug
The ID or slug of the organization the resource belongs to.
Version
The version identifier of the release
Body

Request body which must comply to the following JSON Schema:

{
  "type" : "object",
  "properties" : {
    "ref" : {
      "maxLength" : 200,
      "type" : "string",
      "description" : "An optional commit reference. This is useful if a tagged version has been provided.",
      "nullable" : true
    },
    "url" : {
      "type" : "string",
      "description" : "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.",
      "format" : "uri",
      "nullable" : true
    },
    "dateReleased" : {
      "type" : "string",
      "description" : "An optional date that indicates when the release went live.  If not provided the current time is used.",
      "format" : "date-time",
      "nullable" : true
    },
    "commits" : {
      "type" : "array",
      "description" : "An optional list of commit data to be associated.",
      "items" : {
        "required" : [ "id" ],
        "type" : "object",
        "properties" : {
          "id" : {
            "maxLength" : 64,
            "type" : "string"
          },
          "repository" : {
            "maxLength" : 64,
            "type" : "string",
            "nullable" : true
          },
          "message" : {
            "type" : "string",
            "nullable" : true
          },
          "author_name" : {
            "maxLength" : 128,
            "type" : "string",
            "nullable" : true
          },
          "author_email" : {
            "maxLength" : 75,
            "type" : "string",
            "nullable" : true
          },
          "timestamp" : {
            "type" : "string",
            "format" : "date-time",
            "nullable" : true
          },
          "patch_set" : {
            "type" : "array",
            "nullable" : true,
            "items" : {
              "required" : [ "path", "type" ],
              "type" : "object",
              "properties" : {
                "path" : {
                  "maxLength" : 510,
                  "type" : "string"
                },
                "type" : {
                  "maxLength" : 1,
                  "type" : "string"
                }
              }
            }
          }
        }
      }
    },
    "refs" : {
      "type" : "array",
      "description" : "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.",
      "items" : {
        "required" : [ "commit", "repository" ],
        "type" : "object",
        "properties" : {
          "commit" : {
            "type" : "string"
          },
          "repository" : {
            "maxLength" : 200,
            "type" : "string"
          },
          "previousCommit" : {
            "maxLength" : 64,
            "type" : "string",
            "nullable" : true
          }
        }
      }
    }
  }
}
Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Structured Table: Returns a parsed table with data split into rows and columns.

  • Ref:
  • Url:
  • Date Released:
  • Date Created:
  • Date Started:
  • Owner:
  • Last Commit:
  • Last Deploy:
  • First Event:
  • Last Event:
  • Current Project Meta:
  • User Agent:
  • Adoption Stages:
  • Id:
  • Version:
  • New Groups:
  • Status:
  • Short Version:
  • Version Info:
  • Data:
  • Commit Count:
  • Deploy Count:
  • Authors:
  • Projects:

Raw Response: Returns the raw response in a single row with the following columns:

  • body: Response body
  • status: HTTP status code

Input Ports

Icon
Configuration data.

Output Ports

Icon
Result of the request depending on the selected Result Format.
Icon
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.