{"action":"closed","issue":{"url":"https://api.github.com/repos/360EntSecGroup-Skylar/excelize/issues/231","repository_url":"https://api.github.com/repos/360EntSecGroup-Skylar/excelize","labels_url":"https://api.github.com/repos/360EntSecGroup-Skylar/excelize/issues/231/labels{/name}","comments_url":"https://api.github.com/repos/360EntSecGroup-Skylar/excelize/issues/231/comments","events_url":"https://api.github.com/repos/360EntSecGroup-Skylar/excelize/issues/231/events","html_url":"https://github.com/360EntSecGroup-Skylar/excelize/issues/231","id":330602323,"node_id":"MDU6SXNzdWUzMzA2MDIzMjM=","number":231,"title":"Use consistent tag format for versionning","user":{"login":"dolmen","id":129536,"node_id":"MDQ6VXNlcjEyOTUzNg==","avatar_url":"https://avatars1.githubusercontent.com/u/129536?v=4","gravatar_id":"","url":"https://api.github.com/users/dolmen","html_url":"https://github.com/dolmen","followers_url":"https://api.github.com/users/dolmen/followers","following_url":"https://api.github.com/users/dolmen/following{/other_user}","gists_url":"https://api.github.com/users/dolmen/gists{/gist_id}","starred_url":"https://api.github.com/users/dolmen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dolmen/subscriptions","organizations_url":"https://api.github.com/users/dolmen/orgs","repos_url":"https://api.github.com/users/dolmen/repos","events_url":"https://api.github.com/users/dolmen/events{/privacy}","received_events_url":"https://api.github.com/users/dolmen/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-06-08T10:19:17Z","updated_at":"2018-06-14T14:16:05Z","closed_at":"2018-06-14T14:16:05Z","author_association":"CONTRIBUTOR","body":"We have the following tags in the repo:\r\n- `v1.0`\r\n- `1.1`\r\n- `v1.2`\r\n- `1.3`\r\n\r\nThis inconsistent naming is not helpful when upgrading dependencies references from an external project.\r\n\r\nI propose to use semver with a \"v\" prefix (example: \"v1.3.0\") as this is the direction that the Go community is taking with the VGO proposal. https://research.swtch.com/vgo-import"}}
{"actor":{"display_login":"dolmen"}}