{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/vsts-extension-build-release-tasks/issues/99","repository_url":"https://api.github.com/repos/Microsoft/vsts-extension-build-release-tasks","labels_url":"https://api.github.com/repos/Microsoft/vsts-extension-build-release-tasks/issues/99/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/vsts-extension-build-release-tasks/issues/99/comments","events_url":"https://api.github.com/repos/Microsoft/vsts-extension-build-release-tasks/issues/99/events","html_url":"https://github.com/Microsoft/vsts-extension-build-release-tasks/issues/99","id":379180069,"node_id":"MDU6SXNzdWUzNzkxODAwNjk=","number":99,"title":"Category validation mismatch - can't build or can't publish","user":{"login":"djerghiuta","id":22031434,"node_id":"MDQ6VXNlcjIyMDMxNDM0","avatar_url":"https://avatars0.githubusercontent.com/u/22031434?v=4","gravatar_id":"","url":"https://api.github.com/users/djerghiuta","html_url":"https://github.com/djerghiuta","followers_url":"https://api.github.com/users/djerghiuta/followers","following_url":"https://api.github.com/users/djerghiuta/following{/other_user}","gists_url":"https://api.github.com/users/djerghiuta/gists{/gist_id}","starred_url":"https://api.github.com/users/djerghiuta/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djerghiuta/subscriptions","organizations_url":"https://api.github.com/users/djerghiuta/orgs","repos_url":"https://api.github.com/users/djerghiuta/repos","events_url":"https://api.github.com/users/djerghiuta/events{/privacy}","received_events_url":"https://api.github.com/users/djerghiuta/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-11-09T14:20:59Z","updated_at":"2018-11-09T17:22:09Z","closed_at":null,"author_association":"NONE","body":"I am building extensions for Azure Pipelines using this extension. I was surprised that it does not allow the new categories (i.e. \"Azure Pipelines\") and forced me to use the old TFS ones (i.e.\"Build and release\"), but did not bother me as long as there was backward compatibility. Something must have changed in the last couple of days, and Azure DevOps no longer allows \"Build and release\" category on publish. If I change to \r\n\"Aure Pipelines\", the Pack Extension task says it's invalid.\r\n\r\nI believe the problem is that the extension downloads tfx-cli@0.5.3, which was TFS-specific. \r\n\r\nWorkaround: Before Pack Extension, I add an NPM step with the command:\r\ninstall tfx-cli --prefix D:\\a\\_tools\\\r\nThis puts the latest version (0.6.0) in the place where the extension likes to cache it, and the packing task uses it. This version is compatible with Azure Pipelines.\r\n\r\nIt would be better if the extension would use latest tfx-cli by default, and, if necessary, document the workaround for TFS 2018 or older:\r\ninstall tfx-cli@0.5.3 --prefix D:\\a\\_tools\\\r\n"},"comment":{"url":"https://api.github.com/repos/Microsoft/vsts-extension-build-release-tasks/issues/comments/437431538","html_url":"https://github.com/Microsoft/vsts-extension-build-release-tasks/issues/99#issuecomment-437431538","issue_url":"https://api.github.com/repos/Microsoft/vsts-extension-build-release-tasks/issues/99","id":437431538,"node_id":"MDEyOklzc3VlQ29tbWVudDQzNzQzMTUzOA==","user":{"login":"jessehouwing","id":4173387,"node_id":"MDQ6VXNlcjQxNzMzODc=","avatar_url":"https://avatars1.githubusercontent.com/u/4173387?v=4","gravatar_id":"","url":"https://api.github.com/users/jessehouwing","html_url":"https://github.com/jessehouwing","followers_url":"https://api.github.com/users/jessehouwing/followers","following_url":"https://api.github.com/users/jessehouwing/following{/other_user}","gists_url":"https://api.github.com/users/jessehouwing/gists{/gist_id}","starred_url":"https://api.github.com/users/jessehouwing/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jessehouwing/subscriptions","organizations_url":"https://api.github.com/users/jessehouwing/orgs","repos_url":"https://api.github.com/users/jessehouwing/repos","events_url":"https://api.github.com/users/jessehouwing/events{/privacy}","received_events_url":"https://api.github.com/users/jessehouwing/received_events","type":"User","site_admin":false},"created_at":"2018-11-09T17:22:09Z","updated_at":"2018-11-09T17:22:09Z","author_association":"COLLABORATOR","body":"I'll. Update this issue.\n\nOn Fri, 9 Nov 2018, 18:21 Jeff Przylucki <notifications@github.com wrote:\n\n> I am also experiencing this issue.. can't build the publish-able vsix...\n> can't publish the build-able vsix. I am putting on the bypass on my build\n> now, how can we best find out when there has been a fix for this so that we\n> can go back and remove that bypass in the future (I don't really want to\n> bypass the validations..)\n>\n> —\n> You are receiving this because you commented.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/Microsoft/vsts-extension-build-release-tasks/issues/99#issuecomment-437431176>,\n> or mute the thread\n> <https://github.com/notifications/unsubscribe-auth/AD-uS-f1uI5JFDfe7TeUgbTASIHQqLnIks5utbmGgaJpZM4YWqOI>\n> .\n>\n"}}
{"actor":{"display_login":"jessehouwing"}}