Composer Package Registry
Publish Composer packages for your user or organization.
Requirements
To work with the Composer package registry, you can use Composer to consume and a HTTP upload client like curl
to publish packages.
Publish a package
To publish a Composer package perform a HTTP PUT operation with the package content in the request body.
The package content must be the zipped PHP project with the composer.json
file.
You cannot publish a package if a package of the same name and version already exists. You must delete the existing package first.
PUT https://gitea.example.com/api/packages/{owner}/composer
Parameter | Description |
---|---|
owner | The owner of the package. |
If the composer.json
file does not contain a version
property, you must provide it as a query parameter:
PUT https://gitea.example.com/api/packages/{owner}/composer?version={x.y.z}
Example request using HTTP Basic authentication:
curl --user your_username:your_password_or_token \
--upload-file path/to/project.zip \
https://gitea.example.com/api/packages/testuser/composer
Or specify the package version as query parameter:
curl --user your_username:your_password_or_token \
--upload-file path/to/project.zip \
https://gitea.example.com/api/packages/testuser/composer?version=1.0.3
If you are using 2FA or OAuth use a personal access token instead of the password.
The server responds with the following HTTP Status codes.
HTTP Status Code | Meaning |
---|---|
201 Created | The package has been published. |
400 Bad Request | The package is invalid. |
409 Conflict | A package file with the same combination of parameters exists already. |