git sync: tag not found bug should be fixed

[hoatle]

something changes git github repo as the new tag configured did not work for git sync at the moment

$ vagrant status
fatal: ambiguous argument 'v0.6.0-a7': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: ambiguous argument 'v0.6.0-a7': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
[TeracyDev::Location::GitSynch][WARN]: tag not found: v0.6.0-a7

A workaround for this is that users must fetch new tags before $ vagrant status

$ git fetch --tags
remote: Enumerating objects: 26, done.
remote: Counting objects: 100% (26/26), done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 26 (delta 15), reused 25 (delta 15), pack-reused 0
Unpacking objects: 100% (26/26), done.
From https://github.com/teracyhq/dev
 * [new tag]         v0.6.0-a7  -> v0.6.0-a7
$ vagrant status
Previous HEAD position was 9164282 Merge pull request #583 from hoatle/tasks/#582-v0.6.0-a6-release
HEAD is now at a817b5c Merge pull request #592 from hoatle/tasks/#590-v0.6.0-a7-release
[TeracyDev::Loader][INFO]: reloading...

[hoatle]

should be fixed by v0.6.0-a8

[hoatle]

verified, closed.

[hoatle]

note

• prior to v0.6.0-a8: users must execute $ git fetch --tags manually then $ vagrant up/reload/status for upgrading teracy-dev and extensions. So it's wise to upgrade teracy-dev to v0.6.0-a8 first before upgrading extensions.

• after v0.6.0-a8: $ vagrant up/reload/status should upgrade teracy-dev and extenstions as normal.