Skip to content
Snippets Groups Projects
Commit 66f12e66 authored by Olav Morken's avatar Olav Morken
Browse files

build-release: Use same version number format as in Git

Our releases published to Packagist use version numbers with a
"v"-prefix, e.g. "v1.18.7".

The build-release script overwrites this with a version number without
the "v"-prefix, e.g. "1.18.7".

The result of this is that the composer.json in our release tar-files
does not match the composer.lock file in the repository nor the
composer.json that Packagist looks at.

Fix this by prepending a "v" to the version number when updating
composer.json.
parent 269e996f
No related branches found
No related tags found
No related merge requests found
...@@ -41,7 +41,7 @@ if [ ! -x "$TARGET/composer.phar" ]; then ...@@ -41,7 +41,7 @@ if [ ! -x "$TARGET/composer.phar" ]; then
fi fi
# Set the version in composer.json # Set the version in composer.json
php "$TARGET/composer.phar" config version "$VERSION" -d "$TARGET" php "$TARGET/composer.phar" config version "v$VERSION" -d "$TARGET"
# Install dependencies (without vcs history or dev tools) # Install dependencies (without vcs history or dev tools)
php "$TARGET/composer.phar" install --no-dev --prefer-dist -o -d "$TARGET" php "$TARGET/composer.phar" install --no-dev --prefer-dist -o -d "$TARGET"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment