{"action":"created","issue":{"url":"https://api.github.com/repos/rapid7/metasploit-framework/issues/9706","repository_url":"https://api.github.com/repos/rapid7/metasploit-framework","labels_url":"https://api.github.com/repos/rapid7/metasploit-framework/issues/9706/labels{/name}","comments_url":"https://api.github.com/repos/rapid7/metasploit-framework/issues/9706/comments","events_url":"https://api.github.com/repos/rapid7/metasploit-framework/issues/9706/events","html_url":"https://github.com/rapid7/metasploit-framework/pull/9706","id":304651204,"number":9706,"title":"fix #9497, bump metasploit payloads","user":{"login":"timwr","id":684924,"avatar_url":"https://avatars2.githubusercontent.com/u/684924?v=4","gravatar_id":"","url":"https://api.github.com/users/timwr","html_url":"https://github.com/timwr","followers_url":"https://api.github.com/users/timwr/followers","following_url":"https://api.github.com/users/timwr/following{/other_user}","gists_url":"https://api.github.com/users/timwr/gists{/gist_id}","starred_url":"https://api.github.com/users/timwr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timwr/subscriptions","organizations_url":"https://api.github.com/users/timwr/orgs","repos_url":"https://api.github.com/users/timwr/repos","events_url":"https://api.github.com/users/timwr/events{/privacy}","received_events_url":"https://api.github.com/users/timwr/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-03-13T07:14:04Z","updated_at":"2018-03-13T08:16:28Z","closed_at":"2018-03-13T07:43:41Z","author_association":"CONTRIBUTOR","pull_request":{"url":"https://api.github.com/repos/rapid7/metasploit-framework/pulls/9706","html_url":"https://github.com/rapid7/metasploit-framework/pull/9706","diff_url":"https://github.com/rapid7/metasploit-framework/pull/9706.diff","patch_url":"https://github.com/rapid7/metasploit-framework/pull/9706.patch"},"body":"This includes https://github.com/rapid7/metasploit-payloads/pull/275\r\n"},"comment":{"url":"https://api.github.com/repos/rapid7/metasploit-framework/issues/comments/372581877","html_url":"https://github.com/rapid7/metasploit-framework/pull/9706#issuecomment-372581877","issue_url":"https://api.github.com/repos/rapid7/metasploit-framework/issues/9706","id":372581877,"user":{"login":"busterb","id":4108654,"avatar_url":"https://avatars3.githubusercontent.com/u/4108654?v=4","gravatar_id":"","url":"https://api.github.com/users/busterb","html_url":"https://github.com/busterb","followers_url":"https://api.github.com/users/busterb/followers","following_url":"https://api.github.com/users/busterb/following{/other_user}","gists_url":"https://api.github.com/users/busterb/gists{/gist_id}","starred_url":"https://api.github.com/users/busterb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/busterb/subscriptions","organizations_url":"https://api.github.com/users/busterb/orgs","repos_url":"https://api.github.com/users/busterb/repos","events_url":"https://api.github.com/users/busterb/events{/privacy}","received_events_url":"https://api.github.com/users/busterb/received_events","type":"User","site_admin":false},"created_at":"2018-03-13T08:16:28Z","updated_at":"2018-03-13T08:16:28Z","author_association":"CONTRIBUTOR","body":"There are good reasons why it commits the version bump immediately after the gem is published and released. This is consistent across metasploit-framework and all dependent gems:\r\n\r\n  1. When someone says 'I'm on version 1.2.3', you know whether they are using a checked-out version of master, or an actual release, just by the version number. Prior to this change, this was a frequent problem.\r\n  2. The build automation triggers on commits. If the last commit itself was a version bump, the build automation knows not to build again and to get in an infinite loop. The version commit basically is marker used by the build automation.\r\n\r\nThink of the version bump as a marker as 'this will be the next version released'. Now, the lack of tags looks like a problem in our usage of the gem-release tool, but something that could be fixed too. I think @jmartin-r7 has a fix in the build templates."}}
{"actor":{"display_login":"busterb"}}