Update Release

Update a release's notes, file, compatibility fields, or status. Only include fields you want to change.

PATCH /v1/products/:id/releases/:releaseId

Path Parameters

Parameter	Description
id	Product ID
releaseId	Release ID

Request Body

Field	Type	Description
releaseNotes	string	Changelog / release notes
filePath	string	New storage path (replacing the file removes the orphaned old object)
fileName	string	File name
fileSize	number	File size in bytes
status	string	draft or published — publishing makes it the stable release
requiresWp	string	Minimum WordPress version
testedWp	string	Tested-up-to WordPress version
requiresPhp	string	Minimum PHP version

Version is immutable

version cannot be changed once a release exists — customers and the update channel pin against it. Sending a different version returns 400; create a new release instead.

Response

{
  "data": {
    "message": "Release updated"
  }
}

Example

curl -X PATCH "https://api.packedge.dev/v1/products/prd_xxx/releases/rel_xxx" \
  -H "Authorization: Bearer pk_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "status": "published",
    "releaseNotes": "Now with dark mode"
  }'

Notes

• Publishing (status: "published") automatically makes this the stable release and busts the edge cache for the WordPress update-check
• Other edits also invalidate cached update metadata so changes serve quickly