mirror of
https://github.com/danog/psalm.git
synced 2024-12-11 00:39:38 +01:00
62e7e7f470
Previously we built phar and pushed it: 1. To `psalm/phar:master` (always) 2. To `psalm/phar:$tag` (for tagged releases) However it's entirely possible to tag branches that diverged from master (like when we do a patch release for a legacy version). In this case our push to `psalm/phar:master` was rejected and script failed. As a result, `psalm/phar` was missing the tag (release). Now we will either: * push to `psalm/phar:master` (if the build was for `vimeo/psalm:master`) * or push to `psalm/phar:$tag` (if it's a tagged release) |
||
---|---|---|
.. | ||
build-phar.sh | ||
composer-require-checker-config.json | ||
generate_issues_list_doc.php | ||
generate_levels_doc.php | ||
generate_testsuites.php | ||
github-deploy-phar.sh | ||
improve_class_alias.php | ||
max_used_shortcode.php | ||
phar.psalm.xml | ||
test-with-real-projects.sh | ||
tests-github-actions.sh | ||
update-property-map.php |