I am trying to set up the package "ourcompany/project" in our own nexus repository, using composer-push. We have versions based on commit hashes already, that works nicely, and now I want to additionally always push a "latest" version (so that it can be used in test pipelines). Here I get the following error message:
Pushing archive to URL: https://nexus.ourcompany.com/repository/composer-ourcompany/packages/upload/ourcompany/project/latest...
[GuzzleHttp\Exception\ClientException]
Client error: `PUT https://nexus.ourcompany.com/repository/composer-ourcompany/packages/upload/ourcompany/project/latest` resulted in a `400 Repository does not allow updating assets: composer-ourcompany` response
push [--name NAME] [--url URL] [--type TYPE] [--repository REPOSITORY] [--username USERNAME] [--password PASSWORD] [-i|--ignore [IGNORE]] [--ignore-dirs [IGNORE-DIRS]] [--ignore-by-git-attributes] [--ignore-by-composer] [--src-type SRC-TYPE] [--src-url SRC-URL] [--src-ref SRC-REF] [--keep-vendor] [--keep-dot-files] [--ssl-verify [SSL-VERIFY]] [--access-token [ACCESS-TOKEN]] [--] [<version>]
Can composer-push be configured to force overriding the existing version name? If not, are there other ways of always getting the latest version of a package?
I am trying to set up the package "ourcompany/project" in our own nexus repository, using composer-push. We have versions based on commit hashes already, that works nicely, and now I want to additionally always push a "latest" version (so that it can be used in test pipelines). Here I get the following error message:
Can composer-push be configured to force overriding the existing version name? If not, are there other ways of always getting the latest version of a package?