Update Release

firebase_app_distribution.update_release
ActionBusiness appsconnection required

Calls firebaseappdistribution v1 PATCH /v1/projects/{projectsId}/apps/{appsId}/releases/{releasesId}.

Updates a release.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Firebase App Distribution
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
app
App name or id.
stringYes———
release
Release name or id.
stringYes———
body
The GoogleFirebaseAppdistroV1Release resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
acceptedInvitationCount
integer—
androidPackageRegistrationState
string—
binaryDownloadUri
string—
binaryType
string—
buildVersion
string—
createTime
string—
displayVersion
string—
expireTime
string—
feedbackCount
integer—
firebaseConsoleUri
string—
installationCount
integer—
name
string—
openInvitationCount
integer—
releaseNotes
object—
testState
string—
testingUri
string—
updateTime
string—
{
  "acceptedInvitationCount": 0,
  "androidPackageRegistrationState": "",
  "binaryDownloadUri": "",
  "binaryType": "",
  "buildVersion": "",
  "createTime": "",
  "displayVersion": "",
  "expireTime": "",
  "feedbackCount": 0,
  "firebaseConsoleUri": "",
  "installationCount": 0,
  "name": "",
  "openInvitationCount": 0,
  "releaseNotes": {},
  "testState": "",
  "testingUri": "",
  "updateTime": ""
}

See Update Release run in a workflow.

In a technical demo we add the Firebase App Distribution connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.