Delete a package

Delete a package and every version: it is gone from the registries at once, and can be restored for 30 days, during which its name cannot be taken.

DELETE/workspaces/{workspace}/packages/{package_type}/{package_name}

Takes the Admin role on the package.

The package and every version are gone from the registry at once. Restore it with restore_package within 30 days; until then nobody can publish a package of its name.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: package with action delete, and the same inputs
Scope: An access token needs packages:delete.

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s slug, e.g. “flagon-io”.
`package_type`	string	Yes	The registry: container (also docker), npm, cargo, maven, nuget, rubygems or composer. One of `container`, `npm`, `cargo`, `maven`, `nuget`, `rubygems`, `composer`.
`package_name`	string	Yes	The package’s name without the workspace: web for g1t.sh/acme/web, web/worker for an image with more parts, group:artifact for Maven.

Example request

curl -X DELETE https://api.g1t.sh/workspaces/acme/packages/container/web-old \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

{
  "deleted": true
}

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.