Skip to main content
POST
Start a release and get links to upload its artifacts

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

owner
string
required

Owning user or team slug

Required string length: 1 - 255
name
string
required

Package name

Required string length: 1 - 255

Body

application/json
version
string
required

PEP 440; must be new in the package

Required string length: 1 - 255
artifacts
ArtifactDeclaration · object[]
required

Exactly one source, and at most one wheel

Required array length: 1 - 2 elements
metadata
Metadata · object

What the release declares about itself, such as description, tags and the requires_dist that shows which verifiers API it targets

framework
enum<string> | null

The verifiers API it targets, overriding what metadata implies; omit to go by the verifiers requirement in metadata

Available options:
v0,
v1

Response

Successful Response

release_id
string
required
version
string
required

The version as stored, in PEP 440 normal form

content_hash
string
required

The source artifact's sha256

uploads
ArtifactUpload · object[]
required