Fatal error if git tags contain a string which is not a valid version #256
Labels
Comments
REBELinBLUE
added a commit
that referenced
this issue
Aug 2, 2016
* bug/invalid-tag-name: Fixes #256 - Git tag names causing a fatal error if they are not valid version string
REBELinBLUE
added a commit
that referenced
this issue
Aug 2, 2016
* master: Updated ioredis Updated google2fa library Fixes #254 Fixes #256 - Git tag names causing a fatal error if they are not valid version string Fixed gulpfile so that assets don't get removed before they are versioned Updated dependencies Conflicts: composer.json composer.lock gulpfile.js socket.js
REBELinBLUE
added a commit
that referenced
this issue
Aug 6, 2016
* master: (60 commits) Updated CHANGELOG Fixes #257 - Touch files when extracting to prevent warnings about timestamps Update README.md Added a note about a common error Updated ioredis Updated google2fa library Fixes #254 Fixes #256 - Git tag names causing a fatal error if they are not valid version string Fixed gulpfile so that assets don't get removed before they are versioned Updated dependencies Updated dependencies Priority WS for optimal transport browser (#250) Ignore suggestions when installing Composer deps (#252) Fix style issue Revert "[Snyk Alert] Fix for 2 vulnerable dependency paths" (#245) fix: package.json & .snyk to reduce vulnerabilities (#244) Handling the timeout checking for an update on github, i.e. when I am at work behind a proxy Added a check to the updatre script to ensure npm install has been run Update dialog.blade.php (#239) Silence PHPMD ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The project screen dies if the git tags contains something which can not be parsed as a version
The text was updated successfully, but these errors were encountered: